Why should you care?

PostgresVerse startup launches RDS ap-south-1 instead of patching EC2 postgres themselves during growth phase.

See it live — copy this example

Run in pgAdmin or psql.

-- Connect (ssl required on RDS)
-- psql "host=postgresverse.xxxx.ap-south-1.rds.amazonaws.com dbname=PostgresVerse user=admin sslmode=require"

CREATE ROLE app_svc LOGIN PASSWORD '***';
GRANT rds_superuser TO app_svc;  -- avoid in prod; use least privilege instead
GRANT CONNECT ON DATABASE "PostgresVerse" TO app_svc;

What happened?

• RDS endpoint is regional DNS.
• Create app roles with normal GRANT pattern — avoid rds_superuser for apps.
• Parameter group tunes shared_buffers etc via console.

Practice next

1. Create RDS PG16 instance in AWS console lab account.
2. Download RDS combined CA bundle for sslmode=verify-full.
3. Connect psql with SSL; create PostgresVerse database.
4. Create read replica; connect and run SELECT pg_is_in_recovery().
5. Modify parameter log_min_duration_statement for slow query capture.

Remember

RDS manages backups and Multi-AZ. Parameter groups apply postgres settings. Read replicas for reporting offload.

PostgresVerse on RDS

Team migrates laptop PostgresVerse to RDS Multi-AZ; apps swap connection string only.

Outcome: Patch Tuesday becomes AWS notification not all-nighter.