Regions are geographical locations where data centers reside. After you create a resource, you cannot change the region where the resource resides. This topic describes the regions that are supported by ApsaraMQ for RocketMQ.
Geographic region | Region | Region ID | TCP endpoint | HTTP endpoint |
Asia Pacific | China (Hangzhou) | cn-hangzhou |
|
|
China (Shanghai) | cn-shanghai |
|
| |
China (Qingdao) | cn-qingdao |
|
| |
China (Beijing) | cn-beijing |
|
| |
China (Zhangjiakou) | cn-zhangjiakou |
|
| |
China (Hohhot) | cn-huhehaote |
|
| |
China (Shenzhen) | cn-shenzhen |
|
| |
China (Chengdu) | cn-chengdu |
|
| |
China (Hong Kong) | cn-hongkong |
|
| |
Japan (Tokyo) | ap-northeast-1 |
|
| |
Singapore | ap-southeast-1 |
|
| |
Malaysia (Kuala Lumpur) | ap-southeast-3 |
|
| |
Indonesia (Jakarta) | ap-southeast-5 |
|
| |
Philippines (Manila) | ap-southeast-6 |
| To be supported | |
Europe & Americas | Germany (Frankfurt) | eu-central-1 |
|
|
UK (London) | eu-west-1 |
|
| |
US (Virginia) | us-east-1 |
|
| |
US (Silicon Valley) | us-west-1 |
|
| |
Middle East | SAU (Riyadh - Partner Region) | me-central-1 |
|
|
UAE (Dubai) | me-east-1 |
| To be supported |
indicates that the feature is supported in the region.