Will we ever access our managed databases through private IP?

So I’ve started using the managed databases, granted I impulsively did it, not for leaving MySQL intentionally, I would have stayed if that launched first, but because of a reliable cluster.

But anyways. Is there a special case as to why we’re only using a domain to access our cluster instead of IP? Such as routing behind the address due to it being a cluster, or simply out of proxying and security?

As I transitioned over I only noticed an additional 2ms-5ms in latency vs using a local database through socket, which is not bad at all, but I wonder if directly connecting through a private IP would be beneficial over the domain, because currently, I don’t know if we’re routing directly to the management database in the same datacenter or not.

Anyways, thanks for taking the time to look over the question, it’s been on my mind for the past week.

Submit an answer

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!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

DigitalOcean Employee
DigitalOcean Employee badge
July 19, 2019
Accepted Answer

Private IP connectivity is now supported for Managed Databases!

Did you secure the connection via SSL cert provided by DO? print(“Using psycopg2”) import psycopg2 myConnection = psycopg2.connect( host=hostname, user=username, password=password, dbname=database, sslmode=‘verify-ca’, sslrootcert=sslrootcert,sslcert=sslcert , sslkey=sslkey)

I am unable to get the SSL Key for that purpose? Can anyone pls share how to get SSL Key from the Managed Postgres SQL’s SSL setup?

Thanks and Advance.

DigitalOcean Employee
DigitalOcean Employee badge
February 25, 2019

Hey friend!

Great questions. I believe the thought behind hostname is just that it’s easier to commit to a hostname than an IP, and it gives us some of the management power there. Likely never relevant, but some things you regret later if you don’t implement before you know you need them.

Private IP access to your managed database is absolutely coming. We intend to have that implemented before we start billing for bandwidth on the product. No one wants to pay for bandwidth between their droplet and database, and our intent is to provide that clear path.


Try DigitalOcean for free

Click below to sign up and get $200 of credit to try our products over 60 days!

Sign up

Featured on Community

Get our biweekly newsletter

Sign up for Infrastructure as a Newsletter.

Hollie's Hub for Good

Working on improving health and education, reducing inequality, and spurring economic growth? We'd like to help.

Become a contributor

Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.

Welcome to the developer cloud

DigitalOcean makes it simple to launch in the cloud and scale up as you grow — whether you're running one virtual machine or ten thousand.

Learn more
DigitalOcean Cloud Control Panel