Regions refer to the geographical areas of physical data centers. Availability zones (AZs) are physically independent data centers within the same Tencent Cloud region, with separate power and network resources. For more information, see CVM - Regions and AZs. Supported Regions
Regions in the Chinese Mainland
|
South China | Guangzhou | ap-guangzhou | ✓ | ✓ |
| Shenzhen Finance | ap-shenzhen-fsi | × | ✓ |
East China | Nanjing | ap-nanjing | ✓ | ✓ |
| Shanghai | ap-shanghai | ✓ | ✓ |
| Shanghai Finance | ap-shanghai-fsi | × | ✓ |
| Shanghai Autonomous Driving Cloud | ap-shanghai-adc | × | ✓ |
Hong Kong (China), Macao (China), and Taiwan (China) | Hong Kong (China) | ap-hongkong | × | ✓ |
| Taipei (China) | ap-taibei | × | ✓ |
North China | Beijing | ap-beijing | × | ✓ |
Southwest China | Chengdu | ap-chengdu | × | ✓ |
| Chongqing | ap-chongqing | × | ✓ |
Other Countries and Regions
|
Southeast Asia | Singapore | ap-singapore | × | ✓ |
| Bangkok | ap-bangkok | × | ✓ |
| Jakarta | ap-jakarta | × | ✓ |
Northeast Asia-Pacific | Seoul | ap-seoul | ✓ | ✓ |
| Tokyo | ap-tokyo | × | ✓ |
Western United States | Silicon Valley | na-siliconvalley | × | ✓ |
Eastern United States | Virginia | na-ashburn | × | ✓ |
Europe | Frankfurt | eu-frankfurt | × | ✓ |
South America | São Paulo | sa-saopaulo | × | ✓ |
How to Select Regions and AZs
When you select regions and availability zones (AZs), the following factors need to be considered:
The region of your TDMQ for RabbitMQ cluster, your own location, and the location of your target users. We recommend that you select the region closest to your customers when you purchase a TDMQ for RabbitMQ cluster to reduce access latency and improve access speed.
The relationship between TDMQ for RabbitMQ and other cloud products. We recommend that you deploy other cloud products in the same region and AZ whenever possible. This allows different cloud products to communicate over the private network, reducing access latency and improving access speed.
High availability and disaster recovery considerations for your business. Even in scenarios with only one VPC, we recommend that you deploy your business across at least different AZs to ensure fault isolation between AZs and achieve cross-AZ disaster recovery.
Possible network communication latency between availability zones. Evaluate it based on your actual business requirements to find the optimal balance between high availability and low latency.