OpenSearch — support and end-of-life dates
OpenSearch 3 is the current release, released 2025-05-06, with no end-of-life date published upstream.
- 1 of its 3 tracked cycles have passed their EOL date (earliest tracked cycle 1)
Direct answer
OpenSearch 3 has no published end-of-life date. Data as of 2026-11-18.
All tracked cycles
| Cycle | Released | Active support ends | End of life (EOL) | Latest | Status |
|---|---|---|---|---|---|
| 3 | 2025-05-06 | — | not announced | 3.9.0 | No EOL date |
| 2 | 2022-05-26 | 2025-05-06 | not announced | 2.19.7 | No EOL date |
| 1 | 2021-07-12 | 2022-05-26 | 2025-05-06 561 days ago | 1.3.20 | End of life |
Upgrade path stated in the data
- No successor is stated in the upstream data for this product.
This is not a recommendation from DeprecateWatch. It repeats what the upstream source states, plus the newest cycle that is still inside its published support window.
Questions this page answers
Is OpenSearch 3 end of life?
No. OpenSearch 3 has no published end-of-life date in the source data.
How many OpenSearch versions are already end of life?
1 of the 3 cycles tracked here have passed their EOL date as of 2026-11-18.
Other Databases & datastores with upcoming deadlines
- Tarantool — next EOL 2026-11-29 (3.3)
- Redis — next EOL 2026-12-01 (8.0)
- MariaDB — next EOL 2026-12-31 (13.0)
- CockroachDB — next EOL 2027-02-19 (26.3)
- DuckDB — next EOL 2027-03-01 (1.5)
- ClickHouse — next EOL 2027-03-26 (26.3)
- Couchbase Server — next EOL 2027-03-31 (7.6)
- IBM Db2 — next EOL 2027-04-30 (11.5)
Source for the cycle table: endoflife.date/opensearch
read through the endoflife.date API on 2026-11-18. Machine-readable copy:
/api/eol.json (product key opensearch).