BlogPostgreSQL

PostgreSQL 14 on Amazon RDS: End of Standard Support on 28 February 2027

Scott Sternloff

By Scott Sternloff, Senior Enterprise Architect

LinkedIn · Updated · 5 min read

PostgreSQL 14 on Amazon RDS: End of Standard Support on 28 February 2027
On this page

Short answer

Amazon RDS for PostgreSQL 14 reaches the end of standard support on 28 February 2027, per the AWS release calendar read on 18 November 2026. From 1 March 2027 RDS Extended Support is billed per vCPU-hour until 28 February 2030, when AWS upgrades the instance itself. The PostgreSQL community ended support for 14 on 12 November 2026. This guide covers the dates, the cost, the upgrade blockers and your options.

Amazon RDS for PostgreSQL 14 leaves standard support on 28 February 2027. From 1 March 2027 AWS bills RDS Extended Support per vCPU-hour, and when Extended Support ends on 28 February 2030 it upgrades the instance itself. The dates are from the AWS release calendar for RDS for PostgreSQL, read on 18 November 2026, 102 days before the standard support date.

Two dates are easy to confuse. The PostgreSQL community ended support for version 14 on 12 November 2026 with 14.25, its final minor release. RDS keeps patching 14 until the 28 February 2027 date. The community dates for every version are on PostgreSQL end of life dates by version.

RDS for PostgreSQL 14 dates

DateWhat happensSource
12 Nov 2026Community end of life; 14.25 is the final releasepostgresql.org
28 Feb 2027RDS end of standard support for PostgreSQL 14AWS calendar
1 Mar 2027RDS Extended Support year 1 pricing starts; instances are enrolled automaticallyAWS calendar
1 Mar 2029Extended Support year 3 pricing startsAWS calendar
28 Feb 2030RDS Extended Support ends; AWS upgrades to a supported major versionAWS calendar

Minor versions run out sooner. The calendar lists 14.18 and 14.19 as past standard support since 31 October 2026, and 14.20 as ending in February 2027. Run 14.24, the latest on the calendar, so a minor version does not force the issue first.

What RDS Extended Support costs

Paid Extended Support is billed per vCPU-hour, on top of instance charges, and Reserved Instance discounts do not apply to it. Rates vary by Region, engine version and years since standard support ended. AWS's pricing page shows $0.100 per vCPU-hour for years 1 and 2 and $0.200 for year 3, using PostgreSQL 12 in US East (Ohio) as the example. Check the rate for 14 in your Region.

As an illustration only, at the $0.100 rate a 4-vCPU instance running about 730 hours a month adds roughly $292 a month, and roughly $584 at $0.200. Multiply by every instance you run, including replicas.

For that money AWS provides security updates for critical and high CVEs, bug fixes for critical issues and support cases under the standard RDS SLA. Enrollment does not change the engine or affect uptime. If you disable enrollment on an instance already past standard support, AWS upgrades it to the next supported major version.

Which PostgreSQL version to upgrade to

TargetRDS end of standard supportRDS end of Extended Support
PostgreSQL 1529 Feb 202828 Feb 2031
PostgreSQL 1628 Feb 202929 Feb 2032
PostgreSQL 1728 Feb 203028 Feb 2033
PostgreSQL 1828 Feb 203128 Feb 2034

Upgrading 14 to 15 only buys a year of standard support, so you would repeat the exercise in early 2028. Most teams should target 17 or 18. RDS lets you jump straight to a later major version, skipping the majors in between; list the valid targets for your minor version with aws rds describe-db-engine-versions before you plan.

RDS upgrade gotchas when leaving PostgreSQL 14

AWS runs pg_upgrade under the hood, and its documentation lists the blockers. The ones that stop upgrades from 14:

  • Logical replication slots. An upgrade cannot proceed while any exist, and slots are only retained when the source is version 17 or later. DMS tasks and CDC pipelines (see PostgreSQL CDC with logical replication and Debezium) must be dropped and rebuilt.
  • Data types. Remove reg* columns other than regtype and regclass. Remove aclitem columns before moving to 16 or later, because its internal format changed in 16.
  • Read replicas. In-Region replicas are upgraded with the primary, and you are down until the upgrade finishes.
  • No rollback. After the upgrade you can only restore the pre-upgrade snapshot. Rehearse on a snapshot restore, and use a Blue/Green Deployment to cut downtime.
  • Statistics. Optimizer statistics are not carried over, so run ANALYZE on every database afterwards, and upgrade extensions separately.

A PostgreSQL health check before the move finds these, and PostgreSQL major version upgrades covers the cut-over itself.

Your options after 28 February 2027

  1. Upgrade before the date. No Extended Support bill, and you land on a version with years of patches.
  2. Pay for Extended Support while you test. It buys time, at a rate that doubles in year 3.
  3. Leave RDS for self-managed PostgreSQL 14. RDS does not let you install other builds, so third-party patches need EC2, Kubernetes or your own hosts. OSSeva, AceMQ's extended support platform, backports CVE fixes for versions the community has ended, and it covers PostgreSQL 14 now that community support has stopped. See OSSeva PostgreSQL extended support.

Whichever you choose, AceMQ's PostgreSQL support is 24/7 with a named senior engineer, for self-managed and cloud-hosted PostgreSQL including RDS. Support typically runs $24,000-72,000 a year (USD), by SLA, scope and deployment, and quote requests are answered within 1 hour.

Sources

Frequently Asked Questions

When does Amazon RDS for PostgreSQL 14 reach end of standard support?

28 February 2027, per the AWS release calendar read on 18 November 2026. RDS Extended Support year 1 pricing starts on 1 March 2027.

How long does RDS Extended Support last for PostgreSQL 14?

Until 28 February 2030. AWS offers Extended Support for up to three years past standard support, then upgrades the instance to a supported major version.

Is PostgreSQL 14 already end of life?

Yes, for the community. PostgreSQL 14.25 was the final release, on 12 November 2026. RDS still patches version 14 until 28 February 2027, and Extended Support after that.

Can I avoid RDS Extended Support charges?

Only by upgrading to a supported major version before 28 February 2027. If you turn enrollment off for an instance already past standard support, AWS upgrades it automatically.

Can I upgrade RDS PostgreSQL 14 straight to 17 or 18?

RDS lists valid upgrade targets per minor version. Check them with the AWS CLI, run a dry run on a snapshot restore, and remove logical replication slots first, since slots are only kept through upgrades from 17 and later.

Scott Sternloff

Author

Scott SternloffSenior Enterprise Architect

Senior Enterprise Architect at AceMQ. Writes the technical coverage here: RabbitMQ, Kafka and Redis architecture, clustering and migrations.

Talk to an engineer

Need a hand with PostgreSQL?

Senior engineers who run it in production. Get a quote or a free consultation, no sales pitch.

Free Consultation

Get Expert Eyes on Your PostgreSQL Environment

Whether you're troubleshooting a production incident, planning a migration, or want a second opinion on your architecture — our team is ready. No pitch, just answers.

Email Us