Simplest approach will be : 1. Create an RDS Snapshot: Take a snapshot of your current RDS instance in the public subnet. 2. Create a New DB Instance in Private Subnet: Launch a new RDS instance from the snapshot you just created, but select a private subnet during configuration. 3. Update Applications: Modify your applications to point to the endpoint of the newly created RDS instance in the private subnet. 4. Terminate Old Instance (Optional): Once you've verified the new instance functions correctly, you can terminate the original instance in the public subnet. But in this process there will be additional cost involved, as creating new instance. Also there there will be some downtime involved while applications switch to the new endpoint. Second approach will be : 1. Create new VPC 2. Create new subnet group with private subnet only 3. Modify existing database and update subnet group with new subnet group that you have created in step 2. Another approach will be kind of workaround : repost.aws/knowledge-center/rds-move-to-private-subnet
The tutorial is concise and straightforward. Thank you.
Thanks for the feedback.
Excelent!
Thanks for the feedback.
good topic thank you
Thanks for the feedback.
First view stamp 🔥
How to move aws rds public vpc to private vpc
So what i understood from your question : you want to move your aws rds from public subnet to private subnet within the same VPC. Is it correct?
@@kodedge yes
@@kodedge I need to connect local db ssms with aws rds.(windows EC2 instance)
Simplest approach will be :
1. Create an RDS Snapshot: Take a snapshot of your current RDS instance in the public subnet.
2. Create a New DB Instance in Private Subnet: Launch a new RDS instance from the snapshot you just created, but select a private subnet during configuration.
3. Update Applications: Modify your applications to point to the endpoint of the newly created RDS instance in the private subnet.
4. Terminate Old Instance (Optional): Once you've verified the new instance functions correctly, you can terminate the original instance in the public subnet.
But in this process there will be additional cost involved, as creating new instance. Also there there will be some downtime involved while applications switch to the new endpoint.
Second approach will be :
1. Create new VPC
2. Create new subnet group with private subnet only
3. Modify existing database and update subnet group with new subnet group that you have created in step 2.
Another approach will be kind of workaround :
repost.aws/knowledge-center/rds-move-to-private-subnet
@@kodedge Thank you