// Competitive Comparison
OSSeva vs. Amazon RDS Extended Support
PostgreSQL 14 reaches community end of life on 12 November 2026. On RDS and Aurora it stays in standard support until 28 February 2027 and then moves into paid Extended Support, which is the natural path if the database stays on AWS's managed service. OSSeva patches PostgreSQL 11 to 14 that you run yourself, on EC2, Kubernetes or your own hardware.
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 does not support MySQL
- →Support cases within the standard RDS service level agreement, on the bill you already have
Trusted globally by enterprises
Capability comparison
Comparison based on AWS documentation and the PostgreSQL versioning policy as of October 2026. Verify current dates in the AWS release calendars.
| 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 | ||
| 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), higher from year 3 |
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 rises from the third year. 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 does not support MySQL, so for a mixed RDS estate Extended Support covers both engines with one mechanism.
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 16, including 11 to 14 past community end of life.
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. The same rate applies for the first two years after standard support ends, and a higher rate applies in year 3. Rates vary by Region, 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. We do not reproduce AWS's prices; the RDS and Aurora pricing pages have them.
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.
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?
No. OSSeva covers PostgreSQL 11 to 16, including 11 to 14 past community end of life. For RDS for MySQL 5.7 and 8.0, RDS Extended Support is the option AWS provides.
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.
Ready to see if OSSeva covers your stack?
Book a 30-minute discovery call. We'll confirm version coverage and scope a proposal within 5 business days.