Elastic Compute Service (ECS) is available across multiple regions worldwide. Each region contains one or more isolated zones. The region and zone you choose affect network performance, service availability, and cost.
For general concepts, see Regions and zones. For a visual overview of global infrastructure, see the Global Infrastructure page.
Choose a region
Choose a region based on the following factors. If the wrong region is selected, create a new instance in the correct region and release the original. Alternatively, migrate the service using SMC.
| Factor | Description |
|---|---|
| Geographic proximity | Geographic distance is a key factor in network latency. Deploy resources in a region close to your end users to reduce latency and improve access speed. |
| Internal network communication | ECS and other cloud services in the same region communicate through a Virtual Private Cloud (VPC) network. Internal communication is faster than the public network and does not incur traffic fees. If a cloud network service is already in place to connect your services, this factor does not apply. |
| Cross-border access from China | ECS instances in China regions, including China (Hong Kong) and China (Macao), may experience high latency and packet loss when accessing instances in other countries and regions over the public network. Deploy services in the same region to avoid these issues. |
| Pricing | Resource prices vary by region. Some regions offer lower resource plan prices due to different discount policies. For current pricing, see the Instance buy page and the Pricing tab on the ECS product page. |
| Feature availability | New ECS features are often released as public previews in select regions. To try new features, create ECS instances in the specified regions. For details, see Release notes for ECS features. |
Choose a zone
A resource's zone cannot be changed after creation. To move an ECS instance to a different zone, see Change instance types across zones.
Zones within the same region are interconnected over an internal network. Each zone is independent, providing effective fault isolation -- incidents in one zone do not affect operations in another.
Distribute services across zones based on your disaster recovery and latency requirements:
High disaster recovery -- Deploy instances in different zones within the same region.
Low latency -- Deploy instances within the same zone.
A typical disaster recovery architecture uses multi-zone primary/secondary solutions for services like ECS and File Storage NAS (NAS).
Supported regions and zones
The following tables list all regions and zones supported by ECS. Other cloud services may support different regions and zones. Check the documentation of each service for details.
Regions in China
| Region name | Region ID | Zones | Zone name | Zone ID |
|---|---|---|---|---|
| China (Qingdao) | cn-qingdao | 2 | Qingdao Zone B | cn-qingdao-b |
| Qingdao Zone C | cn-qingdao-c | |||
| China (Beijing) | cn-beijing | 12 | Beijing Zone A | cn-beijing-a |
| Beijing Zone B | cn-beijing-b | |||
| Beijing Zone C | cn-beijing-c | |||
| Beijing Zone D | cn-beijing-d | |||
| Beijing Zone E | cn-beijing-e | |||
| Beijing Zone F | cn-beijing-f | |||
| Beijing Zone G | cn-beijing-g | |||
| Beijing Zone H | cn-beijing-h | |||
| Beijing Zone I | cn-beijing-i | |||
| Beijing Zone J | cn-beijing-j | |||
| Beijing Zone K | cn-beijing-k | |||
| Beijing Zone L | cn-beijing-l | |||
| China (Zhangjiakou) | cn-zhangjiakou | 3 | Zhangjiakou Zone A | cn-zhangjiakou-a |
| Zhangjiakou Zone B | cn-zhangjiakou-b | |||
| Zhangjiakou Zone C | cn-zhangjiakou-c | |||
| China (Hohhot) | cn-huhehaote | 2 | Hohhot Zone A | cn-huhehaote-a |
| Hohhot Zone B | cn-huhehaote-b | |||
| China (Ulanqab) | cn-wulanchabu | 3 | Ulanqab Zone A | cn-wulanchabu-a |
| Ulanqab Zone B | cn-wulanchabu-b | |||
| Ulanqab Zone C | cn-wulanchabu-c | |||
| China (Hangzhou) | cn-hangzhou | 8 | Hangzhou Zone B | cn-hangzhou-b |
| Hangzhou Zone E | cn-hangzhou-e | |||
| Hangzhou Zone F | cn-hangzhou-f | |||
| Hangzhou Zone G | cn-hangzhou-g | |||
| Hangzhou Zone H | cn-hangzhou-h | |||
| Hangzhou Zone I | cn-hangzhou-i | |||
| Hangzhou Zone J | cn-hangzhou-j | |||
| Hangzhou Zone K | cn-hangzhou-k | |||
| China (Shanghai) | cn-shanghai | 12 | Shanghai Zone A | cn-shanghai-a |
| Shanghai Zone B | cn-shanghai-b | |||
| Shanghai Zone C | cn-shanghai-c | |||
| Shanghai Zone D | cn-shanghai-d | |||
| Shanghai Zone E | cn-shanghai-e | |||
| Shanghai Zone F | cn-shanghai-f | |||
| Shanghai Zone G | cn-shanghai-g | |||
| Shanghai Zone K | cn-shanghai-k | |||
| Shanghai Zone L | cn-shanghai-l | |||
| Shanghai Zone M | cn-shanghai-m | |||
| Shanghai Zone N | cn-shanghai-n | |||
| Shanghai Zone O | cn-shanghai-o | |||
| China (Nanjing - Local Region) (Closing Down) | cn-nanjing | 1 | Nanjing - Local Region Zone A | cn-nanjing-a |
| China (Fuzhou - Local Region) (Closing Down) | cn-fuzhou | 1 | Fuzhou - Local Region Zone A | cn-fuzhou-a |
| China (Wuhan - Local Region) | cn-wuhan-lr | 1 | Wuhan - Local Region Zone A | cn-wuhan-lr-a |
| China (Shenzhen) | cn-shenzhen | 6 | Shenzhen Zone A | cn-shenzhen-a |
| Shenzhen Zone B | cn-shenzhen-b | |||
| Shenzhen Zone C | cn-shenzhen-c | |||
| Shenzhen Zone D | cn-shenzhen-d | |||
| Shenzhen Zone E | cn-shenzhen-e | |||
| Shenzhen Zone F | cn-shenzhen-f | |||
| China (Heyuan) | cn-heyuan | 2 | Heyuan Zone A | cn-heyuan-a |
| Heyuan Zone B | cn-heyuan-b | |||
| China (Guangzhou) | cn-guangzhou | 2 | Guangzhou Zone A | cn-guangzhou-a |
| Guangzhou Zone B | cn-guangzhou-b | |||
| China (Chengdu) | cn-chengdu | 2 | Chengdu Zone A | cn-chengdu-a |
| Chengdu Zone B | cn-chengdu-b | |||
| China (Hong Kong) | cn-hongkong | 3 | Hong Kong Zone B | cn-hongkong-b |
| Hong Kong Zone C | cn-hongkong-c | |||
| Hong Kong Zone D | cn-hongkong-d |
Regions outside China
| Region name | Region ID | Zones | Zone name | Zone ID |
|---|---|---|---|---|
| Singapore | ap-southeast-1 | 3 | Singapore Zone A | ap-southeast-1a |
| Singapore Zone B | ap-southeast-1b | |||
| Singapore Zone C | ap-southeast-1c | |||
| Malaysia (Kuala Lumpur) | ap-southeast-3 | 3 | Kuala Lumpur Zone A | ap-southeast-3a |
| Kuala Lumpur Zone B | ap-southeast-3b | |||
| Kuala Lumpur Zone C | ap-southeast-3c | |||
| Indonesia (Jakarta) | ap-southeast-5 | 3 | Jakarta Zone A | ap-southeast-5a |
| Jakarta Zone B | ap-southeast-5b | |||
| Jakarta Zone C | ap-southeast-5c | |||
| Philippines (Manila) | ap-southeast-6 | 2 | Manila Zone A | ap-southeast-6a |
| Manila Zone B | ap-southeast-6b | |||
| Thailand (Bangkok) | ap-southeast-7 | 2 | Bangkok Zone A | ap-southeast-7a |
| Bangkok Zone B | ap-southeast-7b | |||
| Japan (Tokyo) | ap-northeast-1 | 3 | Tokyo Zone A | ap-northeast-1a |
| Tokyo Zone B | ap-northeast-1b | |||
| Tokyo Zone C | ap-northeast-1c | |||
| South Korea (Seoul) | ap-northeast-2 | 2 | Seoul Zone A | ap-northeast-2a |
| Seoul Zone B | ap-northeast-2b | |||
| US (Silicon Valley) | us-west-1 | 2 | Silicon Valley Zone A | us-west-1a |
| Silicon Valley Zone B | us-west-1b | |||
| US (Virginia) | us-east-1 | 2 | Virginia Zone A | us-east-1a |
| Virginia Zone B | us-east-1b | |||
| Germany (Frankfurt) | eu-central-1 | 3 | Frankfurt Zone A | eu-central-1a |
| Frankfurt Zone B | eu-central-1b | |||
| Frankfurt Zone C | eu-central-1c | |||
| UK (London) | eu-west-1 | 2 | London Zone A | eu-west-1a |
| London Zone B | eu-west-1b | |||
| UAE (Dubai) | me-east-1 | 2 | Dubai Zone A | me-east-1a |
| Dubai Zone B | me-east-1b | |||
| SAU (Riyadh - Partner Region) | me-central-1 | 2 | Riyadh Zone A | me-central-1a |
| Riyadh Zone B | me-central-1b | |||
| Mexico | na-south-1 | 1 | Mexico Zone A | na-south-1a |
Query regions and zones
Query available regions
Call the DescribeRegions operation to query available ECS regions.
CLI example (replace {RegionId} with a valid region ID):
aliyun ecs DescribeRegions --region {RegionId}Query resources in a zone
Call the DescribeZones operation to query the zones and purchasable resources in a specified region.
CLI example (replace {RegionId} with a region ID from the tables above):
aliyun ecs DescribeZones --region {RegionId}Check instance type availability by region
Available instance types vary by region. To check which regions support a specific instance type, go to the Instance types available for each region page.
Regions and endpoints
An endpoint is the access domain name for an ECS service. ECS supports public endpoints and VPC endpoints. When integrating ECS through an SDK, the CLI, or an API, configure the correct endpoint. For endpoint details, see:
Resource management (instances, images, block storage): Endpoints of ECS API
Advanced block storage features: Endpoints of advanced block storage features