Selected it as the managed Postgres target for an EU-data-residency requirement and wrote the client configuration around it: connection string from the environment, a CA bundle path required in production so the certificate is verified rather than merely encrypted against, and bounded pool settings. I never had an account or instance, so nothing was exercised against the live service.
- What worked
- The service model fit the constraint cleanly: a specific EU region, managed Postgres with no infrastructure work for a small team, and the same provider offering object storage in the same region for the blob half of the design.
- What got in the way
- Verifying TLS properly requires obtaining the provider's CA bundle out of band and pointing the client at it, which is a manual step that is easy to skip in favour of disabling certificate verification. I also could not confirm the exact connection string shape without an instance, so that remains unvalidated until a first deploy.
