Competitive Comparison
Amazon RDS Extended Support: what it costs for PostgreSQL 14, and the alternatives
Amazon RDS Extended Support for PostgreSQL 14 starts on 1 March 2027 and is charged per vCPU-hour: AWS lists $0.10 in years 1 and 2 and $0.20 in year 3 for PostgreSQL in US East (N. Virginia). Enter your own vCPU count below to see your bill, then compare upgrading, paying AWS, and OSSeva patched builds for PostgreSQL you run yourself on EC2, Kubernetes or your own hardware.
Get a quote for self-managed PostgreSQL
Last reviewed against Amazon RDS Extended Support's own site.
Where OSSeva is stronger
- ✓Self-managed PostgreSQL on EC2, Kubernetes, another cloud or on premises, where RDS Extended Support does not apply
- ✓Patched RPM, DEB and tarball packages and Bitnami-compatible images for PostgreSQL 11 to 14, with extension compatibility validated
- ✓You choose when to upgrade: no automatic major-version upgrade when a support window closes
- ✓Migration planning, vacuum and configuration audits and 24/7 DBA-level operations from the same team
Where Amazon RDS Extended Support is stronger
- →Nothing to migrate: RDS and Aurora databases are enrolled automatically and keep running on the same engine
- →AWS builds the patched minor versions, such as 12.22-rds.20260514, and publishes them inside the managed service
- →Covers RDS for MySQL 5.7 and 8.0 as well as PostgreSQL; OSSeva supports self-managed MySQL, not MySQL inside RDS
- →Support cases within the standard RDS service level agreement, on the bill you already have
Trusted globally by enterprises





When RDS Extended Support starts for PostgreSQL 14
Community support for PostgreSQL 14 ends on 12 November 2026. AWS keeps RDS for PostgreSQL 14 and Aurora PostgreSQL 14 in standard support for a further three and a half months, and Extended Support charges start on 1 March 2027. Instances still running 14 on that date are enrolled automatically unless Extended Support was turned off when they were created.
| Event | Date |
|---|---|
| Community end of life (final minor release) | 12 November 2026 |
| RDS and Aurora end of standard support | 28 February 2027 |
| Extended Support year 1 pricing starts | 1 March 2027 |
| Extended Support year 3 pricing starts | 1 March 2029 |
| RDS and Aurora end of Extended Support | 28 February 2030 |
Source: the AWS RDS for PostgreSQL and Aurora PostgreSQL release calendars on docs.aws.amazon.com, read 20 October 2026. Community date checked against endoflife.date the same day.
What it costs: per vCPU-hour, year 1 and year 3
RDS Extended Support is charged per vCPU per hour for every provisioned instance, standbys and read replicas included, on top of the instance, storage and I/O charges you already pay. The rate doubles in year 3. Enter your own numbers to see the monthly and annual bill.
| Period | Rate per vCPU-hour | Monthly | Annual |
|---|---|---|---|
| Year 1 and 2 (from 1 March 2027) | $0.100 | $584 | $7,008 |
| Year 3 (from 1 March 2029) | $0.200 | $1,168 | $14,016 |
| Three years (two at year 1 rate, one at year 3) | 8 billed vCPUs | $28,032 | |
AWS rates copied 20 October 2026 from the AWS RDS for PostgreSQL pricing page and its price list. Extended Support is charged on top of your instance, storage and I/O costs, and every instance in a Multi-AZ deployment is billed, standby included. AWS lists these rates for PostgreSQL 10 to 13 and has not yet published a separate PostgreSQL 14 line, so this assumes the same per-vCPU rate applies to 14. Confirm in the AWS Pricing Calculator before you budget.
Capability comparison
Comparison based on AWS documentation, AWS price list data and the PostgreSQL versioning policy, read 20 October 2026. Verify current dates and rates with AWS.
| Capability | OSSeva | Amazon RDS Extended Support |
|---|---|---|
| PostgreSQL 14 after community end of life | Standard support to 28 Feb 2027, then Extended Support to 28 Feb 2030 | |
| PostgreSQL 11, 12 and 13 | Extended Support ends 31 Mar 2027, 29 Feb 2028 and 28 Feb 2029 | |
| Databases on RDS or Aurora | ||
| Self-managed PostgreSQL (EC2, Kubernetes, on premises) | ||
| MySQL 5.7 and 8.0 running inside RDS | ||
| Security fixes | Quarterly patch releases | Critical and high CVEs, critical bug fixes |
| Who applies the patches | You, or OSSeva on Operate | You, though AWS may apply critical ones |
| Enrollment | Subscription | Automatic unless EngineLifecycleSupport is disabled |
| When coverage ends | You choose when to upgrade | RDS attempts an automatic major-version upgrade |
| Extension compatibility validation | Not stated | |
| Major-version migration planning | Assure and Operate | |
| 24/7 DBA-level operations | Operate | Managed service operations |
| Pricing model | Per cluster | Per vCPU-hour (ACU-hour on Aurora Serverless), doubles in year 3; rates below |
RDS Extended Support rates (US East, N. Virginia)
AWS charges Extended Support per vCPU per hour on provisioned RDS and Aurora instances, and per ACU per hour on Aurora Serverless v2. The rate is the same for the first two years after standard support ends and doubles in year 3. For PostgreSQL 14 on RDS and Aurora, year 1 starts on 1 March 2027 and year 3 on 1 March 2029.
| Engine | Billed per | Years 1 and 2 | Year 3 |
|---|---|---|---|
| RDS for PostgreSQL, provisioned | vCPU-hour | $0.10 | $0.20 |
| RDS for MySQL 5.7 and 8.0, provisioned | vCPU-hour | $0.10 | $0.20 |
| Aurora PostgreSQL, provisioned | vCPU-hour | $0.10 | $0.20 |
| Aurora MySQL 2 (MySQL 5.7), provisioned | vCPU-hour | $0.10 | Not listed by AWS |
| Aurora Serverless v2 (PostgreSQL 13 to 15, MySQL 3) | ACU-hour | $0.085 | $0.170 |
Source: the AWS Price List for Amazon RDS (published 20 October 2026), the data behind aws.amazon.com/rds/postgresql/pricing, /rds/mysql/pricing and /rds/aurora/pricing. AWS rates copied 20 October 2026. AWS lists the PostgreSQL rate for versions 10 to 13 and has no PostgreSQL 14 entry in most Regions yet; its pricing page shows one rate for provisioned instances. Other Regions cost more: Ireland $0.112 and $0.224, Frankfurt $0.122 and $0.244, up to $0.210 and $0.419 in São Paulo, the most expensive Region AWS lists. Every instance in a Multi-AZ deployment is billed, standby included. Rates change; check the AWS Pricing Calculator before you budget.
What does RDS Extended Support cost? Worked examples
One year is 8,760 hours, each instance runs all year and the rate is the US East (N. Virginia) rate above. Year 1 means the first 12 months of Extended Support, so for PostgreSQL 14 that is 1 March 2027 to 28 February 2028, and nothing is charged before then. The last column is two years at the year 1 rate plus one at the year 3 rate.
| vCPUs billed | Example fleet | Year 1 | Year 3 | Three years |
|---|---|---|---|---|
| 8 | One 8 vCPU instance, Single-AZ | $7,008 | $14,016 | $28,032 |
| 32 | One 16 vCPU primary with a Multi-AZ standby | $28,032 | $56,064 | $112,128 |
| 96 | Three 16 vCPU primaries, each with a Multi-AZ standby | $84,096 | $168,192 | $336,384 |
| 16 ACU average | Aurora Serverless v2 running all year at 16 ACUs | $11,914 | $23,827 | $47,654 |
Arithmetic on the published rates: vCPUs x 8,760 x $0.10 for years 1 and 2, x $0.20 for year 3; ACUs x 8,760 x $0.085 and $0.170 for Serverless v2. Excludes the instance, storage and I/O charges you already pay. Read replicas are instances and are billed the same way.
Upgrade, pay AWS, or run patched builds yourself
There are three ways to get past the end of PostgreSQL 14. Each is right for a different set of databases, and most estates use more than one.
| Option | What it costs | Right when | The catch |
|---|---|---|---|
| Upgrade to PostgreSQL 17 or 18 | Engineering time: extension audit, rehearsal, a change window | You can schedule it. The Extended Support charge stops the day the instance is on a supported version | Scope depends on schema size, extension use, code volume and the downtime window you can get |
| Pay AWS (RDS or Aurora Extended Support) | Per vCPU-hour from 1 March 2027, doubling in year 3 (calculator above) | The database stays on RDS or Aurora and cannot move yet | Only inside the managed service. The bill follows vCPU count, and RDS attempts an automatic major-version upgrade when coverage ends |
| Self-managed patched builds (OSSeva) | A subscription per cluster, not per vCPU | PostgreSQL runs on EC2, Kubernetes, another cloud or on premises, or you are leaving RDS anyway | Does not apply to RDS or Aurora. Moving a database off RDS is a project with its own cost |
OSSeva cannot patch databases inside RDS or Aurora, because only AWS can change those engine builds. For those, upgrade or pay AWS.
A cheaper alternative to RDS Extended Support for self-managed PostgreSQL
Extended Support is a per-vCPU charge that doubles in year 3, so it grows with your fleet. If the PostgreSQL 14 you are paying for could run on EC2, Kubernetes or your own hardware, OSSeva Patch supplies patched PostgreSQL 11 to 14 builds after community end of life, with a published 48-hour target for critical fixes and 7 days for high, priced per cluster rather than per vCPU.
That only applies if you are willing to move the database off RDS, which has its own migration and operations cost. For databases that stay on RDS, Extended Support is usually the lower-effort choice. Send us your fleet's versions and vCPU counts and we will quote the self-managed option against the figures above.
Why teams choose OSSeva
For PostgreSQL you run yourself
RDS Extended Support exists only inside RDS and Aurora. If your PostgreSQL 14 runs on EC2 instances, in Kubernetes with Helm charts or an operator, in another cloud or on your own hardware, nothing from AWS patches it after 12 November 2026. OSSeva ships signed RPM, DEB and tarball packages and Bitnami-compatible images for PostgreSQL 11 to 14, with compatibility validated against widely used extensions such as PostGIS, pg_partman, pgvector and TimescaleDB.
Your upgrade date, not a calendar's
RDS Extended Support runs for up to three years after the end of standard support. After that, RDS attempts to upgrade the engine to a supported major version, and if the upgrade fails AWS reserves the right to delete the instance after preserving its data. Turning Extended Support off on a database already past its standard support date also triggers an automatic major-version upgrade. On self-managed PostgreSQL with OSSeva, the upgrade happens when your team schedules it.
A bill that does not follow vCPU count
RDS Extended Support is charged per vCPU per hour, including Multi-AZ standby instances, and the rate doubles in the third year (see the rate table above). On Aurora Serverless it is charged per ACU per hour. OSSeva prices per cluster, so adding cores to a busy database does not change the support bill. The Assure tier adds major-version migration planning, so the time you buy is used to get off the old version.
Why teams choose Amazon RDS Extended Support
No migration and no new vendor
If your databases already run on RDS or Aurora, Extended Support is the shortest path. Enrollment is automatic, it does not change the engine or affect uptime, and the charge stops as soon as you upgrade to a version in standard support. Moving a production database off RDS to keep a cheaper support option is a project in itself, and for many teams it is not worth it to buy two or three years.
Patches built by AWS for its own service
AWS publishes Extended Support minor versions with critical security patches and bug fixes for retired PostgreSQL majors, such as 11.22-rds.20260514 and 13.23-rds.20260514, released in September 2026. They are built for RDS and applied through RDS. Support cases are handled within the standard RDS service level agreement.
MySQL as well as PostgreSQL
RDS for MySQL 5.7 and 8.0 are now available only under Extended Support, with 5.7 covered to 30 June 2029 and 8.0 to 31 July 2029. OSSeva supports MySQL only when you run it yourself, so for a mixed estate that stays inside RDS, Extended Support covers both engines with one mechanism. Moving MySQL to self-managed servers brings it under OSSeva with the rest of the stack (see OSSeva MySQL support).
Which is right for your situation?
Choose OSSeva when…
Your PostgreSQL 11 to 14 runs outside RDS and Aurora, on EC2, Kubernetes, another cloud or on premises, and you need patched builds past community end of life, or you want migration planning and 24/7 operations from one team.
Talk to an engineerConsider Amazon RDS Extended Support when…
Your databases run on RDS or Aurora and will stay there, you run RDS for MySQL 5.7 or 8.0, or you want fixes applied inside the managed service without changing vendors. That is most RDS customers.
RDS and Aurora Extended Support cover PostgreSQL 11 to 14 and MySQL 5.7 and 8.0 inside AWS's managed services, for up to three years past standard support. OSSeva covers self-managed PostgreSQL 11 to 18, including 11 to 13 past community end of life, and self-managed MySQL 5.7, 8.0, 8.4 and 9.7.
Frequently asked questions
When does PostgreSQL 14 reach end of life?
The PostgreSQL Global Development Group supports each major version for five years, and lists 12 November 2026 as the final release for PostgreSQL 14. After that the community publishes no further fixes for it. PostgreSQL 13 ended on 13 November 2025.
What happens to PostgreSQL 14 on RDS and Aurora?
AWS keeps RDS for PostgreSQL 14 and Aurora PostgreSQL 14 in standard support until 28 February 2027. From 1 March 2027 they move into RDS Extended Support at the year 1 rate, the year 3 rate starts on 1 March 2029, and Extended Support ends on 28 February 2030. Check the AWS release calendars for the current dates.
How is RDS Extended Support priced?
Per vCPU per hour on provisioned RDS and Aurora instances, and per ACU per hour on Aurora Serverless. In US East (N. Virginia), AWS lists $0.10 per vCPU-hour for the first two years after standard support ends and $0.20 in year 3, and $0.085 then $0.170 per ACU-hour on Aurora Serverless v2. Other Regions cost more, and Multi-AZ standby instances are charged too. Charges start the day after standard support ends and stop when you upgrade or delete the database.
What does RDS Extended Support cover?
Security updates for critical and high CVEs as rated by NVD CVSS, bug fixes and patches for critical issues, and support cases within the standard RDS service level agreement, for up to three years past the end of standard support. You are responsible for applying the patches, although AWS may apply or require a patch for security or critical stability issues.
How much does RDS Extended Support cost for PostgreSQL 14?
AWS had not listed a separate PostgreSQL 14 price on 20 October 2026, because Extended Support for it starts on 1 March 2027. For the other RDS for PostgreSQL versions AWS lists $0.10 per vCPU-hour in years 1 and 2 and $0.20 in year 3 in US East (N. Virginia), and the calculator on this page applies those rates to 14. At that rate an 8 vCPU instance running all year costs $7,008, and a 32 vCPU instance $28,032, before the Multi-AZ standby is counted. Confirm the PostgreSQL 14 rate for your Region in the AWS Pricing Calculator.
When does RDS Extended Support start for PostgreSQL 14?
On 1 March 2027. The AWS release calendar lists 28 February 2027 as the end of standard support for RDS for PostgreSQL 14 and Aurora PostgreSQL 14, year 3 pricing from 1 March 2029, and the end of Extended Support on 28 February 2030. Community support ends earlier, on 12 November 2026.
What is cheaper than Amazon RDS Extended Support?
Upgrading is cheaper than any extended support, because the charge stops the day you move to a version in standard support. For PostgreSQL you run yourself, OSSeva patched PostgreSQL 11 to 14 builds on EC2, Kubernetes or on premises are the alternative, priced per cluster rather than per vCPU. Moving a database off RDS is a project with its own cost, so for databases that stay on RDS, Extended Support is usually the cheaper path. Contact us for a quote against your own fleet.
Which vendors offer extended security support for PostgreSQL 13 after it reached end of life?
PostgreSQL 13 reached community end of life on 13 November 2025. If it runs on Amazon RDS or Aurora, AWS sells Extended Support for it from 1 March 2026 to 28 February 2029. If it runs on your own servers, independent providers sell patched builds, and OSSeva is one: Patch, Assure and Operate cover PostgreSQL 13 on EC2, Kubernetes or on premises. Azure has its own extended support dates for Azure Database for PostgreSQL.
Can OSSeva patch our RDS or Aurora databases?
No. RDS and Aurora run engine builds that only AWS can change. OSSeva is for PostgreSQL you operate yourself. If you are on RDS and want to stay there, Extended Support is the right tool.
Does OSSeva cover MySQL?
For self-managed MySQL, yes: OSSeva ships patched 5.7 and 8.0 builds and supports 8.4 LTS. Inside RDS, AWS controls the binaries, so RDS Extended Support is the option for RDS for MySQL 5.7 and 8.0.
Can we use both?
Yes. A common pattern keeps the RDS databases on Extended Support and puts OSSeva on the self-managed PostgreSQL that RDS does not reach, such as databases in Kubernetes or in data centres.
Self-managed PostgreSQL 14? Get a quote against your fleet.
Send your work email and an engineer replies within 1 business day with a quote for your clusters.