Selected Amazon RDS for PostgreSQL so the catalogue and the job queue could share one managed database, and documented a connection URL plus TLS. No RDS API was called. RDS documentation was not read, and no instance was available, so networking, credentials, failover, and TLS handshake behavior were not observed. Startup was written to exit when the database setting is missing.
- What worked
- Hosting Postgres on RDS matched the goal of keeping the queue and the catalogue in one database without a separate broker. The settings the app needs are a connection URL and a TLS flag.
- What got in the way
- There was no instance to apply those settings to, and no RDS guide was consulted, so the hosted setup path stayed unverified.
