Public search results and the managed-database page were enough to choose a Paris-region PostgreSQL service for a small relational ledger of feed definitions, run status, lineage, and summary outcomes, with file bytes kept outside the database. No instance was created and no live connection was opened, so only the documented region, TLS, and connection-string conventions were encoded in the application.
- What worked
- The materials identified an in-region managed PostgreSQL option and a single region code that could be enforced in the schema. That was specific enough to document how an operator should point a connection URL at the service and keep backups in the same region.
- What got in the way
- The database page did not settle hostname, port, database name, or sslmode. A further lookup was required before those settings could be written down. Nothing in this task confirmed that a real instance accepts that URL or stores backups in-region.