Complete end-of-life dates, support windows, and security status for all Amazon Opensearch versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1.0 | — | Sep 8, 2021 | Nov 7, 2025 | 183 days past EOL | EOL |
| 1.1 | — | Jan 4, 2022 | Nov 7, 2025 | 183 days past EOL | EOL |
| 1.2 | — | Apr 4, 2022 | Nov 7, 2025 | 183 days past EOL | EOL |
| 1.3 | — | Aug 16, 2022 | Already EOL | Supported | Active |
| 2.3 | — | Nov 15, 2022 | Nov 7, 2025 | 183 days past EOL | EOL |
| 2.5 | — | Mar 13, 2023 | Nov 7, 2025 | 183 days past EOL | EOL |
| 2.7 | — | Jul 10, 2023 | Nov 7, 2025 | 183 days past EOL | EOL |
| 2.9 | — | Oct 2, 2023 | Nov 7, 2025 | 183 days past EOL | EOL |
| 2.11 | — | Nov 17, 2023 | Already EOL | Supported | Active |
| 2.13 | — | May 21, 2024 | Already EOL | Supported | Active |
| 2.15 | — | Oct 11, 2024 | Already EOL | Supported | Active |
| 2.17 | — | Nov 13, 2024 | Already EOL | Supported | Active |
| 2.19 | — | Apr 30, 2025 | Already EOL | Supported | Active |
| 3.1 | — | Sep 9, 2025 | Already EOL | Supported | Active |
| 3.3 | — | Nov 24, 2025 | Already EOL | Supported | Active |
| 3.5 | — | Mar 18, 2026 | Already EOL | Supported | Active |
When a Amazon Opensearch version reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Amazon Opensearch should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →