ApsaraDB RDS:Change the network type

For more information about how to change the network type of an RDS instance that runs a different database engine, see the following topics:

• Change the network type of an ApsaraDB RDS for SQL Server instance

• Change the network type of an ApsaraDB RDS for PostgreSQL instance

Impacts

The following table describes the impacts that a change in the network type may bring if the database proxy feature is enabled for your RDS instance. For more information, see Introduction to database proxies.

Network types

• Classic network: RDS instances in the classic network are not isolated. To block unauthorized access to these instances, you must configure IP address whitelists or security groups.

• Virtual private cloud (VPC): Each VPC is an isolated virtual network. VPCs are more secure than the classic network. We recommend that you select the VPC network type.

  You can customize route tables, CIDR blocks, and gateways for a VPC. In addition, you can connect your data center to a VPC by using Express Connect circuits or VPNs. The data center and the VPC comprise a virtual data center. You can use the virtual data center to migrate your workloads to the cloud with no downtime.

View the network type

1. Go to the Instances page. In the top navigation bar, select the region in which the RDS instance resides. Then, find the RDS instance and click the ID of the instance.

2. In the left-side navigation pane, click Database Connection.

Change the network type from classic network to VPC

1. Go to the Instances page. In the top navigation bar, select the region in which the RDS instance resides. Then, find the RDS instance and click the ID of the instance.

2. In the left-side navigation pane of the page that appears, click Database Connection.

3. Click Switch to VPC.

   Note

   If the preceding button cannot be found, check whether your RDS instance resides in the classic network.

4. In the dialog box that appears, select a VPC and a vSwitch and specify whether to retain the classic network endpoint.

   • Select a VPC. We recommend that you select the VPC in which the required ECS instance resides. If the ECS instance and the RDS instance reside in different VPCs, these instances can communicate over an internal network only if you use Cloud Enterprise Network (CEN) or VPN Gateway to enable network communication between the VPCs of these instances. For more information, see Overview of CEN or Establish IPsec-VPN connections between two VPCs.

   • Select a vSwitch. If no vSwitches are available in the selected VPC, create a vSwitch in the zone where the RDS instance resides. For more information, see Create and manage a vSwitch.

   • Clear or select Reserve original classic endpoint.

     Scaling policy	Description
     Clear Reserve original classic endpoint	The classic network endpoint is not retained and changes to a VPC endpoint. When you change the network type from the classic network to a VPC, an instance switchover occurs and ECS instances that reside in the classic network are immediately disconnected from the RDS instance. For more information about the impacts of an instance switchover, see Impacts of an instance switchover.
     Select Reserve original classic endpoint	The classic network endpoint is retained, and a new VPC endpoint is generated. In this case, the RDS instance runs in hybrid access mode. ECS instances in the classic network and ECS instances in VPCs can connect to the RDS instance over an internal network. For more information, see Configure the hybrid access solution for an ApsaraDB RDS for MySQL instance. When you change the network type from classic network to VPC, no instance switchovers occur. The connection between each ECS instance of the classic network type and the RDS instance remains available until the classic network endpoint expires. Before the classic network endpoint expires, add the VPC endpoint to your application that runs on an ECS instance. This allows ApsaraDB RDS to migrate your workloads to the selected VPC with no downtime. For more information, see Configure the hybrid access solution.

5. Add the private IP address of the required ECS instance of the VPC network type to an IP address whitelist of the VPC network type on the RDS instance. This way, the ECS instance can access the RDS instance over an internal network. For more information about how to add the private IP address to an IP address whitelist, see Configure an IP address whitelist. If no IP address whitelists of the VPC network type are available, create one.

   Note

   You can go to the Instance Details tab of an ECS instance in the ECS console to view the private IP address of the ECS instance.

6. Add the VPC endpoint of your RDS instance to the connection settings of your application. This way, your application can connect to the RDS instance through the VPC endpoint. For more information about how to obtain the VPC endpoint, see View and manage instance endpoints and ports.

   • If you selected Reserve original classic endpoint, you must add the VPC endpoint to your application that runs on an ECS instance before the classic network endpoint expires.

   • If you cleared Reserve original classic endpoint, the connection between each ECS instance of the classic network type and the RDS instance over an internal network is immediately closed after the network type is changed. You must add the VPC endpoint of the RDS instance to your application that runs on the ECS instance.

   Note

   If the RDS instance resides in a VPC and you want to connect a classic network-hosted ECS instance to the RDS instance over an internal network, you can use ClassicLink to establish a connection. Alternatively, you can migrate the ECS instance to the same VPC as the RDS instance. For more information, see Overview of ClassicLink.

Related operations