This topic describes how to switch an ApsaraDB RDS for PostgreSQL instance that uses standard or enhanced SSDs to a different vSwitch.
- During the change process, your RDS instance encounters a transient connection of about 30 seconds. Make sure that your application is configured to automatically reconnect to your RDS instance.
- After the vSwitch of your RDS instance is changed, the virtual IP addresses (VIPs) of your RDS instance change. We recommend that you connect your application to your RDS instance by using an endpoint. For more information, see Configure endpoints for an ApsaraDB RDS for PostgreSQL instance.
- The VIP changes temporarily interrupt the connections to DMS and Data Transmission Service (DTS). After the change process is finished, these connections are automatically restored to normal.
- If data is cached on the database client, you can read data but cannot write data. After the change process is finished, we recommend that you immediately clear the cache on the database client.
- Access RDS Instances, select a region at the top, and then click the ID of the target RDS instance.
- In the left-side navigation pane, click Database Connection.
- Click Switch vSwitch.
- Select a VPC and a vSwitch. Then, click OK. Note If you want to create a VPC or a vSwitch, click go to the VPC console.
- In the message that appears, click Switch.
How do I change the VPC of an RDS instance if the instance does not allow me to switch to a different VPC and vSwitch?
Purchase a new RDS instance with the required VPC selected. Then, migrate the data of the original RDS instance to the new RDS instance. For more information, see Migrate data between ApsaraDB RDS for PostgreSQL instances.