All Products
Search
Document Center

ApsaraDB RDS:Change the vSwitch for an RDS for PostgreSQL instance

Last Updated:Jun 20, 2026

To change the vSwitch of an ApsaraDB RDS for PostgreSQL instance, you can use the console or call an API.

Prerequisites

The ApsaraDB RDS for PostgreSQL instance must use cloud disks.

Limitations

Impacts

  • The switchover causes a transient connection interruption of about 30 seconds. Ensure that your application has an automatic reconnection mechanism.

  • Because switching the vSwitch changes the virtual IP (VIP) address, use an endpoint instead of an IP address in your application to connect to the instance.

  • The VIP address change temporarily affects the use of Data Management (DMS) and Data Transmission Service (DTS). All services automatically resume after the switchover is complete.

  • The DNS cache on the client may prevent write operations, allowing only read operations. You must clear the cache as soon as possible.

Procedure

  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 Connectivity and Security.

  3. Click Switch to another vSwitch.

  4. Select a vSwitch and click OK.

    If no vSwitch is available in the current zone, go to the VPC console to create a vSwitch.

  5. In the dialog box, review the risks and click OK.

FAQ

Q: How do I change the VPC of an instance?

A: You cannot change the VPC of an ApsaraDB RDS for PostgreSQL instance.

Related operations

To switch an instance to a vSwitch in another availability zone, see Change the zone of an instance.

Related API

API

Description

SwitchDBInstanceVpc

Switches the vSwitch of an ApsaraDB RDS for PostgreSQL instance.

Important

The VpcId parameter must be set to the ID of the instance's current VPC because VPC changes are not supported.