RDS migration from one vpc to another

Question

We are currently using an AWS RDS PostgreSQL instance running version 14.2. The instance is public and has a fixed master password. I want to migrate the data to a new VPC with the latest version of PostgreSQL, ensure there are no public connections by making use of isolated subnets, and manage the master password via AWS Secrets Manager. What is the best way to achieve this and transfer the data with minimal or no downtime?

Subhash Raut · Answer

by just modifying the DB subnet group it wont trigger to change to new VPC it only guides which subnets to use when setting up new instance or if there change in underlying host due to various manual methods

Rather i would suggest using a read replica path with preconfigured dbsubnet group/sg's/parametergroup (new version)/secret manager.
let me know if any questions

Gary Mclean · Answer

1. Create a new DB Subnet group in the New VPC
2. Modify the RDS Instance and select the new Subnet Group
3. RDS will migrate the RDS Instance to the New VPC
4. Modify the RDS Instance and disable public Access
5. Modify the RDS and under Credential Management, update to be managed by Secrets Manager
6. Update any application connection strings to the NEW endpoint name

The migration will cause minimal downtime while the RDS instance moves subnets.

**NOTE the endpoint name WILL change because of the VPC Move!**

Allan Wilson · Answer

Actually I just did a RDS PostgreSQL migration to another VPC.
It was a dev instance so downtime wasn't an issue.

High level
- create new db subnet group for the private subnets in the new VPC
- create new security groups for the new VPC
- update db subnet group for the RDS instance
- it migrated to the new VPC (via the new db subnet group) and applied my new security groups
- endpoint name Stays the Same (this was a requirement)

RDS migration from one vpc to another

Add your answer

Relevant content