Christophe Pettus: Managed Postgres, Examined: Amazon RDS for PostgreSQL
Amazon RDS for PostgreSQL is a managed database service that runs unmodified community PostgreSQL on EC2 instances with EBS storage, offering a straightforward architecture focused on ease of management. It provides automated provisioning, patching, backups, and high availability through AWS's control plane, without forking the PostgreSQL codebase. The service imposes operational constraints such as no shell access, limited superuser privileges, and reliance on AWS-specific mechanisms for replication and failover.
- ▪Amazon RDS for PostgreSQL runs unmodified community PostgreSQL on EC2 instances with EBS storage.
- ▪High availability is achieved through synchronous block-level replication at the EBS layer, not PostgreSQL streaming replication.
- ▪The standby instance in a Multi-AZ deployment is not readable and failover typically takes 60–120 seconds.
- ▪Storage types include gp3, io1, io2, and io2 Block Express, with options for provisioned IOPS and online resizing.
- ▪Users interact with the database via the Postgres wire protocol and AWS APIs, with no direct filesystem or shell access.
Opening excerpt (first ~120 words) tap to expand
2026-04-28 13 min PostgreSQL #RDS Managed Postgres, Examined: Amazon RDS for PostgreSQL First in a series of dispassionate surveys of the major managed-Postgres offerings. This post is about Amazon RDS for PostgreSQL — what AWS calls “traditional RDS,” as distinct from Aurora PostgreSQL, which is a separate product with a separate architecture and will get its own post. Overview Amazon RDS for PostgreSQL is the oldest and most widely deployed managed-Postgres product in the market. The architecture is straightforward: AWS runs community PostgreSQL, unmodified, on an EC2 instance that you don’t have shell access to, backed by EBS storage, with a control plane that handles provisioning, patching, backups, monitoring, and failover.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Postgr.
Discussion
0 commentsMore from Postgr
