A region is the physical location of an IDC. In Tencent Cloud, regions are fully isolated from each other, ensuring cross-region stability and fault tolerance. We recommend that you choose the region closest to your end users to minimize access latency and improve access speed.
You can view the following table or use the DescribeRegions API to get a complete region list.
An availability zone (AZ) is a physical IDC of Tencent Cloud with independent power supply and network in the same region. It can ensure business stability, as failures (except for major disasters or power failures) in one AZ are isolated without affecting other AZs in the same region. By starting an instance in an independent availability zone, users can protect their applications from being affected by a single point of failure.
You can view the following table or use the DescribeZones API to get a complete availability zone list.
Tencent Cloud services in the same VPC are interconnected via the private network, which means they can communicate using private IPs, even if they are in different availability zones of the same region.
Private network interconnection refers to the interconnection of resources under the same account. Resources under different accounts are completely isolated on the private network.
|South China (Guangzhou)
|Guangzhou Zone 3
|Guangzhou Zone 4
|Guangzhou Zone 6
|East China (Shanghai)
|Shanghai Zone 2
|Shanghai Zone 3
|Shanghai Zone 4
|Shanghai Zone 5
|East China (Nanjing)
|Nanjing Zone 1
|Nanjing Zone 2
|North China (Beijing)
|Beijing Zone 3
|Beijing Zone 4
|Beijing Zone 5
|Beijing Zone 6
|Beijing Zone 7
|Southwest China (Chengdu)
|Chengdu Zone 1
|Chengdu Zone 2
|Hong Kong, Macao and Taiwan, China (Hong Kong)
|Hong Kong Zone 2 (Nodes in Hong Kong, China can cover Hong Kong/Macao/Taiwan regions)
|Southeast Asia (Singapore)
|Singapore Zone 1 (Nodes in Singapore can cover Southeast Asia)
|Singapore Zone 2 (Nodes in Singapore can cover Southeast Asia)
|Southeast Asia (Jakarta)
|Jakarta Zone 1 (Nodes in Jakarta can cover Southeast Asia)
|Northeast Asia (Seoul)
|Seoul Zone 1 (Nodes in Seoul can cover Northeast Asia)
|Seoul Zone 2 (Nodes in Seoul can cover Northeast Asia)
|Northeast Asia (Tokyo)
|Tokyo Zone 2 (Tokyo nodes can cover services in Northeast Asia)
|South Asia (Mumbai)
|Mumbai Zone 1 (Nodes in Mumbai can cover South Asia)
|Mumbai Zone 2 (Nodes in Mumbai can cover South Asia)
|Southeast Asia (Bangkok)
|Bangkok Zone 1 (Nodes in Bangkok can cover Southeast Asia)
|North America (Toronto)
|Toronto Zone 1 (Nodes in Toronto can cover North America)
|Eastern US (Virginia)
|Virginia Zone 1 (Nodes in Virginia can cover Eastern US)
|Virginia Zone 2 (Nodes in Virginia can cover Eastern US)
|Frankfurt Zone 1 (Nodes in Frankfurt can cover Europe)
|Moscow Zone 1 (Nodes in Moscow can cover Europe)
When selecting a region and availability zone, take the following into consideration:
The following table describes which Tencent Cloud resources are global, which are regional, and which are specific to 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 around the world.|
|SSH Keys||skey-xxxxxxxx||Global||Users can use an SSH key to bind a CVM in any region under the account.|
|CVM Instances||ins-xxxxxxxx||CVM instances are specific to an availability zone.||A CVM instance created in an availability zone is not available to other availability zones.|
|Custom Images||img-xxxxxxxx||Regional||Custom images created for the instance are available to all availability zones of the same region. Use Copy Image to copy a custom image if you need to use it in other regions.|
|EIPs||eip-xxxxxxxx||Regional||EIPs can only be associated with instances in the same region.|
|Security Groups||sg-xxxxxxxx||Regional||Security group 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||CVM instances are specific to an availability zone.||Users can only create a Cloud Block Storage disk in a specific AZ and mount it to instances in the same availability zone.|
|Snapshots||snap-xxxxxxxx||Regional||A snapshot created from a cloud disk can be used for other purposes (such as creating cloud disks) in this region.|
|Cloud Load Balancer||clb-xxxxxxxx||Regional||Cloud Load Balancer can be bound with CVMs in different availability zones of a single region for traffic forwarding.|
|VPC||vpc-xxxxxxxx||Regional||A VPC in one region can have resources created in different availability zones of the region.|
|Subnets||subnet-xxxxxxxx||CVM instances are specific to an availability zone.||Users cannot create subnets across availability zones.|
|Route Tables||rtb-xxxxxxxx||Regional||When creating a route table, users need to specify a VPC. Therefore, route tables are regional as well.|
Once launched, an instance cannot be migrated. However, you can create a custom image of your CVM instance and use the image to launch or update an instance in a different availability zone.
Operations such as launching and viewing instances are region-specific. If the image of the instance that you need to launch does not exist in the region, copy the image to the desired region. For more information, see Copying Images.