Updated October 25, 2026
· ~2 min read
Running databases on Kubernetes stopped being a joke somewhere around 2023, mostly because of operators like CloudNativePG, which handles PostgreSQL failover, backups to object storage, point-in-time recovery and rolling minor upgrades the Kubernetes way. It is a CNCF project and widely used in production.
The question is no longer whether Postgres can run on Kubernetes, but whether it should on AWS, where RDS and Aurora do the same jobs as a service — and, since 2024, charge for Extended Support when a major version ages out, which has made some teams look harder at the alternative.
Preview environments and per-tenant databases are the clearest case: spinning up a small Postgres per pull request or per customer as pods on shared nodes costs a fraction of an RDS instance each, and the operator makes them disposable. Portability is the other — the same manifests run on EKS, another cloud or on-premises. And some teams need extensions or server settings that managed services restrict.
Storage performance and durability become yours: EBS volume types and IOPS, and making sure replicas land in different zones. Restore testing becomes yours — an untested backup is a hope. Major upgrades need a plan and a rehearsal. And an incident in the database is now an incident in your Kubernetes cluster too, which is a different on-call skill. None of this is exotic, but it is work RDS does for you.
Question 1 of 1
Is this a production system of record on AWS?
On AWS, keep production PostgreSQL on RDS or Aurora unless you have a specific reason not to: backups, failover, patching and storage durability are handled, and Blue/Green Deployments make major upgrades a planned afternoon. Run CloudNativePG when the same database stack must run outside AWS too, when you need many small databases cheaply (per-tenant or per-preview-environment), or when you need extensions or configuration RDS does not allow. Extended Support charges are a reason to upgrade on schedule, not a reason to leave.
AWS Cost Optimization & FinOps Sprint
Reduce your AWS bill by 20–60% while improving performance and reliability.
Multi-Tenant SaaS Platform Architecture
Production-ready SaaS architecture supporting secure multi-tenant isolation and rapid scaling.
Production EKS Platform
A production-ready Kubernetes platform on EKS with Karpenter, GitOps, service mesh, full observability stack, and security hardening: built to run real workloads.
We work with startups and growing companies on AWS architecture decisions. Tell us about your situation and we will recommend the right approach.
As of October 25, 2026. Provided as is, for general information, and accurate to the best of our knowledge on the date shown. Not legal, compliance, tax, financial or other professional advice. Prices, limits and vendor services change; check current vendor documentation before relying on anything here. Terms of use.