Amazon Elasticsearch End of Life (EOL) Dates and End of Support (EOS) Dates
Amazon Elasticsearch end of life (EOL) and end of support (EOS) dates: 16 Amazon Elasticsearch versions have reached EOL, including Amazon Elasticsearch 7.8 (EOL date: Nov 07, 2025) — no longer receiving security updates or patches. Amazon Elasticsearch 7.10 is the current supported release, with support through Nov 07, 2027 — 3 versions in active support. Also see Amazon Corretto end of life dates for related end-of-life information.
Currently Supported Amazon Elasticsearch Releases - Active EOS/EOSL Support (3)
| Release | Released | Standard Support | Extended Support |
|---|---|---|---|
| 7.10 | (5 years and 7 months ago) | (in 11 months) | (in 3 years and 11 months) |
| 7.9 | (5 years and 11 months ago) | (in 11 months) | (in 1 year and 11 months) |
| 6.8 | (7 years and 3 months ago) | (in 11 months) | (in 3 years and 11 months) |
Amazon Elasticsearch End of Life (EOL) Releases - No Longer Supported (16)
| Release | Released | Standard Support | Extended Support |
|---|---|---|---|
| 7.8 | (6 years ago) | (1 year ago) | (in 11 months) |
| 7.7 | (6 years and 3 months ago) | (1 year ago) | (in 11 months) |
| 7.4 | (6 years and 8 months ago) | (1 year ago) | (in 11 months) |
| 7.1 | (7 years and 3 months ago) | (1 year ago) | (in 11 months) |
| 6.7 | (7 years and 5 months ago) | (1 year ago) | (in 11 months) |
| 6.5 | (7 years and 7 months ago) | (1 year ago) | (in 11 months) |
| 6.4 | (7 years and 9 months ago) | (1 year ago) | (in 11 months) |
| 5.6 | (8 years and 3 months ago) | (1 year ago) | (in 1 year and 11 months) |
| 6.3 | (8 years and 3 months ago) | (1 year ago) | (in 11 months) |
| 6.2 | (8 years and 8 months ago) | (1 year ago) | (in 11 months) |
| 6.0 | (8 years and 11 months ago) | (1 year ago) | (in 11 months) |
| 5.5 | (9 years and 2 months ago) | (1 year ago) | (in 11 months) |
| 5.3 | (9 years and 5 months ago) | (1 year ago) | (in 11 months) |
| 5.1 | (9 years and 9 months ago) | (1 year ago) | (in 11 months) |
| 2.3 | (10 years and 3 months ago) | (1 year ago) | (in 11 months) |
| 1.5 | (11 years and 1 month ago) | (1 year ago) | (in 11 months) |
Amazon Elasticsearch end of life already has a calendar: the original Extended Support window for most legacy Elasticsearch versions on Amazon OpenSearch Service closes on November 7, 2026, and Amazon has stretched coverage a further twelve months at a higher rate. Customers who keep that software past the dates lose critical security fixes and operating system patches, which puts compliance at risk. This page lists every date and what staying put costs you.
Amazon Elasticsearch End of Life Dates for Each Elasticsearch Version
Amazon renamed its managed search engine service OpenSearch Service after Elasticsearch 7.10, so every Elasticsearch release still offered there is a legacy line with a fixed calendar. Amazon Web Services announced the schedule in November 2024 and later added a year of coverage for most supported versions. The table shows the end of Standard Support and both Extended Support end dates.
| Elasticsearch version | End of Standard Support | Extended Support ends (original) | Extended Support ends (updated) |
|---|---|---|---|
| 1.5 to 2.3, 5.1 to 5.5, 6.0 to 6.7, 7.1 to 7.8 | November 7, 2025 | November 7, 2026 | November 7, 2027 |
| 5.6 | November 7, 2025 | November 7, 2028 | No change |
| 6.8 and 7.10 | November 7, 2027 | Not applicable | November 7, 2030 |
| 7.9 | November 7, 2027 | Not applicable | November 7, 2028 |
Elasticsearch 5.6 keeps the longest original window. Elasticsearch versions in the first row move together, and the Elasticsearch versions in the last three rows each get a later horizon. Meanwhile the end of Extended Support for the last release in each family, 6.8 and 7.10, lands furthest out. Check your engine version first; the rest of your plan depends on which row you sit in.
End of Standard Support and Extended Support for OpenSearch Versions
OpenSearch versions follow the upstream open source project. Amazon provides at least 12 months of Standard Support after the upstream end date, or 12 months after the next minor version arrives on the service, whichever is longer. Customers on older OpenSearch versions get the same Standard Support rules, and domains on those OpenSearch versions then get at least 12 months of Extended Support, matching the open source maintenance policy. The support dates for OpenSearch 1.0 to 1.2 and 2.3 to 2.9 mirror the legacy row above, while 1.3 and 2.19 get the same three-year treatment as 6.8 and 7.10. Newer lines from 3.1 up have no announced end yet, and each version lifecycle is published on the supported versions page. Staying current also keeps legacy software off your plate and brings new features, resiliency and better price-performance.
What Security Fixes and Bug Fixes Still Cover
A version in Standard Support receives regular bug fixes and critical security patches. Extended Support narrows that to security patches and operating system updates, because several legacy lines lean on third-party dependencies their own maintainers no longer support. Once Extended Support ends, that setup is unsupported: new vulnerabilities go unfixed, and your only way to patch is to upgrade.
Extended Support Charges on Amazon OpenSearch Service
Extended Support is billed as a flat additional fee on top of normal instance usage; storage costs are untouched. The standard rate is $0.0065 per normalized instance hour in the US East (N. Virginia) AWS Region, and the pricing page lists every other region. Domains running versions already in Extended Support face a steeper surcharge: through the extension period that ends November 7, 2027, it equals your instance price, which doubles what you pay for compute. Elasticsearch 5.6 and the newer lines keep the standard flat fee.
Normalized Instance Hour Pricing
NIH is the hours an instance runs multiplied by its size normalization factor: nano is 0.25, small 1, medium 2, large 4, xlarge 8, and the normalization factor keeps doubling up to 256 for 32xlarge. Types such as m7g.medium.search or r7g.large.search follow the same rule, so a bigger instance size means a bigger fee.
$$S = 0.0065 \times F \times H$$
Here S is the monthly added fee per instance, F the factor and H the hours.
A Six-Node Extended Support Cost Example
Take a six-node cluster of r7g.large.search data nodes at an assumed on-demand $0.150 an hour each, running 730 hours a month.
| Component | Newer line, standard rate | Legacy line after the doubling |
|---|---|---|
| Monthly instance cost (6 × 730 × $0.150) | $657.00 | $657.00 |
| Added fee | $113.88 | $657.00 |
| Monthly total | $770.88 | $1,314.00 |
The standard added fee is $0.0065 × 4 × 730 × 6 = $113.88. Across 12 months the doubled surcharge adds $7,884.00, against $1,366.56 at the standard rate.
Upgrade Elasticsearch Versions Before End of Support
Moving off a legacy version is the only way to stop paying the added fee and keep receiving fixes. Amazon recommends the latest available OpenSearch version, and recent OpenSearch versions bring the newest software fixes, and minor version upgrades are typically non-disruptive. Follow the guide on upgrading OpenSearch Service domains, and if a cluster runs an older 6.x or 7.x release, step to 6.8 or 7.10 first. The Migration Assistant helps move log analytics and search workloads across families. OpenSearch keeps the full-text search model over distributed JSON documents, so most queries carry over, but test them. If your path is unclear, read the documentation or contact AWS Support.
Migration Paths and New Domain Creation
When a version reaches its cutoff on Amazon OpenSearch Service, staying inside one family is the easy path; crossing families means checking for breaking changes in settings and plugins. New domain creation is blocked once Extended Support ends for a version, so snapshot your data before then. Also test client libraries: some Elastic-distributed clients refuse servers they do not recognize, a side effect of the license change after 7.10.
Elastic Maintenance Term and Support Term for Elasticsearch
Elastic's calendar is separate from the Amazon dates above. Elastic, the company behind the software, runs its own calendar under its support policy, and it applies to the whole Elastic Stack: Kibana, Logstash, Beats, APM Server, Elastic APM agents and Elastic Cloud on Kubernetes. Each major release is maintained for the longer of 30 months from general availability or 18 months after the next major arrives. The Support Term adds six months on top. Version 8.x maintenance ends 15 January 2027 and support ends 15 July 2027, while 9.x is maintained until at least 15 October 2027. A retirement notice for any product guarantees 12 months of support. Tracking sites such as endoflife.date, last updated October 2026, apply semantic versioning to these releases and mirror the same dates.
Major Release Rules
Elastic maintains the two newest minor releases of the current major release, plus the final minor release of the previous major release while that series is in its term. A maintenance release is the third number: in 8.3.2 the major is 8, the minor 3 and the maintenance 2. Elastic's term governs self-managed software and clusters; on Amazon the dates above apply.
Plan Your Move Off Legacy Versions Before the Lifecycle Ends
Check your Elasticsearch version against the table above, then upgrade before November 7, 2026 so the extra fee on Amazon OpenSearch Service does not double your compute bill. The cheapest path is to move early, test queries on a copy, and cut over while support still covers you.