Skip to content
Database

Elasticsearch Releases

Track every Elasticsearch release from latest stable to end-of-life. Version timelines, licensing changes, OpenSearch context, and upgrade guidance.

Total Versions

Supported

Latest

Version Timeline

All tracked releases with lifecycle status and EOL dates.

Loading version data…

Lifecycle Timeline

Visual overview of active support and maintenance windows.

7.x
8.x
2022 2023 2024 2025 2026 2027 2028 2029
Active
Maint
Active
Maint
Active / LTS
Maintenance
Today

Upgrade Paths

Migration guidance between major versions — breaking changes, effort estimates, and tips.

7.x 8.x High Difficulty
Est. 1-2 days for production clusters

Breaking Changes

  • Security enabled by default (TLS, authentication)
  • Java 17+ required (drops Java 8, 11)
  • REST API changes (several endpoints removed/changed)
  • Index lifecycle management changes
  • Kibana 8 requires Elasticsearch 8
  • Some mapping types and query parameters removed
  • License options changed (SSPL/Elastic/AGPL)

Migration Notes

The security-by-default change is the biggest operational shift. Use the Elasticsearch Upgrade Assistant in Kibana to identify breaking changes. Run the deprecation API (GET /_migration/deprecations) before upgrading. Plan for TLS configuration if your 7.x cluster ran without security.

Version Risk Assessment

Evaluate risk factors before choosing a version for production.

Version EOL Risk CVE Risk Ecosystem Cloud Support Overall Recommended Action
Elasticsearch 6.x and below Critical High EOL Dropped Critical Way past EOL — must migrate (cannot skip to 8.x directly)
Elasticsearch 7.x High Medium Maintenance Legacy High Approaching EOL — plan 8.x migration
Elasticsearch 8.x None Low Active Full Low Current — keep on latest 8.x minor

Risk combines EOL status, security defaults, and license clarity. Assessed as of March 2026.

Elasticsearch 7.x vs 8.x

Side-by-side feature differences across major versions.

Feature 7.x (late) 8.x
Security by default Optional Enabled
Java minimum 8 / 11 17
License Apache→SSPL SSPL/Elastic/AGPL
Vector search (kNN) Experimental Stable
NLP/ML inference Basic Enhanced
ESQL query language No Stable
Serverless offering No Available
Data stream lifecycle ILM ILM + Data lifecycle
Profiling No Universal Profiling
OpenSearch compatible 7.10 fork No

Embed Badges

Add live Elasticsearch status badges to your README, docs, or dashboard.

Health Status

Overall support health

Elasticsearch Health Status
![Elasticsearch Health Status](https://img.releaserun.com/badge/health/elasticsearch.svg)

EOL Countdown

Next end-of-life date

Elasticsearch EOL Countdown
![Elasticsearch EOL Countdown](https://img.releaserun.com/badge/eol/elasticsearch.svg)

Latest Version

Current stable release

Elasticsearch Latest Version
![Elasticsearch Latest Version](https://img.releaserun.com/badge/v/elasticsearch.svg)

CVE Status

Known vulnerabilities

Elasticsearch CVE Status
![Elasticsearch CVE Status](https://img.releaserun.com/badge/cve/elasticsearch.svg)

Frequently Asked Questions

Common questions about Elasticsearch releases and lifecycle.

What happened with Elasticsearch licensing?
Elasticsearch was Apache 2.0 until version 7.10 (Jan 2021), when Elastic switched to SSPL + Elastic License. AWS forked it as OpenSearch. In Aug 2024, Elastic added AGPL as a third license option, making Elasticsearch open source again. Versions 7.11+ through 8.x are SSPL/Elastic/AGPL triple-licensed.
Elasticsearch vs OpenSearch: which should I choose?
Elasticsearch has faster feature development, better ML/AI integration, and the original team. OpenSearch is fully Apache 2.0, has stronger AWS integration, and is community-governed. If you are on AWS, OpenSearch is easier. If you want the latest features and are self-hosted or on Elastic Cloud, choose Elasticsearch.
How long are Elasticsearch versions supported?
Elastic provides maintenance for the current major and previous major version. Each major version gets roughly 18-24 months of active maintenance plus extended support. Elasticsearch 7.x maintenance ended after 8.x was well-established.
How hard is upgrading Elasticsearch?
Within a major version (8.1→8.15), upgrades are rolling and zero-downtime. Cross-major upgrades (7.x→8.x) require more planning: deprecation API checks, index compatibility verification, and potentially reindexing. You cannot skip major versions (no 6.x→8.x).
Should I use Elasticsearch or PostgreSQL full-text search?
PostgreSQL full-text search handles moderate search workloads well without additional infrastructure. Elasticsearch is necessary for: large-scale search (millions of documents), complex relevance scoring, aggregations/analytics, geo-spatial queries at scale, or when you need near-real-time indexing of high-volume data.

Related Tools

Browse All Version History