Satya walks you through
changing the VPC
for your RDS DB instance

change-vpc-rds-db-instance-satya

I want to move my Amazon Relational Database Service (RDS) DB instance from an existing VPC to a new VPC. 

A virtual private cloud (VPC) is a virtual network dedicated to your account and separated from other networks in the AWS Cloud. Be sure to configure the new VPC before you move the RDS DB instance to the new network, including security group inbound rules, subnet group, route tables, etc.

Before you begin, note these two restrictions when changing the VPC for your DB instance:

  • If your DB instance is in multiple Availability Zones, you cannot change the VPC. First convert to a single zone, and then you can convert back to a Multi-AZ DB instance after moving to the new VPC. For more information about converting your instance, see High Availability (Multi-AZ).
  • You cannot change the VPC for Read Replicas or a DB instance with a Read Replica. First remove the Read Replicas, and then add them again after moving to the new VPC.

Note: When you change the VPC for a DB instance, the instance reboots as it moves from one network to another. Because the DB instance is not accessible when this happens, make this change during a scheduled maintenance window.

  1. Open the Amazon RDS console and choose Subnet Groups from the left navigation pane.
  2. Choose Create DB Subnet Group.
  3. Enter the subnet name, description, and VPC ID, and choose the subnets needed for the DB instance.
  4. Choose Create.
  5. Choose Instances from the left navigation pane.
  6. Select the DB instance, choose Instance Actions, and then choose Modify.
  7. Under Network & Security, select the Subnet Group associated with the new VPC and choose the appropriate Security Group for that VPC.
  8. Choose Apply Immediately and Continue.
    Note: If Apply Immediately is not selected, the VPC is modified during the next maintenance window.
  9. Review the details on the Modify DB Instance page, and choose Modify DB Instance.

This can take several minutes to complete. You can confirm that the subnet has been changed by selecting the instance and navigating to the configuration details page, which should show that the subnet group has been updated and the status is Complete. You can also open the RDS console and choose Events in the left navigation pane to confirm that the process has finished moving the DB instance to the target VPC.


Did this page help you? Yes | No

Back to the AWS Support Knowledge Center

Need help? Visit the AWS Support Center

Published: 2016-05-26