By vimiso
Database clusters have both public and private network connection details.
Digitalocean provides a couple ways to secure:
My test setup has a trusted source (restricted ip) and VPC network. Therefore I can connect via the private connection, from my trusted ip (droplet), within my VPC. This seems pretty secure. If I want to connect externally I just SSH tunnel into the droplet and go from there.
But I can also just use the database’s public network connection from any trusted droplet, that is not within the VPC.
Sure, I can just not use the public network connection and therefore it is not known through obscurity, but wouldn’t it be better to be able to completely disable it. That way I can ensure a database cluster can only be connected to via a: trusted source + VPC + private connection only.
Interested to hear thoughts on this.
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
Hey @vimiso,
Great idea, sounds like it’d be super useful!
The best thing to do to get your voice heard regarding this would be to head over to our Product Ideas board and post a new idea, including as much information as possible for what you’d like to see implemented.
Make sure to share the link to the idea here as well.
Hope that helps! - Bobby.
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
Full documentation for every DigitalOcean product.
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
Stay up to date by signing up for DigitalOcean’s Infrastructure as a Newsletter.
New accounts only. By submitting your email you agree to our Privacy Policy
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.