ApsaraMQ for RocketMQ 4.x is available in 20 regions across Asia Pacific, Europe & Americas, and the Middle East. Each region is an independent physical data center. After you create a resource in a region, you cannot move it to a different region.
TCP and HTTP endpoints are available in most regions. Two regions support TCP only.
Asia Pacific
|
Region |
Region ID |
TCP endpoint |
HTTP endpoint |
|
China (Hangzhou) |
cn-hangzhou |
Supported |
Supported |
|
China (Shanghai) |
cn-shanghai |
Supported |
Supported |
|
China (Qingdao) |
cn-qingdao |
Supported |
Supported |
|
China (Beijing) |
cn-beijing |
Supported |
Supported |
|
China (Zhangjiakou) |
cn-zhangjiakou |
Supported |
Supported |
|
China (Hohhot) |
cn-huhehaote |
Supported |
Supported |
|
China (Shenzhen) |
cn-shenzhen |
Supported |
Supported |
|
China (Chengdu) |
cn-chengdu |
Supported |
Supported |
|
China (Hong Kong) |
cn-hongkong |
Supported |
Supported |
|
Japan (Tokyo) |
ap-northeast-1 |
Supported |
Supported |
|
Singapore |
ap-southeast-1 |
Supported |
Supported |
|
Malaysia (Kuala Lumpur) |
ap-southeast-3 |
Supported |
Supported |
|
Indonesia (Jakarta) |
ap-southeast-5 |
Supported |
Supported |
|
Philippines (Manila) |
ap-southeast-6 |
Supported |
To be supported |
Europe & Americas
|
Region |
Region ID |
TCP endpoint |
HTTP endpoint |
|
Germany (Frankfurt) |
eu-central-1 |
Supported |
Supported |
|
UK (London) |
eu-west-1 |
Supported |
Supported |
|
US (Virginia) |
us-east-1 |
Supported |
Supported |
|
US (Silicon Valley) |
us-west-1 |
Supported |
Supported |
Middle East
|
Region |
Region ID |
TCP endpoint |
HTTP endpoint |
|
SAU (Riyadh - Partner Region) |
me-central-1 |
Supported |
Supported |
|
UAE (Dubai) |
me-east-1 |
Supported |
To be supported |
Indicates that the feature is supported in the region.