Featured AI Products
Compute
Build, deploy, and scale cloud compute resources
Containers and Images
Safely store and manage containers and backups
Managed Databases
Fully managed resources running popular database engines
Management and Dev Tools
Control infrastructure and gather insights
Networking
Secure and control traffic to apps
Security
Help protect your account and resources with these security features
Storage
Store and access any amount of data reliably in the cloud
Browse all products
AI/ML
CMS
Data and IoT
Developer Tools
Gaming and Media
Hosting
Security and Networking
Startups and SMBs
Web and App Platforms
See all solutions
Community
Documentation
Developer Tools
Get Involved
Utilities and Help
Become a Partner
Marketplace
Pricing

- Community
- DigitalOcean
- Community
- DigitalOcean

Will we ever access our managed databases through private IP?

Posted on February 25, 2019

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.

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!

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.

abearfield

July 19, 2019

Accepted Answer

Private IP connectivity is now supported for Managed Databases!

liveb4buy

April 18, 2019

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.

jarland

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.

Jarland

The developer cloud

Scale up as you grow — whether you're running one virtual machine or ten thousand.

View all products

Start building today

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.