From Self-hosted Postgres to Obsfly

• Patch management, replica failover, and PITR backups consume engineer-weeks per quarter.
• AWS RDS / Aurora / GCP Cloud SQL handle the boring parts.
• Compliance-grade backups and encryption are turnkey.
• Obsfly works against managed Postgres exactly the same as self-hosted — no telemetry gap.

Fairness signal — useful in renewal conversations.

• Self-hosted Postgres gives you superuser, custom extensions, no per-IOPS surprise bills.
• Cheaper at extreme scale (1k+ DBs) when you have the team to run it.

1. Step 1

   Snapshot baseline performance

   Export Obsfly's top-100 query distribution from the self-hosted cluster.

2. Step 2

   Provision target RDS / Aurora cluster

   Match instance class to current workload + 25% headroom.

3. Step 3

   Logical replication or pg_dump cutover

   Pg 16+ logical replication keeps downtime minimal. pg_dump if you can take a maintenance window.

4. Step 4

   Re-baseline post-cutover

   Compare p99 / cache hit rate / replica lag in Obsfly. RDS Performance Insights complements but doesn't replace per-query depth.

• Custom extensions: verify RDS supports each one before cutover.
• Connection limits differ between self-hosted (max_connections) and RDS-tier-based limits.

Does Obsfly work with RDS Postgres?

Yes — read-only role, no agent. Performance Insights and pg_stat_statements both surface in Obsfly.