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.
Affected RDS instances
RDS instances that use the classic network type and RDS instances for which the hybrid access mode is enabled. In hybrid access mode, the endpoints of the Virtual Private Cloud (VPC) and classic network types are retained. You can use one of the following methods to query the affected RDS instances:
Go to the Instances page. In the top navigation bar, select a region. Then, select Classic Network from the Network Type column and click OK to view all RDS instances of the classic network type in the selected region.
Call the DescribeInstances operation and make sure that a region is specified and the InstanceNetworkType parameter is set to Classic in the request. This way, you can query all RDS instances of the classic network in the specified region. For more information, see DescribeDBInstances.
If the network type of your RDS instance is changed but you still receive a notification of the classic network discontinuation, this indicates that you do not release the classic network endpoint in hybrid access mode. As a result, the RDS instance is still affected by the classic network discontinuation. For example, you may fail to renew the subscription or change specifications. To prevent your business from being interrupted because of the classic network discontinuation, you must go to the details page of the instance from the Instances page, and then manually release the classic network endpoint of the instance or modify the expiration time of the endpoint on the Database Connection page.
End-of-sale plan
RDS instances of the classic network type can no longer be renewed, upgraded, downgraded, or cloned from 00: 00 on October 30, 2024
RDS instances that use the classic network type and RDS instances for which the hybrid access mode is enabled: You can no longer renew, upgrade, downgrade, or clone the RDS instances. In addition, you cannot renew the existing subscription RDS instances of the classic network type.
RDS instances that use the VPC type: The RDS instances are not affected.
If the network type of your RDS instance is changed to VPC but you still fail to renew the subscription or change specifications, this indicates that you do not release the classic network endpoint in hybrid access mode. To prevent your business from being interrupted because of the classic network discontinuation, you must go to the details page of the instance from the Instances page, and then manually release the classic network endpoint of the instance or modify the expiration time of the endpoint on the Database Connection page.
RDS instances of the classic network type stop providing services from 00:00 on February 28, 2025
RDS instances of the classic network type:: The RDS instances are forcefully stopped, and your workloads are interrupted.
RDS instances for which the hybrid access mode is enabled:
The classic network endpoint is released and automatically becomes invalid. As a result, your workloads on the classic network are interrupted.
The VPC endpoint is retained, and your workloads in the VPC are not affected.
RDS instances that use the VPC type: The RDS instances are not affected.
Solutions
To prevent the impacts on your workloads, you must change the network type of your RDS instance from classic network to VPC.
Go to the Instances page. In the top navigation bar, select the region in which your RDS instance resides. Click the ID of your RDS instance to go to the instance details page. In the left-side navigation pane, click Database Connection. On the page that appears, click Switch to VPC. You can use one of the following methods to change the network type:
Direct change: You can directly change the network type to VPC without the need to retain the classic network endpoint.
Enable the hybrid access mode to implement smooth change: The classic network endpoint is temporarily retained and a VPC endpoint is generated. You must gradually modify the application configurations to change the endpoint to the new VPC endpoint. During the change, you can use both the classic network endpoint and the VPC endpoint to connect to the RDS instance. After the network type is changed, you must delete the classic network endpoint.
The following table describes the impacts of the change methods.
Affected item | Direct change | Smooth change |
Instance connection | The connection to the instance is momentarily disconnected. | The connection to the instance is not disconnected. |
Internal endpoint | Only one internal endpoint: After the change, the internal endpoint remains unchanged but the type of the internal endpoint is changed from classic network to VPC. | Two internal endpoints: The internal endpoint of the classic network type is retained and an internal endpoint of the VPC type is generated. |
Internal network access | After the network type of an RDS instance is changed to VPC, other cloud service instances (such as ECS instances) can access the RDS instance only if the network type of the instances is VPC. | If a different cloud service instance, such as ECS instance, wants to access an RDS instance, the network type of the cloud service instance can be classic network or VPC.
After the classic network endpoint expires, you can use only the VPC endpoint to connect to the RDS instance. |
Public endpoint | The network change does not affect the public endpoint and Internet access of the instance. Only the internal endpoint and internal network access are affected. | |
Internet access | ||
