ApsaraDB RDS supports two network types: virtual private cloud (VPC) and classic network. This page answers common questions about choosing and changing network types.
What network types does ApsaraDB RDS support?
ApsaraDB RDS supports two network types:
VPC: Each VPC is an isolated virtual network. Inside a VPC, you can define CIDR blocks, configure route tables, and set up gateways. To connect your on-premises data center to Alibaba Cloud, use a leased line or VPN. All ApsaraDB RDS instances support VPC.
Classic network: Classic network instances share the underlying network infrastructure and cannot be isolated at the network level. Access control relies entirely on IP address whitelists and security groups. Only ApsaraDB RDS instances that use local disks support the classic network.
Use VPC for all new instances. VPC provides stronger isolation and more networking options than the classic network.
What are the differences between VPC and classic network?
| Feature | VPC | Classic network |
|---|---|---|
| Layer 2 logical isolation | Supported | Not supported |
| Custom private CIDR block | Supported | Not supported |
| Private IP address planning | Unique within a VPC; can overlap across VPCs | Must be unique across the entire classic network |
| Instance communication | Instances in the same VPC can communicate; instances in different VPCs are isolated | Instances in the same region and account can communicate |
| Tunneling | Supported | Not supported |
| Custom router | Supported | Not supported |
| Route table | Supported | Not supported |
| vSwitch | Supported | Not supported |
| Software-Defined Networking (SDN) | Supported | Not supported |
| Self-managed NAT gateway | Supported | Not supported |
| Self-managed VPN | Supported | Not supported |
Can I change the network type of an ApsaraDB RDS instance?
You can switch from classic network to VPC. Switching from VPC to classic network is not supported.
For the step-by-step procedure and the impact of switching, see Change the network type.
How do I move an ApsaraDB RDS instance to a different VPC?
The approach depends on whether your instance supports direct VPC and vSwitch changes.
If your instance supports direct VPC and vSwitch changes, update the VPC configuration directly. Refer to the guide for your database engine:
MySQL: Change the VPC and vSwitch for an ApsaraDB RDS for MySQL instance
SQL Server: Switch an ApsaraDB RDS for SQL Server instance to a different vSwitch
PostgreSQL: Switch an ApsaraDB RDS for PostgreSQL instance to a different vSwitch
If your instance does not support direct VPC and vSwitch changes, purchase a new ApsaraDB RDS instance in the target VPC, then migrate your data from the original instance to the new one.
Migration guides by engine: