A region is a physical data center. After you create a resource, you cannot change its region. This topic describes the regions supported by ApsaraMQ for MQTT.
In the following tables, 
indicates that a feature is supported in a region, and 
indicates that it is not supported in that region.
Instance regions
Region name | Region ID | Serverless instance | Subscription instance | ||
Professional Edition | Platinum Edition | Basic Edition | |||
China (Shanghai) | cn-shanghai |
|
|
|
|
China (Hong Kong) | cn-hongkong |
|
|
|
|
Singapore | ap-southeast-1 |
|
|
|
|
Malaysia (Kuala Lumpur) | ap-southeast-3 |
|
|
|
|
Indonesia (Jakarta) | ap-southeast-5 |
|
|
|
|
Philippines (Manila) | ap-southeast-6 |
|
|
|
|
Japan (Tokyo) | ap-northeast-1 |
|
|
|
|
Germany (Frankfurt) | eu-central-1 |
|
|
|
|
US (Silicon Valley) | us-west-1 |
|
|
|
|
US (Virginia) | us-east-1 |
|
|
|
|
SAU (Riyadh - Partner Region) | me-central-1 |
|
|
|
|
SDK access regions
Region name | Region ID | Client SDK access | Cloud SDK access |
China (Shanghai) | cn-shanghai |
|
|
China (Hong Kong) | cn-hongkong |
|
|
Singapore | ap-southeast-1 |
|
|
Malaysia (Kuala Lumpur) | ap-southeast-3 |
|
|
Indonesia (Jakarta) | ap-southeast-5 |
|
|
Philippines (Manila) | ap-southeast-6 |
|
|
Japan (Tokyo) | ap-northeast-1 |
|
|
Germany (Frankfurt) | eu-central-1 |
|
|
US (Silicon Valley) | us-west-1 |
|
|
US (Virginia) | us-east-1 |
|
|
SAU (Riyadh - Partner Region) | me-central-1 |
|
|