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.
Heya,
Since it’s a managed product you can’t modify some of the settings and if not mistaken changing the timeout is exactly that.
Having said that, I don’t see why you’ll need to do something like that. All in all, when connecting to your Database it should be to do an Operation and a connection shouldn’t stay long.
Is it possible you’ve not allowed your Droplet’s IP to your Managed Database?
Hi there,
You can modify the managed database cluster configurations using the DigitalOcean API:
https://docs.digitalocean.com/reference/api/api-reference/#operation/databases_patch_config
The curl request would look as follows:
curl -X PATCH \
-H "Content-Type: application/json" \
-H "Authorization: Bearer $DIGITALOCEAN_TOKEN" \
-d '{"config": {"connect_timeout": 3600}}' \
"https://api.digitalocean.com/v2/databases/9cc10173-e9ea-4176-9dbc-a4cee4c4ff30/config"
The connect_timeout config option accepts parameters between 2 and 3600.
An alternative option here is to use the doctl CLI tool instead of the HTTP API:
https://docs.digitalocean.com/reference/doctl/reference/databases/configuration/update/
Hope that this helps!
- Bobby