Since the Alibaba Cloud public cloud was released in 2011, the classic network architecture is used to host Elastic Compute Service (ECS) instances and serve numerous users in the cloud. In 2014, Alibaba Cloud released Virtual Private Cloud (VPC)-based cloud services, which are more secure, consistent, flexible, and performant than classic network-based cloud services. After years of development, the VPC network architecture has increasingly become the default choice of Alibaba Cloud users. Against this backdrop, ApsaraDB for Redis starts the end-of-life (EOL) process for ApsaraDB for Redis instances in the classic network.
To help minimize the impacts on your workloads, Alibaba Cloud provides sufficient time prior to the EOL date to allow you to devise, test, and execute the plan for migrating ApsaraDB for Redis instances from the classic network to VPCs. Alibaba Cloud provides necessary tools, documentation, and service personnel to assist in your migration.
Dates and impacts
End of cloning, renewal, and configuration change on October 30, 2024
Starting October 30, 2024, you cannot clone, renew, or change the specifications of ApsaraDB for Redis instances in the classic network.
EOL on February 28, 2025
On February 28, 2025, all ApsaraDB for Redis instances of the classic network type will be shut down. All business applications running on these instances will be terminated.
For ApsaraDB for Redis instances that allow hybrid access to the classic network and VPCs, the classic network endpoints will automatically become invalid and the VPC endpoints will remain operational. Any usage restrictions imposed from the October 30, 2024 timeline will be removed.
All ApsaraDB for Redis instances deployed solely in VPCs will not be affected by the aforementioned changes.
If you switch the network type of your ApsaraDB for Redis instances from classic network to VPC before the preceding dates, these instances will not be affected by the aforementioned changes.
Query the affected ApsaraDB for Redis instances
You can use the console or API to query the ApsaraDB for Redis instances of the classic network type.
Use the console
Log on to the ApsaraDB for Redis console and go to the Instances page. In the top navigation bar, select the region in which the instance that you want to manage resides. Then, find the instance and click the instance ID.
In the Basic Information section, check that the Network parameter is set to Classic Network.
Use the API
You can call the DescribeInstances operation with the NetworkType parameter set to CLASSIC to query all instances of the classic network type in a region.
Suggestions
Make sure that you switch the network type of your ApsaraDB for Redis instances from classic network to VPC before the EOL date. This allows clients to communicate with the ApsaraDB for Redis instances over the same VPC, providing enhanced security and lower network latency. For more information, see Switch the network type from classic network to VPC.
If you configured hybrid access for your instances, make sure that the classic network access does not extend beyond the EOL date.