Amazon Aurora PostgreSQL 18 · Version Status
Amazon Aurora PostgreSQL 18 End of Life Date
Amazon Aurora PostgreSQL 18 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.
✓
Amazon Aurora PostgreSQL 18 is actively supported. EOL date: February 28, 2031.
📅 Get reminded before Amazon Aurora PostgreSQL 18 reaches EOL on February 28, 2031 — alerts 90, 30 & 7 days out.
✓ Alerts are on — confirmation is in your inbox.
EOL Date
Feb 28, 2031
1584 days remaining
Latest Release
18.6
Standard release
Release Date
Feb 26, 2026
Amazon Aurora PostgreSQL 18 series
Extended Support
Feb 28, 2034
Amazon RDS Extended Support · paid
Where these dates come from
End of lifeFeb 28, 2031endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees End of extended supportFeb 28, 2034endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees ReleaseFeb 26, 2026endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees Confidence: high = two or more independent sources agree (the vendor's page read by our adapter, a person's check against the vendor, the dataset the date came from); medium = one; low = the vendor page disagrees or our last read is stale.
How we source dates.
Lifecycle detail
Amazon Aurora PostgreSQL 18 was released on February 26, 2026 and support is scheduled to end on February 28, 2031 — a planned supported lifespan of 5 years, in line with the 5 years and 5 months median for Amazon Aurora PostgreSQL releases. Its most recent patch is 18.6, published September 29, 2026.
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build.
Methodology → ·
View score card →
All Amazon Aurora PostgreSQL Versions
| Version | Latest | EOL Date | Status |
|---|
| 11 |
11.21 |
Feb 29, 2024 |
EOL |
| 12 |
12.22 |
Feb 28, 2025 |
EOL |
| 13 |
13.23 |
Feb 28, 2026 |
EOL |
| 14 |
14.24 |
Feb 28, 2027 |
Warning |
| 15 |
15.19 |
Feb 29, 2028 |
Active |
| 16 |
16.15 |
Feb 28, 2029 |
Active |
| 17 |
17.11 |
Feb 28, 2030 |
Active |
| → 18 |
18.6 |
Feb 28, 2031 |
Active |
What does Amazon Aurora PostgreSQL 18 end of life mean?
When Amazon Aurora PostgreSQL 18 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running Amazon Aurora PostgreSQL 18 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to Amazon Aurora PostgreSQL 18 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Amazon Aurora PostgreSQL 18 reach end of life?
Amazon Aurora PostgreSQL 18 reaches end of life on February 28, 2031. That is 1584 days remaining.
Is Amazon Aurora PostgreSQL 18 still supported?
Yes, Amazon Aurora PostgreSQL 18 is currently supported. The EOL date is February 28, 2031.
What should I upgrade to from Amazon Aurora PostgreSQL 18?
The recommended upgrade from Amazon Aurora PostgreSQL 18 is
Amazon Aurora PostgreSQL 18 — the latest actively supported version. Check the
Amazon Aurora PostgreSQL full timeline for all supported versions.
What are the security risks of running Amazon Aurora PostgreSQL 18 past EOL?
When Amazon Aurora PostgreSQL 18 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL Amazon Aurora PostgreSQL should migrate immediately or implement compensating controls.