How can I move an Amazon RDS DB instance from a public subnet to private subnet within the same VPC?
I have an Amazon Relational Database Service (Amazon RDS) DB instance that is in a public subnet. I want to move my DB instance from a public to a private subnet within the same VPC, and make my DB instance completely private. How can I do this?
Amazon RDS doesn't provide an option to change the subnet group of your DB instance, within the same VPC. However, you can use the workaround method in this article to move your DB instance from a public subnet to a private subnet. Performing this action makes your DB instance private.
This method has a number of advantages, including:
- You don't need to create a new DB instance
- You don't need to use the snapshot-restore process
- It minimizes the downtime involved in creating a new instance and diverting traffic. The only downtime that you see is the failover time.
Turn off Multi-AZ deployments and public accessibility on your DB instance
If your DB instance is already set to Single-AZ with the Public accessibility parameter set to No, then skip this step.
To modify your DB instance to turn off Multi-AZ deployments, follow these steps:
- Sign in to the Amazon RDS console.
- From the navigation pane, choose Databases, and then choose the DB instance that you want to modify.
- Choose Modify.
- From the Modify DB Instance page, for Multi-AZ deployment and Public accessibility, choose No.
- Choose Continue, and then review the summary of modifications.
- Choose Apply immediately to apply your changes.
- Review your changes, and if correct, choose Modify DB Instance to save.
Discover the IP address of your DB instance
After your DB instance returns to the Available state, run dig on the DB instance's endpoint to find its underlying IP address:
db-RDS-instance.xxxxxxxx.us-east-1.rds.amazonaws.com. 5 IN A 18.104.22.168
From the private IP, you can find which subnet your primary instance is using.
In this example, the list of subnet CIDR is as follows:
- subnet1 -> 22.214.171.124/24
- subnet2 -> 126.96.36.199/24
Because the IP is falling under 188.8.131.52/24, you can conclude that the instance is placed in subnet1.
Remove the public subnets and add private subnets on your DB instance
Add all the required private subnets in the subnet group. Also, delete all public subnets from the subnet group except for the one that is used by your primary. In the previous example, you delete everything except subnet1 because it is used by your DB instance.
Note: A private subnet is a subnet that is associated with a route table that has no route for an internet gateway.
- Sign in to the Amazon RDS console.
- From the navigation pane, choose Subnet groups, and then choose the subnet group that is associated with your DB instance.
- Choose Edit.
- From the Add subnets section, choose the Availability Zone and private subnets that you want to add.
- Select the public subnets that you want to delete, and then choose Remove.
- Choose Save.
Turn on Multi-AZ on your DB instance
Modify the DB instance to turn on the Multi-AZ deployment. The new secondary launches in one of the remaining private subnets.
Reboot your DB instance with failover and turn off Multi-AZ deployment
When your DB instance fails over, the secondary, which is using the private IP, becomes the primary and the public subnet becomes the secondary.
After you reboot your DB instance with failover, remove the secondary, which is now in the public subnet. To do this, modify the DB instance to turn off Multi-AZ, again. You can do this by setting Multi-AZ deployment to No.
Remove the public subnet
- Remove the remaining public subnet from the subnet group.
Note: Removing subnets from the subnet group is a configuration from the RDS side. It doesn't involve deleting any subnets from the VPC.
- Check that there are only private subnets in the subnet group.
- If your DB instance was previously in Multi-AZ deployment, then turn Multi-AZ deployment on again.
This solution involves failover and turning on/turning off Multi-AZ so there are few things to consider. For more information, see Multi-AZ DB instance deployments.
Note: This method is specific for RDS DB instances. If your DB instance is part of Aurora cluster, then you can use the clone option. Or you can follow the steps in this article, but instead of turning off Multi-AZ, you should delete and recreate the readers.
- ¿Por qué aparece un error de acceso denegado cuando intento conectarme a mi clúster de base de datos de Amazon Aurora?OFICIAL DE AWSActualizada hace 5 meses
- OFICIAL DE AWSActualizada hace un año
- OFICIAL DE AWSActualizada hace 4 meses
- ¿Cómo soluciono los problemas de conectividad de red de mi instancia de cuaderno de Amazon SageMaker que tiene desactivado el acceso directo a Internet?OFICIAL DE AWSActualizada hace 6 meses