Regions and Availability Zones
Last updated: 2019-10-15 10:40:45PDF
A region is the physical location of the IDC. In Tencent Cloud, different regions are fully isolated, ensuring the maximal stability and fault tolerance among those regions. To reduce access latency and increase download speeds, we recommend you select the region nearest to your customers.
You can view the following table or use the DescribeRegions API to view the complete list of regions.
- The networks of different regions are fully isolated from each other, and Tencent Cloud products of different regions cannot communicate via private network by default.
- Tencent Cloud products of different regions can access the Internet through Public IP. Tencent Cloud products in VPCs can also communicate with each other by using Peering Connection provided by Tencent Cloud through Tencent Cloud’s high-speed connected network, to implement connectivity that is more stable and faster than Internet access.
- Cloud Load Balancer currently supports intra-region traffic forwarding, and binding of CVMs in the same region. If the cross-region binding function is enabled, then binding CVMs to the Cloud Load Balancer across regions is supported.
Availability zones refer to Tencent Cloud physical IDCs in the same region with independent power and network resources. They are designed to ensure that the failures within an availability zone can be isolated (except for large-scale disaster or major power failure) without spreading to and affecting other zones, so as to ensure users' business stability. By starting an instance in an independent availability zone, users can protect their applications from being affected by failures that occur in a single location.
You can view the following table or use the DescribeZones API to view the complete list of availability zones.
Tencent Cloud products that are in the same region and different availability zones, but in the same VPC, are interconnected through private network. they can be accessed directly through the private IP.
Private network interconnection refers to the interconnection of resources under the same account. Private networks for resources under different accounts are completely isolated.
|South China (Guangzhou)
|Guangzhou Zone 1 (sold out)
|Guangzhou Zone 2
|Guangzhou Zone 3
|Guangzhou Zone 4
|East China (Shanghai)
|Shanghai Zone 1
|Shanghai Zone 2
|Shanghai Zone 3
|Shanghai Zone 4
|North China (Beijing)
|Beijing Zone 1
|Beijing Zone 2
|Beijing Zone 3
|Beijing Zone 4
|Southwest China (Chengdu)
|Chengdu Zone 1
|Chengdu Zone 2
|Southwest China (Chongqing)
|Chongqing Zone 1
|Hong Kong/Macao/Taiwan (Hong Kong, China)
|Hong Kong Zone 1 (Nodes in Hong Kong, China can cover Hong Kong/Macao/Taiwan)
|Hong Kong Zone 2 (Nodes in Hong Kong, China can cover Hong Kong/Macao/Taiwan)
Other Countries and Regions
|Southeast Asia Pacific (Singapore)
|Singapore Zone 1 (Nodes in Singapore can cover Southeast Asia Pacific)
|Northeast Asia Pacific (Seoul)
|Seoul Zone 1 (Nodes in Seoul can cover Northeast Asia Pacific)
|Northeast Asia Pacific (Tokyo)
|Tokyo Zone 1 (Nodes in Tokyo can cover Northeast Asia Pacific)
|South Asia Pacific (Mumbai)
|Mumbai Zone 1 (Nodes in Mumbai can cover South Asia Pacific)
|Mumbai Zone 2 (Nodes in Mumbai can cover South Asia Pacific)
|Southeast Asia Pacific (Bangkok)
|Bangkok Zone 1 (Nodes in Bangkok cover Southeast Asia Pacific)
|North America (Toronto)
|Toronto Zone 1 (Nodes in Toronto can cover North America)
|West US (Silicon Valley)
|Silicon Valley Zone 1 (Nodes in Silicon Valley can cover West US)
|Silicon Valley Zone 2 (Nodes in Silicon Valley can cover West US)
|East US (Virginia)
|Virginia Zone 1 (Nodes in Virginia can cover East US)
|Virginia Zone 2 (Nodes in Virginia can cover East US)
|Frankfurt Zone 1 (Nodes in Frankfurt can cover Europe)
|Moscow Zone 1 (Nodes in Moscow can cover Europe)
How to Select the Region and Availability Zone
When selecting the region and availability zone, you must take the following factors into consideration:
- The region where the CVM is located, your location, and the location of your users.
We recommend that when you purchase CVMs, you choose the region that is closest to your users to minimize the access latency and improve access speed.
- The relationship between CVMs and other Tencent Cloud products.
We recommend that when you select other Tencent Cloud products, you try to make them all in the same region and availability zone to allow them communicate with each other through the private network, reducing access latency and increasing access speeds.
- Considerations for high reliability and disaster recovery of businesses.
Even in a scenario where there is only one VPC, we still recommend that you deploy businesses in different availability zones to guarantee failure isolation between availability zones and to implement cross-AZ disaster recovery.
- There may be a network communication delay between different availability zones, so you need to make an assessment based on the actual requirements of the businesses to find the optimal balance point between high availability and low delay.
- If you need to access CVMs in other countries or regions, we recommend you select a CVM in other countries or regions for access. If you create a CVM in Mainland China and access servers in other countries and regions there will be relatively high access delay. We do not recommend you do this.
Resource Location Description
The following table specifies 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||Type||Description|
|User Account||No limit||Globally unique||Users can use the same account to access Tencent Cloud resources from around the world.|
|SSH Key||skey-xxxxxxxx||Globally available||Users can use the SSH key to bind a CVM in any region under the account.|
|CVM Instance||ins-xxxxxxxx||This can only be used under one availability zone in one region.||Users can only create CVM instances in a specific availability zones.|
|Custom Images||img-xxxxxxxx||Available in a single region and multiple availability zones||Users can create a custom image for instances, which can be used in different availability zones of the same region. Copy the custom image to other regions using the **Copy Image** feature to use it in those regions.|
|Elastic IP||eip-xxxxxxxx||Available in a single region and multiple availability zones||Elastic IP address is created under a certain region, and can only be associated with instances in the same region.|
|Security Group||sg-xxxxxxxx||Available in a single region and multiple availability zones||Security Group is created under a certain region, and can only be associated with instances in the same region. Tencent Cloud automatically creates three default security groups for users.|
|Cloud Block Storage||disk-xxxxxxxx||This can only be used under one availability zone in one region.||Users can only create a Cloud Block Storage in a specific availability zone, and can mount it on instances in the same availability zone.|
|Snapshots||snap-xxxxxxxx||Available in a single region and multiple availability zones||After creating snapshot for a specific cloud disk, users can use this snapshot in this region for other operations (such as creating cloud disk).|
|Cloud Load Balancer||clb-xxxxxxxx||Available in a single region and multiple availability zones||Cloud Load Balancer can be bound with CVMs in different availability zones in a single region for traffic forwarding.|
|VPC||vpc-xxxxxxxx||Available in a single region and multiple availability zones||A VPC is created under a certain region. You can create resources in different AZs but in the same VPC.|
|Subnet||subnet-xxxxxxxx||This can only be used under one availability zone in one region.||Users cannot create subnets across availability zones.|
|Route Table||rtb-xxxxxxxx||Available in a single region and multiple availability zones||When creating a route table, users need to specify a specific VPC. Thus, the location attribute of the VPC should be followed.|
Migrating an Instance to Another Availability Zone
For a launched instance, its availability zone cannot be changed. But you can migrate it to another availability zone through other means. The migration process involves creating a custom image using the original instance, using the custom image to launch an instance in a new availability zone and updating the configuration of the new instance.
- Create a custom image for the current instance. For more information, see Creating a Custom Image.
- If the network environment of the current instance is VPC and the private IP address needs to be retained 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 by using the custom image you have just created. You can choose the same type and configuration as those of the original instance, or choose new ones. For more information, see Purchasing and Launching Instances.
- If an Elastic IP is associated with the original instance, dissociate it from the old instance and associate it with the new instance. For more information, see Elastic IP.
- (Optional) If the original instance is billed on a Pay-as-you-go basis, then you can choose to terminate the original instance. For more information, see Terminating Instances.
Copying Images to Other Regions
Actions such as launching and viewing instances have region attributes. If the image of the instance that you need to launch does not exist in the region, the image needs to be copied to the current region. For more information, see Copying Images.