This topic describes how to change the network type of an ApsaraDB RDS instance from classic network to Virtual Private Cloud (VPC) by using the ApsaraDB RDS console or by calling the relevant API operation. You can choose to retain the classic network endpoint when you change the network type.

Prerequisites

Before you change the network type, make sure that the following conditions are met:
  • The ApsaraDB RDS instance is deployed in a classic network.
  • VPCs and vSwitches are available in the zone to which the ApsaraDB RDS instance belongs. For more information, see Create an IPv4 VPC.

Background information

For more information about how the system seamlessly migrates an ApsaraDB RDS instance from a classic network to a VPC, see Hybrid access solution for smooth migration from classic networks to VPCs.
Note
  • When you change the network type, you can specify an expiration date for the classic network endpoint. After the expiration date is reached, the classic network endpoint is automatically deleted. Before the classic network endpoint is deleted, you will receive text messages.

  • If the ApsaraDB RDS instance is a shard of a DRDS instance, the DRDS instance will be disconnected from the ApsaraDB RDS instance after the network type is changed. You must manually reconnect both instances.

Change the network type by using the ApsaraDB RDS console

  1. Log on to the ApsaraDB RDS console.
  2. In the left-side navigation pane, click Instances.
  3. Select the region where the ApsaraDB RDS instance is deployed.
  4. Click the ID of the ApsaraDB RDS instance.
  5. In the left-side navigation pane, click Database Connection.
  6. On the Database Connection page, click Switch to VPC.
  7. In the Switch to VPC dialog box, select the VPC and vSwitch that you want to use.
  8. Select Reserve Original Classic Network Endpoint and set Expiration Time for the classic network endpoint.
    • Seven days before the classic network endpoint expires, the system will send a text message to the mobile number associated with your Alibaba Cloud account each day.
    • After the expiration date of the classic network endpoint is reached, the classic network endpoint is automatically deleted. Then, you can no longer access the ApsaraDB RDS instance through the classic network endpoint. To ensure that your services are not interrupted, set a proper expiration date. After you configure the hybrid access mode, you can change the expiration date.
  9. Click OK.
    The Database Connection page displays Reserve Original Classic Network Endpoint. Classic network

Change the expiration date of the classic network endpoint by using the console

You can extend the expiration date of the classic network endpoint in the console before the classic network endpoint expires.

During the period in which your instance can be connected over a classic network or VPC, you can modify the expiration date of the classic network endpoint as needed. The change immediately takes effect. For example, if the classic network endpoint is set to expire on August 18, 2017 and you extend the expiration date by 14 days on August 15, 2017, the endpoint will be deleted on August 29, 2017.

  1. Log on to the ApsaraDB RDS console.
  2. In the left-side navigation pane, click Instances.
  3. Select the region where the ApsaraDB RDS instance is deployed.
  4. Click the ID of the ApsaraDB RDS instance.
  5. In the left-side navigation pane, click Database Connection.
  6. On the Database Connection page, click Change Expiration Time.
  7. Set the expiration time and click OK.

Change the network type by calling the relevant API operation

For more information, see Change the network type of an ApsaraDB for RDS instance.

Change the expiration date of the classic network endpoint by calling the relevant API operation

For more information, see Change the expiration time of a classic network endpoint.