Alibaba Cloud plans to phase out ApsaraDB RDS instances of the classic network type. This applies to RDS instances that run MySQL, SQL Server, and PostgreSQL. This topic describes the end-of-sale plan for RDS instances that use the classic network type. This topic also describes how to query RDS instances that are affected by the end-of-sale plan and how to handle the affected RDS instances.
End-of-sale plan
RDS instances of the classic network type can no loner be renewed, upgraded or downgraded, and cloned from 00: 00 (UTC+8) on October 30, 2024
You can no longer renew, upgrade or downgrade, and clone RDS instances of the classic network type and RDS instances that allow hybrid access to the classic network and VPCs. You also cannot renew the existing subscription RDS instances of the classic network type.
If you only delete the classic network endpoint of an RDS instance that allows hybrid access to the classic network and VPCs but not change the instance network type from the classic network to VPC, the instance cannot be renewed, upgraded, downgraded, or cloned from 00: 00 (UTC+8) on October 30, 2024.
If the network type of an RDS instance that allows hybrid access to the classic network and VPCs is changed to VPC, and the classic network endpoing of the instance is deleted, the instance can still be renewed, upgraded, downgraded, or cloned from 00: 00 (UTC+8) on October 30, 2024.
Discontinuation of RDS instances of the classic network type from 00:00 (UTC+8) on February 28, 2025
All RDS instances of the classic network type will be shut down, and involved services will be affected after the RDS instances are shut down.
For an RDS instance that allows hybrid access to the classic network and VPCs, if the network type of the instance is not changed to VPC, the instance can still be accessed through the classic network but will be shut down at 00:00 (UTC+8) on February 28, 2025.
The database proxy endpoints of the classic network type also become inaccessible from 00:00 (UTC+8) on February 28, 2025.
You can view the connection information about the database proxy of your instance by performing the following steps: 1. Log on to the ApsaraDB RDS console, and then click Instances in the left-side navigation pane. 2. On the top navigation bar of the Instances page, choose the region in which your RDS instance is located and then click the ID of your instance. 3. In the left-side navigation pane, click Database Proxy. 4. View the database proxy connection information on the page that appears.
Usage notes
The preceding end-of-sale plan applies to RDS instances of the classic network types in all regions.
RDS instances of the VPC network type are not affected.
RDS instances that allow hybrid access to the classic network and VPCs are affected unless otherwise specified.
We recommend that you change the network type of your RDS instances from classic network to VPC before the preceding points in time to prevent the RDS instances from being affected.
Query affected RDS instances
Method 1: Query affected RDS instances in the ApsaraDB RDS console
Log on to the ApsaraDB RDS console and go to the Instances page. In the top navigation bar, select the region in which your RDS instance resides.
Select Classic Network from the Network Type column and click OK to view all RDS instances of the classic network type in the current region.
Method 2: Call an API operation to query affected RDS instances
Call the DescribeInstances operation and make sure that a region is specified and the InstanceNetworkType parameter is set to Classic in the call. This way, you can query all RDS instances of the classic network in the specified region. For more information, see DescribeDBInstances.
Solution
RDS instances of the classic network type
Migrate your RDS instance of the classic network type to a VPC before the end-of-sale date. You can also use the hybrid access feature to smoothly migrate your RDS instance of the classic network type to a VPC without interruptions. For more information about detailed operations and migration principles, see the following documentation:
ApsaraDB RDS for MySQL: Change the network type and Configure the hybrid access solution.
ApsaraDB RDS for PostgreSQL: Change the network type of an ApsaraDB RDS for PostgreSQL instance and Configure the hybrid access solution for an ApsaraDB RDS for PostgreSQL instance.
ApsaraDB RDS for SQL Server: Change the network type and Configure the hybrid access solution.
ECS instances on which RDS instances of the classic network type are deployed
Migrate the RDS instances of the classic network type to a VPC before the end-of-sale date. The hybrid access feature cannot be used to migrate the instances. For more information, see the following documentation:
ImportantIf you migrate an RDS instance of the classic network type to a VPC, a switchover is triggered for the instance. For more information, see Impacts of an instance switchover.
ApsaraDB RDS for MySQL: Change the network type.
ApsaraDB RDS for PostgreSQL: Change the network type of an ApsaraDB RDS for PostgreSQL instance.
ApsaraDB RDS for SQL Server: Change the network type.
RDS instances for which database proxies are enabled and a database proxy endpoint of the classic network type is created
If a database proxy endpoint of the classic network type and a database proxy endpoint of the VPC type are both created for your RDS instance, and your application uses the proxy endpoint of the classic network type to connect to the RDS instance, we recommend that you change the current proxy endpoint to the proxy endpoint of the VPC type in the connection settings of your application. After you change the connection settings of your application, you can release the proxy endpoint of the classic network type.
ImportantBefore you release a database proxy endpoint of the classic network type, make sure that this endpoint is not used by your application to connect to the RDS instance.