Level 61
Under Multi-AZ deployment and Public accessibility on Modify DB Instance page select No and save the change.
1 like
Oct 20, 2021
9
Level 1
How to make an already in-production database private?
I have previously created a public database with not NAT nor Jumpbox. Now I'm planning in securing this database by making it private and using a jumpbox. I've already added a NAT gateway to the network in use and created a Jumpbox. But I was wondering if there is a way in making the database private and keep using it in my applications without ruining my already deployed applications' connection to it?
Any help would be much appreciated!
Level 1
Hi, thanks for the reply.
Wouldn't this break the connection from the deployed projects? I mean aren't there any extra steps that should be made?
Level 61
@hmawla there is no way around it. You would have to change the IP address.
Level 61
Level 1
Thanks @bugsysha for the help, I tried moving the database to a private subnet as well, and all the deployed vapor projects failed to connect to the database.
Level 61
@hmawla contact Vapor support and ask what you need to change.
Level 8
Can you just use security group to restrict access to only the ip's you want to have access? This way it is private only to you and your infrastructure but without using private subnet?
Level 75
It's called an intranet, use authentication and authorization. Sure someone can land on the site, but they can't login or do anything.
Like an insurance companies physician portal, you may land on the login page, but can't login or do anything.
1 like
Level 1
Thank you all for the help, I think my best bet is to just create a private database in vapor and migrate all the data from my old instance to the new one and use it in the projects!
Please or to participate in this conversation.