// guides/aurora-postgresql-14-end-of-standard-support

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.

Get Aurora PostgreSQL 14 in the Monday emailFree Monday email. Aurora PostgreSQL 14 is listed every week from 90 days before Feb 28, 2027, plus anything else ending soon. Unsubscribe anytime.

Last checked against AWS documentation:

Aurora PostgreSQL 14 dates

MilestoneDate
Community end of lifeNovember 2026 (AWS gives the month only)
Aurora end of standard supportFeb 28, 2027
Extended Support year 1 pricing startsMar 1, 2027
Extended Support year 3 pricing startsMar 1, 2029
End of Extended SupportFeb 28, 2030

Sooner: 14.x minor versions

Minor versionAurora end of standard support
14.17Nov 30, 2026
14.18Dec 31, 2026
14.6 (LTS), 14.19, 14.20, 14.22, 14.23, 14.24Feb 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

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–2Year 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

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 text

Run 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

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

  1. Test on a clone or a restored snapshot first, with a parameter group for the new version ready.
  2. Drop any logical replication slots (the upgrade can't proceed with them) and commit or roll back open prepared transactions.
  3. Remove columns using reg* types other than regtype and regclass.
  4. Update extensions such as PostGIS and pgRouting before upgrading, and run ALTER EXTENSION ... UPDATE after, since the upgrade doesn't update extensions.
  5. After the upgrade, run ANALYZE in every database, because optimizer statistics aren't carried over.
  6. To cut downtime, consider Aurora Blue/Green Deployments, which AWS says typically switch over in under a minute.

Sources

Get warned 90 days before AWS end-of-support deadlines

Every Monday: each AWS version (EKS, RDS, Aurora, Lambda and more) leaving standard support in the next 90 days, and the extended-support fee AWS starts charging. Enough lead time to upgrade first. Free.

Free weekly email, Mondays. Unsubscribe anytime.

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

Sponsored
Your tool here
Reach engineers planning AWS upgrades. Sponsor EOLWatch.
Sponsor →