Updating the VPC for a DB instance - Amazon Relational Database Service
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Updating the VPC for a DB instance

You can use the Amazon Web Services Management Console to move your DB instance to a different VPC.

For information about modifying a DB instance, see Modifying an Amazon RDS DB instance. In the Connectivity section of the modify page, shown following, enter the new DB subnet group for DB subnet group. The new subnet group must be a subnet group in a new VPC.


				Modify DB Instance panel Subnet group section

You can't change the VPC for a DB instance if the following conditions apply:

  • The DB instance is in multiple Availability Zones. You can convert the DB instance to a single Availability Zone, move it to a new VPC, and then convert it back to a Multi-AZ DB instance. For more information, see Configuring and managing a Multi-AZ deployment.

  • The DB instance has one or more read replicas. You can remove the read replicas, move the DB instance to a new VPC, and then add the read replicas again. For more information, see Working with DB instance read replicas.

  • The DB instance is a read replica. You can promote the read replica, and then move the standalone DB instance to a new VPC. For more information, see Promoting a read replica to be a standalone DB instance.

  • The subnet group in the target VPC doesn't have subnets in the DB instance's the Availability Zone. You can add subnets in the DB instance's Availability Zone to the DB subnet group, and then move the DB instance to the new VPC. For more information, see Working with DB subnet groups.