To provide better quality of service, the ApsaraMQ for RocketMQ HTTP service will no longer accept connections from Elastic Compute Service (ECS) instances in the classic network after May 31, 2021. Migrate affected applications to a virtual private cloud (VPC) before this date to avoid service disruption.
Who is affected
This change applies if your application meets both of the following conditions:
Deployed on an ECS instance in the classic network.
Accesses ApsaraMQ for RocketMQ over HTTP.
Applications already running in a VPC are not affected.
What to expect after May 31, 2021
After May 31, 2021, HTTP requests from classic network ECS instances to ApsaraMQ for RocketMQ will fail. Migrate before this date to prevent disruption to your applications.
Migrate to a VPC
Move your application to an ECS instance in a VPC. For step-by-step instructions, see Migrate ECS instances from the classic network to a VPC.
Get help
If you have questions during the migration, submit a ticket to contact Customer Services.