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

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

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.
Accepted Answer
Hi @bbkkbbkk,
Restricting access to specific ports or IPv6 addresses is not currently supported with DO Managed database.
As we continue to work on improving our products and services, we encourage you to share your thoughts, ideas, or feedback you have at https://ideas.digitalocean.com/
This will help us to better prioritize features that you feel need more attention.
Regards, Rajkishore
Quite sad. I have the same problem here. I have ipv6 at the home/office, and I can’t access the database. I would say that the alternative is to create a jump box inside a droplet.
Since my app is not in production yet, I only remove all trusted sources whenever I’m connected directly to the database.
But soon will be, and I can’t afford to remove the trusted sources and leave them open.
Quite sad. My case is Postgres Managed DB, I have the same problem here. I have ipv6 at the home/office, and I can’t access the database. I would say that the alternative is to create a jump box inside a droplet.
Since my app is not in production yet, I only remove all trusted sources whenever I’m connected directly to the database.
But soon will be, and I can’t afford to remove the trusted sources and leave them open.