Alibaba Cloud is retiring the classic network for ApsaraDB RDS. This affects RDS instances that run MySQL, SQL Server, and PostgreSQL. If your instances already use a Virtual Private Cloud (VPC), no action is required. For classic network instances, switch to VPC before the deadline to avoid service interruption.
Timeline
October 30, 2024 (00:00) -- Classic network RDS instances can no longer be renewed, upgraded, downgraded, or cloned. This restriction also applies to instances with hybrid access mode enabled.
February 28, 2025 (00:00) -- Classic network RDS instances are forcefully stopped and all workloads are interrupted. Database proxy endpoints of the classic network type also become invalid on this date.
RDS instances that use VPC are not affected at either milestone.
Affected instances
The following instance types are affected:
RDS instances that use the classic network type
RDS instances with hybrid access mode enabled (both VPC and classic network endpoints are active)
Identify affected instances in the console
Open the Instances page.
In the top navigation bar, select a region.
In the Network Type column, select Classic Network and click OK.
All classic network RDS instances in the selected region are displayed.
Identify affected instances by API
Call the DescribeDBInstances operation with a specified region. Set the InstanceNetworkType parameter to Classic. This returns all classic network RDS instances in that region. For more information, see DescribeDBInstances.
Impact details
On February 28, 2025
| Instance configuration | Impact |
|---|---|
| Classic network only | Instance is forcefully stopped. All workloads are interrupted. |
| Hybrid access mode | The classic network endpoint is released and becomes invalid. Classic network workloads are interrupted. The VPC endpoint is retained and VPC workloads continue normally. |
| VPC only | No impact. |
Database proxy endpoints of the classic network type also become invalid on this date.
Solutions
Switch the network type from classic network to VPC. If a database proxy endpoint of the classic network type exists, also switch it to VPC and release the classic network proxy endpoint.
Switch the network type
Open the Instances page and select the region of your RDS instance.
Click the instance ID to open the instance details page.
In the left-side navigation pane, click Database Connection.
Click Switch to VPC.
Choose one of the following methods:
Direct switch
Change the network type to VPC immediately without retaining the classic network endpoint. For step-by-step instructions, see Change the network type of an ApsaraDB RDS for MySQL instance.
Smooth switch (hybrid access mode)
Temporarily retain the classic network endpoint while a new VPC endpoint is generated. Update application connection strings to use the VPC endpoint, then release the classic network endpoint. For setup instructions, see Configure hybrid access for an ApsaraDB RDS for MySQL instance.
After all applications use the VPC endpoint, delete the classic network endpoint. If the classic network endpoint remains, the instance is still treated as a classic network instance. Renewal and specification changes are blocked.
Migration method comparison
| Affected item | Direct switch | Smooth switch |
|---|---|---|
| Instance connection | Momentarily disconnected during the switch. | No disconnection. |
| Internal endpoint | One internal endpoint. The endpoint address stays the same; only the type changes from classic network to VPC. | Two internal endpoints. The classic network endpoint is retained and a VPC endpoint is generated. |
| Internal network access | After the switch, only VPC-based cloud service instances (such as ECS instances) can access the RDS instance. | Both classic network and VPC cloud service instances can access the RDS instance. Classic network clients use the classic network endpoint. VPC clients use the VPC endpoint. After the classic network endpoint expires, only the VPC endpoint remains available. |
| Public endpoint and internet access | Not affected. Only internal endpoints and internal network access change. | Not affected. Only internal endpoints and internal network access change. |
Special cases
MySQL 5.7 on RDS Basic Edition with cloud disks on the classic network: Hybrid access mode is not supported. Use the direct switch method.
Phased-out instance type: Change the instance type to a currently available type before switching the network. See Instance types for standard primary ApsaraDB RDS for MySQL instances (original x86 architecture) and Change instance specifications.
Switch the database proxy endpoint
If your RDS instance has a database proxy endpoint of the classic network type, switch it to VPC and release the classic network proxy endpoint.
Check the current proxy endpoint type
Open the Instances page and select the region of your RDS instance.
Click the instance ID to open the instance details page.
In the left-side navigation pane, click Database Proxy.
View the database proxy endpoint and its network type.
Switch and release the classic network proxy endpoint
If both VPC and classic network proxy endpoints exist, update all application connection strings to use the VPC proxy endpoint, then release the classic network proxy endpoint.
Before releasing a classic network database proxy endpoint, verify that no applications still use it.
Troubleshooting: still receiving classic network notifications after switching to VPC
If the network type is already VPC but classic network discontinuation notifications persist, the classic network endpoint from hybrid access mode was not released. To resolve this:
Open the Instances page and click the instance ID.
In the left-side navigation pane, click Database Connection.
Release the classic network endpoint or modify its expiration time.
Until the classic network endpoint is released, the instance remains subject to classic network restrictions. Renewal and specification changes are blocked.