// Elasticsearch 7.x extended support
Still running Elasticsearch 7?
The upgrade is a reindex, and the licence changed after 7.10.2.
Elasticsearch 7.10.2 is the last release available under Apache 2.0, and 7.17, the last 7.x line, reached end of life in January 2026. Moving to 8.x means reindexing old indices, updating clients and turning on security; moving to OpenSearch means a fork migration. OSSeva patches the 7.x clusters you run while you choose.
Trusted globally by enterprises
Why Elasticsearch 7 clusters are stuck
Search clusters outlive their upgrade plans because every path forward touches data, clients or licence.
8.x cannot read 6.x indices
Indices created in Elasticsearch 6.x or earlier must be reindexed before a cluster can run 8.x. For large clusters that is days of I/O and a temporary doubling of storage.
Clients and security change together
8.x removes mapping types and the API endpoints that used them, and enables security by default. Every application that talks to the cluster needs changes and testing.
7.10.2 is a licence decision
From 7.11, Elasticsearch moved to SSPL and the Elastic License, and 7.x never received the later AGPL option. Products that embed Elasticsearch, and teams with licence policies, stayed on 7.10.2 or moved to OpenSearch, and Elastic patches neither 7.x line now.
The dates that matter
2021-01-14
Elasticsearch 7.10.2 released, the last version available under Apache 2.0.
2025-06-24
Elasticsearch 7.17.29, the last 7.x release.
2026-01-15
Elasticsearch 7.17 end of life.
2026-11-07
Amazon OpenSearch Service raises Extended Support on Elasticsearch 1.5 to 7.8 to a surcharge equal to the instance price.
2030-11-07
End of Amazon OpenSearch Service Extended Support for Elasticsearch 7.10.
What OSSeva delivers
Patched Elasticsearch 7.x
Backported security fixes for 7.10.2 and 7.17, including the bundled JDK and libraries, as packages and images.
Migration planning
Index inventory, reindex sizing, client audit, and a decision between 8.x and OpenSearch per cluster.
Executed migrations
Reindex or remote-reindex runs, dual-write cutovers and rollback plans, carried out by engineers who run search clusters.
Your options, compared
| Option | What you get | Trade-off |
|---|---|---|
| Upgrade to Elasticsearch 8.x | Supported Elastic releases | Reindexing, client changes and Elastic's current licence terms. |
| Migrate to OpenSearch | An Apache-2.0 fork of 7.10.2 | A migration of clusters, clients and tooling. |
| Amazon OpenSearch Service Extended Support | Patched Elasticsearch 7.10 inside AWS until November 2030 | A per-normalized-instance-hour charge, and double the instance price for versions 1.5 to 7.8 from November 2026. |
| OSSeva extended support | Patched self-managed 7.10.2 and 7.17 | A subscription while you migrate. |
Licence history and dates from Elastic's release tags and end-of-life page; CVE details from NVD; AWS dates from the Amazon OpenSearch Service announcement of 7 August 2026.
Frequently asked questions
Is Elasticsearch 7.10.2 the last open source version?
It is the last release available under Apache 2.0, through its OSS distribution. From 7.11 Elasticsearch used SSPL and the Elastic License; Elastic added an AGPL option from 8.16. OpenSearch was forked from 7.10.2 to keep Apache 2.0.
Are there Elasticsearch 7.17 vulnerabilities without a fix?
Yes. CVE-2025-37731 and CVE-2025-68384 affect every 7.x release through 7.17.29 and were fixed only in 8.19 and 9.x. Elastic ships no further 7.x releases.
Can I upgrade Elasticsearch 7 to 8 without reindexing?
Only if every index was created in 7.x. Indices from 6.x or earlier must be reindexed first.
Who provides security patches for Elasticsearch 7.10.2?
Elastic does not patch 7.10.2. AWS patches it inside OpenSearch Service under paid Extended Support. For self-managed clusters, OSSeva provides patched builds.
Keep 7.x patched while you decide where it goes.
Discovery call, cluster and index inventory, proposal within five working days.