Starting December 1, 2023, applications deployed on Elastic Compute Service (ECS) instances in the classic network can no longer access newly created ApsaraMQ for RocketMQ 4.x instances or topics through the TCP service. ApsaraMQ for RocketMQ resources for the classic network are sold out, and no additional capacity is available.
Who is affected
This change affects applications that meet all of the following conditions:
Deployed on ECS instances in the classic network
Access the TCP service of ApsaraMQ for RocketMQ 4.x instances
Need to connect to instances or topics created after November 30, 2023
Who is not affected
Applications in virtual private clouds (VPCs): VPC-based applications can access all ApsaraMQ for RocketMQ instances and topics without restrictions.
Existing resources: Applications in the classic network can still access ApsaraMQ for RocketMQ instances and topics created on or before November 30, 2023.
Required action
Migrate your applications from ECS instances in the classic network to ECS instances in a VPC. After migration, your applications can access all ApsaraMQ for RocketMQ 4.x instances and topics, including those created after November 30, 2023. If you do not migrate, your classic network applications cannot connect to any new ApsaraMQ for RocketMQ instances or topics.
For step-by-step instructions, see Migrate ECS instances from the classic network to a VPC.
Support
If you have questions about the migration process, submit a ticket to contact Alibaba Cloud technical support.