EOL notice for Tair (Redis OSS-compatible) 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 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

  • For instances that allow hybrid access to the classic network and VPCs, the classic network endpoint is deleted but the VPC endpoints are retained.

  • If your instances have only classic network endpoints, the system automatically selects or creates VPCs and vSwitches for the instances.

  However, Alibaba Cloud cannot fully guarantee network connectivity after the forced switchover due to the complexity of your network. If you are still using the classic network, network connectivity is affected. We strongly recommend that you switch the network.

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

  1. 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.

  2. In the Basic Information section, check whether 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

1. Switch the network type of Tair (Redis OSS-compatible) instances from classic network to VPC. For more information, see Switch the network type from classic network to VPC.

   When you switch the network type, you can specify whether to retain the classic network endpoint of the instance.

   • No: The VPC endpoint of the instance remains the same as the original classic network endpoint. You do not need to modify the connection string on the client. However, the client can connect to the instance only over a VPC.

     Important

     After you change the network type, a transient connection that lasts for a few seconds may occur. We recommend that you perform this operation during off-peak hours and make sure that your application can automatically reconnect to the instance.

   • Yes: The instance has classic network and VPC endpoints. The classic network endpoint remains unchanged, which places the instance in hybrid access mode. In hybrid access mode, you can manually modify the connection string on the client to smoothly transition your business to a VPC.

2. If you want to retain the classic network endpoint, release the classic network endpoint after you change the network type. For more information, see Release a classic network endpoint.

   If you do not release the classic network endpoint, you cannot perform operations such as renewal, configuration change, and billing method change on the instance.

FAQ

• Why am I unable to renew an instance after I change the network type of the instance to VPC?

  When you change the network type of an instance to VPC, the presence of the classic network endpoint may still impose certain restrictions on the instance. Release the classic network endpoint and try again.

• Is the public endpoint of an instance affected if I release the classic network endpoint of the instance?

  If you release the classic network endpoint of an instance, the public endpoint of the instance is not affected.

• 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.