tencent cloud

Feedback

Regions and Availability Zones

Last updated: 2022-02-09 15:32:40

    Regions

    Overview

    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.

    Characteristics

    • The networks of different regions are fully isolated. Tencent Cloud services in different regions cannot communicate via a private network by default.
    • Tencent Cloud services across regions can communicate with each other through public IPs over the Internet, while those in different VPCs can communicate with each other through CCN, which is faster and more stable.
    • [Cloud Load Balancer (CLB)(https://intl.cloud.tencent.com/document/product/214) currently supports intra-region traffic forwarding by default. If you enable the Cross-Region Binding 2.0 (New) feature, cross-region binding of CLB and CVM instances is supported.

    Availability Zone

    Overview

    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 failures within an availability zone can be isolated (except for large-scale disaster or major power failure) without spreading to other zones, so as to ensure your business stability. 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.
    You can view the following table or use the DescribeZones API to get a complete availability zone list.

    Characteristics

    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.

    Note:

    Private network interconnection refers to the interconnection of resources under the same account. Resources under different accounts are completely isolated on the private network.

    China

    Region AZ
    South China (Guangzhou)
    ap-guangzhou
    Guangzhou Zone 1 (sold out)
    ap-guangzhou-1
    Guangzhou Zone 2 (sold out)
    ap-guangzhou-2
    Guangzhou Zone 3
    ap-guangzhou-3
    Guangzhou Zone 4
    ap-guangzhou-4
    Guangzhou Zone 6
    ap-guangzhou-6
    Guangzhou Zone 7
    ap-guangzhou-7
    East China (Shanghai)
    ap-shanghai
    Shanghai Zone 1
    ap-shanghai-1
    Shanghai Zone 2
    ap-shanghai-2
    Shanghai Zone 3
    ap-shanghai-3
    Shanghai Zone 4
    ap-shanghai-4
    Shanghai Zone 5
    ap-shanghai-5
    East China (Nanjing)
    ap-nanjing
    Nanjing Zone 1
    ap-nanjing-1
    Nanjing Zone 2
    ap-nanjing-2
    Nanjing Zone 3
    ap-nanjing-3
    North China (Beijing)
    ap-beijing
    Beijing Zone 1
    ap-beijing-1
    Beijing Zone 2
    ap-beijing-2
    Beijing Zone 3
    ap-beijing-3
    Beijing Zone 4
    ap-beijing-4
    Beijing Zone 5
    ap-beijing-5
    Beijing Zone 6
    ap-beijing-6
    Beijing Zone 7
    ap-beijing-7
    Southwest China (Chengdu)
    ap-chengdu
    Chengdu Zone 1
    ap-chengdu-1
    Chengdu Zone 2
    ap-chengdu-2
    Southwest China (Chongqing)
    ap-chongqing
    Chongqing Zone 1
    ap-chongqing-1
    Hong Kong, Macao and Taiwan, China (Hong Kong)
    ap-hongkong
    Hong Kong Zone 1 (Nodes in Hong Kong, China can cover services in Hong Kong/Macao/Taiwan regions)
    ap-hongkong-1
    Hong Kong Zone 2 (Nodes in Hong Kong, China can cover services in Hong Kong/Macao/Taiwan regions)
    ap-hongkong-2
    Hong Kong Zone 3 (Nodes in Hong Kong, China can cover Hong Kong/Macao/Taiwan regions)
    ap-hongkong-3

    Other countries and regions

    Region AZ
    Southeast Asia (Singapore)
    ap-singapore
    Singapore Zone 1 (Nodes in Singapore can cover Southeast Asia)
    ap-singapore-1
    Singapore Zone 2 (Nodes in Singapore can cover Southeast Asia)
    ap-singapore-2
    Singapore Zone 3 (Nodes in Singapore can cover Southeast Asia)
    ap-singapore-3
    Northeast Asia (Seoul)
    ap-seoul
    Seoul Zone 1 (Nodes in Seoul can cover Northeast Asia)
    ap-seoul-1
    Seoul Zone 2 (Nodes in Seoul can cover Northeast Asia)
    ap-seoul-2
    Northeast Asia (Tokyo)
    ap-tokyo
    Tokyo Zone 1 (Nodes in Tokyo can cover Northeast Asia)
    ap-tokyo-1
    Tokyo Zone 2 (Nodes in Tokyo can cover Northeast Asia)
    ap-tokyo-2
    South Asia (Mumbai)
    ap-mumbai
    Mumbai Zone 1 (Nodes in Mumbai can cover South Asia)
    ap-mumbai-1
    Mumbai Zone 2 (Nodes in Mumbai can cover South Asia)
    ap-mumbai-2
    Southeast Asia (Bangkok)
    ap-bangkok
    Bangkok Zone 1 (Nodes in Bangkok can cover Southeast Asia)
    ap-bangkok-1
    Bangkok Zone 2 (Nodes in Bangkok can cover Southeast Asia)
    ap-bangkok-2
    North America (Toronto)
    na-toronto
    Toronto Zone 1 (Nodes in Toronto can cover North America)
    na-toronto-1
    Western US (Silicon Valley)
    na-siliconvalley
    Silicon Valley Zone 1 (Nodes in Silicon Valley can cover Western US)
    na-siliconvalley-1
    Silicon Valley Zone 2 (Nodes in Silicon Valley can cover Western US)
    na-siliconvalley-2
    Eastern US (Virginia)
    na-ashburn
    Virginia Zone 1 (Nodes in Virginia can cover Eastern US)
    na-ashburn-1
    Virginia Zone 2 (Nodes in Virginia can cover Eastern US)
    na-ashburn-2
    Europe (Frankfurt)
    eu-frankfurt
    Frankfurt Zone 1 (Nodes in Frankfurt can cover Europe)
    eu-frankfurt-1
    Frankfurt Zone 2 (Nodes in Frankfurt can cover Europe)
    eu-frankfurt-2
    Europe (Moscow)
    eu-moscow
    Moscow Zone 1 (Nodes in Moscow can cover Europe)
    eu-moscow-1

    How to select the region and availability zone

    When selecting a region and availability zone, take the following into consideration:

    • Your location, the location of your users, and the region of the CVM instances.
      We recommend that you choose the region closest to your end users when purchasing CVM instances to minimize access latency and improve access speed.
    • Other Tencent Cloud services you use.
      When you select other Tencent Cloud services, we recommend you try to locate them all in the same region and availability zone to allow them to communicate with each other through the private network, reducing access latency and increasing access speed.
    • High availability and disaster recovery.
      Even if you have just one VPC, we still recommend that you deploy your businesses in different availability zones to prevent a single point of failure and enable cross-AZ disaster recovery.
    • There may be network latency among different availability zones. We recommend that you assess your business requirements and find the optimal balance between high availability and low latency.

    Resource Availability

    The following table describes which Tencent Cloud resources are global, which are regional, and which are specific to availability zones.

    ResourceResource ID Format
    -8-Digit String of Numbers and Letters
    TypeDescription
    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 Users can only create a CVM instance in a specific AZ.
    Custom Images img-xxxxxxxx Regional Users can create custom Image for instances which can be used in different availability zones of the same region Please copy custom image to other regions using the copy image function to use it in those regions.
    EIPs eip-xxxxxxxx Can be used in multiple AZs in a region EIPs (Elastic IPs) can only be created in a region and be associated with instances in the same region.
    Security Groups sg-xxxxxxxx Can be used in multiple AZs in a region Security Group is created under a certain region, and can only be associated with instance in the same region. Tencent Cloud automatically creates 3 default Security Groups for users.
    Cloud Block Storage disk-xxxxxxxx CBS disks 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 Can be used in multiple AZs in a region 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 Can be used in multiple AZs in a region Cloud Load Balancer can be bound with CVMs in different availability zones of a single region for traffic forwarding.
    VPC vpc-xxxxxxxx Available in multiple availability zones of a single region A VPC in one region can have resources created in different availability zones of the region.
    Subnets subnet-xxxxxxxx Subnets are specific to an availability zone. Users cannot create subnets across availability zones.
    Route Tables rtb-xxxxxxxx Can be used in multiple AZs in a region When creating a route table, users need to specify a VPC. Therefore, route tables are regional as well.

    References

    Migrating an instance to another availability zone

    For an instance that is already started, its availability zone cannot be changed, but its user can migrate it to another availability zone by other means. The migration process involves creating a custom image from the original instance, using the custom image to start an instance in a new availability zone and updating the configuration of the new instance.

    1. Create a custom image for the source instance. Creating Custom Images
    2. If the network environment of the current instance is VPC and the private IP address must be retained after migration, you need to 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 instance. Thus, all the instances in the current subnet should be migrated to the new subnet.
    3. Create a new instance in the new AZ by using the created custom image. You can choose the same type and configuration as those of the original instance, or choose new ones. For more information, see Creating Instances via CVM Purchase Page.
    4. If the source instance is associated with an EIP, disassociate the EIP and associate it with the new instance. For more information about shutting down an instance, please see Shutdown Instances.
    5. For more information, see Terminating Instances.

    Copying images to other regions

    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. Copying Images

    Contact Us

    Contact our sales team or business advisors to help your business.

    Technical Support

    Open a ticket if you're looking for further assistance. Our Ticket is 7x24 avaliable.

    7x24 Phone Support