Aurora PostgreSQL 14 end of standard support: Feb 28, 2027
Amazon Aurora PostgreSQL 14 reaches end of standard support on Feb 28, 2027. From Mar 1, 2027, clusters still on 14 are automatically enrolled in RDS Extended Support and billed per vCPU-hour, until Extended Support ends Feb 28, 2030. Minor version 14.17 leaves standard support sooner, on Nov 30, 2026.
Last checked against AWS documentation:
Aurora PostgreSQL 14 dates
| Milestone | Date |
|---|---|
| Community end of life | November 2026 (AWS gives the month only) |
| Aurora end of standard support | Feb 28, 2027 |
| Extended Support year 1 pricing starts | Mar 1, 2027 |
| Extended Support year 3 pricing starts | Mar 1, 2029 |
| End of Extended Support | Feb 28, 2030 |
Sooner: 14.x minor versions
| Minor version | Aurora end of standard support |
|---|---|
| 14.17 | Nov 30, 2026 |
| 14.18 | Dec 31, 2026 |
| 14.6 (LTS), 14.19, 14.20, 14.22, 14.23, 14.24 | Feb 28, 2027 |
Aurora's calendar lists these 14.x minor versions. Which 14.x minors are eligible for Extended Support is still marked “to be determined” by AWS. AWS says Aurora won't upgrade your minor version until after the major version's end of standard support date, and will then move you to the last minor version released before that date.
What happens on Mar 1, 2027
- If you didn't turn off Extended Support when you created or restored the cluster, Aurora automatically enrolls it after the end of standard support date. Enrollment doesn't change the engine or affect uptime.
- AWS says charges begin the day after the end of standard support date.
- Extended Support covers security updates for critical and high CVEs, bug fixes for critical issues, and support cases.
- You can create new clusters on 14 after Feb 28, 2027; they're enrolled and charged too.
What Extended Support costs
AWS prices Extended Support per vCPU-hour for provisioned instances and per ACU-hour consumed for Aurora Serverless. It depends on the Region and the calendar date. AWS doesn't list a rate for 14 specifically; its published example is for Aurora PostgreSQL 12 in US East (Ohio): $0.100 per vCPU-hour in years 1–2 and $0.200 from year 3.
| Instance (illustrative, at AWS's example rate, 730 h) | Years 1–2 | Year 3 |
|---|---|---|
| 2 vCPU | +$146/mo | +$292/mo |
| 4 vCPU | +$292/mo | +$584/mo |
| 8 vCPU | +$584/mo | +$1,168/mo |
| 16 vCPU | +$1,168/mo | +$2,336/mo |
Our math, not an AWS quote: it applies the example rate to PostgreSQL 14's year 1 (from Mar 1, 2027) and year 3 (from Mar 1, 2029) dates. Check the Aurora pricing page ↗ for your Region. Charges apply on top of your normal instance cost, on every instance in the cluster including readers. More: RDS & Aurora extended support pricing.
Opting out forces an upgrade
- Normally Aurora never applies major version upgrades on its own.
- But AWS says that if you disable Extended Support on a cluster already past its end of standard support date, the cluster automatically upgrades to the next supported major version.
- Extended Support is also not forever: AWS says if you haven't upgraded by the end of Extended Support, Aurora automatically upgrades your major version.
- Charges stop when you upgrade to a version in standard support or delete the cluster.
The opt-out flag is open-source-rds-extended-support-disabled on --engine-lifecycle-support.
Find your Aurora PostgreSQL 14 clusters
aws rds describe-db-clusters \
--query "DBClusters[?Engine=='aurora-postgresql' && starts_with(EngineVersion,'14.')].[DBClusterIdentifier,EngineVersion,EngineLifecycleSupport]" \
--output table
aws rds describe-db-engine-versions --engine aurora-postgresql --engine-version 14.24 \
--query "DBEngineVersions[].ValidUpgradeTarget[?IsMajorVersionUpgrade==`true`].{EngineVersion:EngineVersion}" \
--output textRun per Region. EngineLifecycleSupport shows open-source-rds-extended-support for enrolled clusters. The second command lists valid major upgrade targets for your exact version.
Where to upgrade
- Aurora PostgreSQL 15: standard support to Feb 29, 2028.
- Aurora PostgreSQL 16: to Feb 28, 2029.
- Aurora PostgreSQL 17: to Feb 28, 2030.
- Aurora PostgreSQL 18: to Feb 28, 2031.
AWS doesn't apply major upgrades automatically; you modify the cluster with --allow-major-version-upgrade. Aurora takes a snapshot before the upgrade and uses pg_upgrade; after the writer finishes, each reader has a brief outage. For a global database, all clusters are upgraded at the same time. Not every version is a direct target, so use the command above and hop through minor versions if needed.
Upgrade checklist
- Test on a clone or a restored snapshot first, with a parameter group for the new version ready.
- Drop any logical replication slots (the upgrade can't proceed with them) and commit or roll back open prepared transactions.
- Remove columns using
reg*types other thanregtypeandregclass. - Update extensions such as PostGIS and pgRouting before upgrading, and run
ALTER EXTENSION ... UPDATEafter, since the upgrade doesn't update extensions. - After the upgrade, run
ANALYZEin every database, because optimizer statistics aren't carried over. - To cut downtime, consider Aurora Blue/Green Deployments, which AWS says typically switch over in under a minute.
Sources
- AWS: Release calendars for Aurora PostgreSQL (major and minor versions) ↗
- AWS docs: Overview of RDS Extended Support (Aurora) ↗
- AWS docs: RDS Extended Support charges (Aurora) ↗
- Amazon Aurora pricing: RDS Extended Support costs and example ↗
- AWS docs: Performing a major version upgrade (Aurora PostgreSQL) ↗
- AWS docs: Viewing Extended Support enrollment (Aurora) ↗
- AWS docs: Aurora Blue/Green Deployments overview ↗
FAQ
When does Aurora PostgreSQL 14 reach end of standard support?
Feb 28, 2027, per the AWS Aurora PostgreSQL release calendar. The community end of life is listed as November 2026.
How much does Aurora PostgreSQL 14 Extended Support cost?
It is billed per vCPU-hour for provisioned instances and per ACU-hour for Aurora Serverless, and varies by Region and date. AWS's example, for Aurora PostgreSQL 12 in US East (Ohio), is $0.100 per vCPU-hour in years 1 and 2 and $0.200 in year 3. For version 14, year 1 pricing starts Mar 1, 2027 and year 3 starts Mar 1, 2029.
How long can I stay on Aurora PostgreSQL 14?
Until Feb 28, 2030, the end of RDS Extended Support for Aurora PostgreSQL 14. After that, AWS automatically upgrades the major version.
Which Aurora PostgreSQL 14 minor versions end first?
14.17 reaches end of standard support on Nov 30, 2026 and 14.18 on Dec 31, 2026. 14.19 through 14.24, and the 14.6 LTS release, run to Feb 28, 2027.
More guides
- EKS extended support cost calculator
- RDS & Aurora extended support pricing
- RDS MySQL 8.0 end of support
- RDS PostgreSQL end-of-support dates
- Lambda runtime deprecation schedule
- ElastiCache for Redis OSS end of support
- OpenSearch & Elasticsearch end of support
- OpenSearch extended support fees from Nov 7, 2026
- Lambda Python 3.10 deprecation (Oct 31, 2026)
- RDS MariaDB 10.6 end of support (Dec 31, 2026)
- EKS 1.31 end of extended support (Nov 26, 2026)
- RDS PostgreSQL 14 end of standard support (Feb 28, 2027)
- Lambda .NET 8 deprecation (Nov 10, 2026)
- Amazon Neptune 1.1/1.2 end of life (Dec 4, 2026)
- RDS MySQL 8.4.5/8.4.6/8.4.7 end of standard support (Oct 31 & Nov 30, 2026)
- EKS 1.34 end of standard support (Dec 2, 2026)
- ElastiCache Redis OSS 6 end of standard support (Jan 31, 2027)