Since the Alibaba Cloud public cloud was released in 2011, the classic network architecture has been 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, Tair (Redis OSS-compatible) starts the end-of-life (EOL) process for instances deployed 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 Tair (Redis OSS-compatible) 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 renewal, configuration change, and billing method change on October 30, 2024
Starting October 30, 2024, you cannot renew or change the specifications or billing method of subscription instances deployed in the classic network.
EOL on February 28, 2025
On February 28, 2025, all instances deployed in the classic network will be shut down. All business applications that run on these instances will be terminated.
For 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 instances deployed solely in VPCs will not be affected by the aforementioned changes.
If you switch the network type of your instances from classic network to VPC before the preceding dates, these instances will not be affected by the aforementioned changes.
Query the affected instances
You can use the Tair (Redis OSS-compatible) console or call an API operation to query the instances deployed in the classic network.
Use the console
Log on to the 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 Tair (Redis OSS-compatible) instances from classic network to VPC before the EOL date. This allows clients to communicate with the 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, promptly release the classic network endpoints after you switch the network type. For more information about how to release a classic network endpoint, see Release a classic network endpoint.
FAQ
Is this notice related to the classic deployment mode?
This notice is not related to the classic deployment mode. Only instances deployed in the classic network are affected. Instances of the VPC network type are not affected.