Starting July 31, 2021, ApsaraMQ for RocketMQ no longer supports cross-region access over HTTP. If your client connects to an instance through an HTTP endpoint in a different region, update your configuration before this date to avoid service disruption.
What changed
After July 31, 2021, each ApsaraMQ for RocketMQ instance can only be accessed through an HTTP endpoint in the same region where the instance is deployed. Cross-region HTTP access no longer works.
Required action
Update your client configuration so that the HTTP endpoint matches the region where your ApsaraMQ for RocketMQ instance is deployed.
For example, if your instance is in the China (Hangzhou) region:
Client location | Recommended endpoint | Notes |
In the China (Hangzhou) region | Private HTTP endpoint of the China (Hangzhou) region | Lower latency. No Internet access required. |
Outside the China (Hangzhou) region | Public HTTP endpoint of the China (Hangzhou) region | The client must have Internet access. |
In both cases, the endpoint must belong to the same region as the instance.