Alibaba Cloud will retire ApsaraDB RDS instances in the classic network. This change affects ApsaraDB RDS for MySQL, ApsaraDB RDS for PostgreSQL, and ApsaraDB RDS for SQL Server. This document describes the retirement plan, the affected instances, and the required migration solutions.
Affected instances
All ApsaraDB RDS instances in the classic network and instances with hybrid access mode enabled (which retain both classic network and VPC endpoints) across all regions are affected by this retirement. You can use the following methods to identify affected instances:
Query by console
Go to the RDS Instances page. Select a region, click Network Type in the list header, and select Classic Network. The console then lists all ApsaraDB RDS instances in the classic network for the selected region.
Query by API
Call the DescribeInstances operation. Select a region and set the InstanceNetworkType parameter to Classic. The API returns all ApsaraDB RDS instances in the classic network for the specified region. For more information, see Query an instance list.
If you have already switched your network type but still receive retirement notifications from Alibaba Cloud, it means you have not deleted the classic network endpoint. The instance is still affected by the retirement, and you cannot renew the instance or change its specifications. You must go to the RDS Instances page, navigate to the Database Connection page for your instance, and manually delete the classic network endpoint or modify its expiration date to avoid service disruption.
Retirement plan
Effective 00:00, October 30, 2024: Renewal, spec changes, and cloning disabled
-
For instances in the classic network or with hybrid access mode enabled: You can no longer renew, change specifications for, or clone these instances. Existing subscription ApsaraDB RDS instances in the classic network cannot be renewed.
-
For instances that use only a VPC: No impact.
If you have switched to a VPC but still cannot renew your instance or change its specifications, it means that you have not deleted the classic network endpoint. You must go to the RDS Instances page, navigate to the Database Connection page for your instance, and manually delete the classic network endpoint or modify its expiration date to avoid service disruption.
Effective 00:00, February 28, 2025: Service termination
-
For instances in the classic network: These instances will be shut down, which will interrupt your business.
-
For instances with hybrid access mode enabled:
-
The classic network endpoint will be deleted and will stop working, interrupting any business that relies on it.
-
The VPC endpoint will be retained. Business traffic through the VPC will not be affected.
-
-
For instances that use only a VPC: No impact.
The classic network endpoint for the database proxy will also stop working at 00:00 on February 28, 2025.
Solutions
To prevent service interruptions, switch the network type of your instance from classic network to VPC. If your database proxy uses a classic network endpoint, you must also switch it to a VPC endpoint and then release the classic network endpoint.
Switch instance network type
Go to the RDS Instances page, click an instance ID to go to its details page, select the Database Connection tab, and click Switch to VPC. ApsaraDB RDS provides two methods to switch the network type:
-
Direct change: Does not retain the classic network endpoint and switches the network type directly to VPC.
-
Enable hybrid access mode for a smooth change: Temporarily retains the classic network endpoint while adding a new VPC endpoint. You must reconfigure your applications to use the new VPC endpoint. During the migration, you can access the instance through either the classic network or the VPC. After the migration is complete, you must delete the classic network endpoint.
|
Aspect |
Direct change |
Smooth change (hybrid access) |
|
Momentary disconnection |
Yes |
No |
|
Internal endpoint |
Only one internal endpoint: The endpoint string does not change. The endpoint type changes from classic network to VPC. |
Two different internal endpoints: The classic network internal endpoint is retained, and a new VPC internal endpoint is automatically created. |
|
Internal access |
After you switch the instance to a VPC, any cloud services (such as ECS) that access it must also be in the same VPC. |
After hybrid access is enabled for the ApsaraDB RDS instance, other cloud services (such as ECS) can access it over the following network types:
After the classic network endpoint expires, you can only access the instance through the VPC. |
|
Public endpoint |
Neither network switch method affects the public endpoint or public access. They affect only the instance's internal endpoint and internal access. |
|
|
Public access |
||
-
For ApsaraDB RDS for MySQL 5.7 Basic Edition instances with cloud disks in the classic network, only the direct change method is supported. The hybrid access mode is not available.
-
If your instance is a legacy instance type, you must change its specifications to a current instance type before switching its network type.
Switch database proxy endpoint
View database proxy endpoints
Go to the RDS Instances page, select a region, click an instance ID, and then click Database Proxy in the left-side navigation pane to view the current proxy connection information.
Switch to VPC endpoints
If your proxy has both VPC and classic network endpoints, migrate any applications that use the classic network endpoint to the VPC endpoint. After all applications are migrated, release the classic network endpoint.
Before you release the classic network proxy endpoint, ensure that no applications are using it.
Related content
ECS classic network instance retirement and network type changes: