Hosted Databases

The Short Version

A managed database is just a database with a hostname, credentials, and usually TLS and an IP allow-list. Get those four things right and Sutido connects like to anything else. When a provider doesn't expose the database publicly at all, an SSH tunnel through a VM in the same network is the universal way in.

MongoDB Atlas

1. In Atlas: Database → Connect → "Drivers", and copy the mongodb+srv:// string
2. In Atlas: Network Access → add your IP to the IP Access List
3. In Sutido: paste the string into Import URI, replace <password> with your database user's password, and Test connection

The mongodb+srv:// form resolves the cluster via DNS and implies TLS — no extra configuration needed in Sutido.

PostgreSQL & SQL Server in the Cloud

Managed Postgres (RDS, Aurora, Azure Database, Cloud SQL) and Azure SQL / managed SQL Server work with the regular connection form. The usual checklist:

• Use the hostname from the provider's console, not an IP — they rotate
• Open the provider's firewall / security group for your IP
• Some providers require full server usernames (e.g. user@servername on Azure)

ClickHouse Cloud & Self-Hosted

Sutido talks to ClickHouse over its HTTP interface. For hosted offerings, use the HTTPS hostname and port from your provider's console and your database credentials.

Kubernetes & Private Networks

For databases that are only reachable inside a cluster or VPC, tunnel through something that can reach them: an SSH bastion (built into Sutido) or a port-forward such as kubectl port-forward, then connect to localhost.

Credential Hygiene

• Create a dedicated, least-privilege database user for GUI access
• Prefer read-only users for exploring production
• Sutido stores whatever credentials you enter encrypted and local-only — see Authentication & Secrets

Troubleshooting

Connection times out

Almost always the network path: IP allow-list, security group, or the database simply not being publicly exposed. Verify with the provider's own connectivity test if it has one.

Authentication failed against a managed service

Managed services often separate console accounts from database users — make sure you're using the database user's credentials.