Regions and Availability Zones
Last updated: 2018-09-13 15:38:46PDF
Tencent Cloud CVM's entrusted data centers are located in different regions around the world, which are all made up of region and availability zone.
Each region is an independent geographical location. Within each region, there are multiple mutually isolated locations referred to as availability zones. Each region is entirely independent. Each availability zone is independent. However, availability zones in the same region can be connected via private network links with low latency.
Tencent Cloud supports distribution of cloud resources in different locations by users. Users are advised to consider placing resources in different availability zones when designing system to shield "service unavailable" status caused by single point of failure.
Regions are completely isolated with each other, so as to ensure high stability and fault tolerance. Tencent Cloud now have 3 regions in Mainland China and provides nodes in Hong Kong, Singapore and Toronto. You are recommended to choose nearest region to reduce access latency and improve download speed.
Region attribute is differentiated for all behaviors such as enabling and viewing instances by users. If image of the instance that the users need to enable does not exist in the region, then the image needs to be copied to current region. For more information, please see Copy Image.
- Resources in different availability zones of the same region are connected via private network, and can be accessed directly using Private IP.
- Cloud services of different regions cannot communicate via private network by default.
- CVMs cannot access other CVMs, Cloud Database or Cloud Memcached across regions by default.
- When binding Cloud Load Balance to the server, only CVMs in the current region can be chosen;
- Cloud resources on different regions can communicate via Public IP. Cloud Services on VPC can access Internet via peering connection service.
- Cloud Load Balance does not support cross-region data forwarding.
- Regions are named by Coverage + City, and availability zones are named by city + serial number.
- Only resources under the same account can communicate via private network.
Notes for Hong Kong region:
- The following cloud services are temporarily unavailable: Cloud Memcached, elastic web engine, Cloud Object Storage, Cloud Block Storage, one-click opening of server and domain binding with separated regions and servers.
- When you need to log in to CVMs in Hong Kong region, log in via jump server is recommended for better operation and maintenance experience.
Notes for North America region:
- The following cloud services are temporarily unavailable: Cloud Memcached, elastic web engine, Cloud Object Storage, mobile acceleration, Cloud Automated Testing, one-click opening of server and domain binding with separated regions and servers.
- Due to the considerable latency between North America and China, when you need to log in to CVMs in North America region, login via jump server is recommended for better operation and maintenance experience.
Availability zones (Zone) refer to Tencent Cloud's physical data centers whose power and network are independent from each other within the same region. They are designed to ensure that the failures within an availability zones can be isolated (except for large-scale disaster or major power failure) without spreading to and affecting other zones so that users' businesses can provide continuous online services. By starting an instance in an independent availability zone, users can protect their applications from being affected by the failures occurring in a single location.
When starting an instance, users can choose any availability zone within the specified region. If a user needs to ensure the high reliability of application systems so that the services are still available even when a failure occurs in an instance, the user can use cross-zone deployment scheme (e.g. Cloud Load Balance, Elastic IP, etc.) to allow the instance in another availability zone to handle the relevant requests in replace of the failed instance.
Migrating an instance to another availability zone
Once an instance is started, its availability zone cannot be changed. However you can migrate it to another availability zone.
- Create a custom image for the instance (see Create Custom Image).
- If the instance is using Virtual Private Cloud and you want to keep the private IP address after the migration, you can first delete the subnet in the current availability zone and then create a subnet in the new availability zone with the same IP address range as that of the original subnet. Please note that a subnet can be deleted only when it contains no available instances. Thus, all the instances in the current subnet should be migrated to the new subnet.
- Create a new instance in the new availability zone using the custom image you have just created. User can choose the same type and configuration as those of the original instance, or choose new ones.(see Purchase and Start an Instance).
- If an elastic IP address is associated with the original instance, then dissociate it from the old instance and associate it with the new instance (see Elastic IP).
- (Optional) For postpaid instances, you can terminate them manually (see Terminate an Instance). Prepaid instances will be reclaimed automatically after expiration.
How do I select the region and availability zone?
While purchasing Tencent Cloud services, it is recommended to choose the region that is closest to your customers to minimize the access latency and improve download speed.
Specify which resources of Tencent Cloud are global, which resources are regional and not specific to any availability zone and which resources are based on availability zones.
|Resource||Resource ID Format||Availability||Description|
|User ID||Not limited||Cross-region||Each Tencent Cloud user account is unique and applicable to all resources under the account.|
|SSH key||skey-xxxxxxxx||Cross-region||You can bind an SSH key pair to any CVM in any region under your account.|
|CVM instance||ins-xxxxxxxx||One zone only||A CVM instance is created under a specified availability zone|
|Custom Image||img-xxxxxxxx||Cross-zone||A custom image can be used in different availability zones of the same region. You can copy an image to another region.|
|Elastic IP||eip-xxxxxxxx||Cross-zone||An EIP is created under a specified region, and can only be associated with instance in the same region.|
|Security Group||sg-xxxxxxxx||Cross-zone||A security Group is created under a specified region, and can only be associated with instance in the same region.|
|(Elastic) Cloud Disk||disk-xxxxxxxx||Cross-zone||Elastic cloud disks can be created independently under a certain region and mounted to instances in the same region.|
|Cloud Load Balance||clb-xxxxxxxx||Cross-zone||Cloud Load Balance can bind to CVMs in different availability zones in a single region for forwarding traffic.|
|Virtual Private Cloud (VPC)||vpc-xxxxxxxx||Cross-zone||VPC is created under a certain region. Resources belonging to the same VPC can be created under different availability zones|
|Subnet||subnet-xxxxxxxx||One zone only||Users cannot create a subnet across availability zones.|
|Routing table||rtb-xxxxxxxx||Cross-zone||When creating a routing table, users need to designate a specific VPC, and therefore location attribute of the VPC should be followed.|