Amazon Rds Postgresql End of Life Dates
database
Developers rely on Amazon RDS Postgresql for its ability to create and manage PostgreSQL databases in the cloud, simplifying the process of deploying and scaling databases. Initially released by Amazon Web Services, the service has been maintained and updated regularly to ensure it remains a secure and reliable option for database management. With a history of providing stable and supported versions, Amazon RDS Postgresql has become a go-to choice for developers who need to manage PostgreSQL databases without the hassle of manual maintenance. The service is particularly useful for developers who want to focus on building applications rather than managing databases.
The end-of-life landscape for Amazon RDS Postgresql is characterized by a total of 10 versions, with 5 of them already reaching their end-of-life dates. Currently, 5 versions remain active and supported, giving developers a range of options for their database management needs. Notably, version 14 is set to expire on 2027-02-28, marking the next significant milestone in the service's lifecycle. This follows the expiration of version 13 on 2026-02-28, which has already reached its end-of-life date. Developers should be aware of these timelines to plan their upgrades and migrations accordingly, ensuring they stay on supported versions.
Given the current security landscape, Amazon RDS Postgresql has a clean track record with 0 tracked CVEs and 0 critical CVEs. As a result, there is no most affected version, and the service does not have a known exploited vulnerability status. This positive security posture is a testament to the service's robust design and regular maintenance. Nevertheless, developers should remain vigilant and monitor the service's security updates to ensure they are running the latest stable version, which is currently 18.4. By staying informed about end-of-life dates and security updates, developers can ensure the continued security and reliability of their PostgreSQL databases.
Last updated: Jul 24, 2026
| Version | Released | Active support | EOL date | Until EOL | Latest | CVEs | Status | Alert me |
|---|---|---|---|---|---|---|---|---|
| 18 | Nov 14, 2025 | — | Feb 28, 2031 | in 1680d | 18.4 | — | Active | |
| 17 | Nov 14, 2024 | — | Feb 28, 2030 | in 1315d | 17.10 | — | Active | |
| 16 | Nov 17, 2023 | — | Feb 28, 2029 | in 950d | 16.14 | — | Active | |
| 15 | Feb 27, 2023 | — | Feb 29, 2028 | in 585d | 15.18 | — | Active | |
| 14 | Feb 3, 2022 | — | Feb 28, 2027 | in 219d | 14.23 | — | Active | |
| 13 | Feb 24, 2021 | — | Feb 28, 2026 | 146d ago | 13.23 | — | EOL | |
| 12 | Mar 31, 2020 | — | Feb 28, 2025 | 511d ago | 12.22 | — | EOL | |
| 11 | Mar 13, 2019 | — | Feb 29, 2024 | 876d ago | 11.22 | — | EOL | |
| 10 | Feb 27, 2018 | — | Apr 30, 2023 | 1181d ago | 10.23 | — | EOL | |
| 9.6 | Nov 11, 2016 | — | Apr 30, 2022 | 1546d ago | 9.6.24 | — | EOL |
Data sourced from endoflife.date · CVE data from NVD
