Updated on 2026-08-21 GMT+08:00

Version Lifecycles

On the CSS console, a cluster version is displayed in the format of Cluster version(Image version), where:
  • Cluster version indicates the cluster's major version, for example, 7.10.2.
  • Image version indicates the cluster's image version in the format of Cluster version_Requirement version_Date identifier. For example, 7.10.2_24.3.0_0926 indicates version 24.3.0_0926 based on 7.10.2.
The lifecycle of a CSS cluster version includes the following milestones:
  • End of Marketing (EOM): New deployments are no longer available.
  • End of Full Support (EOFS): Regular bug fixes are no longer provided. Only critical issue fixes and security updates are provided.
  • End of Service (EOS): All support is discontinued. Users must upgrade to a later version.

Elasticsearch Version Lifecycle

Table 1 provides the lifecycle of CSS Elasticsearch cluster versions, helping you plan your version upgrade schedule.

Table 1 Elasticsearch version lifecycle

Version

Status

Released

EOM

EOFS

EOS

5.5.1_x.x.x_x

EOS

2017.09.30

2021.09.30

2022.09.30

2023.03.30

6.2.3_x.x.x_x

EOS

2018.06.30

2022.06.30

2023.06.30

2023.12.30

6.5.4_x.x.x_x

EOS

2019.03.30

2023.03.30

2024.03.30

2024.09.30

6.8.23_x.x.x_x

Intermediate versions for feature upgrade are not sold externally and have no lifecycle timeline.

7.1.1_x.x.x_x

EOS

2019.09.30

2023.09.30

2024.09.30

2025.03.30

7.6.2_x.x.x_x

EOS

2020.06.30

2024.06.30

2025.06.30

2025.12.30

7.9.3_x.x.x_x

EOS

2020.12.30

2024.12.30

2025.12.30

2026.06.30

7.10.2_x.x.x_x

Commercial use

2022.03.30

Not planned

Not planned

Not planned

The Lifecycle of OpenSearch Cluster Versions

Table 2 provides the lifecycle of CSS OpenSearch cluster versions, helping you plan your version upgrade schedule.

Table 2 OpenSearch version lifecycle

Version

Status

Released

EOM

EOFS

EOS

1.3.6_x.x.x_x

Restricted use

2023.06.30

2027.06.30

2028.06.30

2028.12.30

2.11.0_x.x.x_x

Restricted use

2023.12.30

2027.12.30

2028.12.30

2029.06.30

2.17.1_x.x.x_x

Restricted use

2024.11.30

2028.11.30

2029.11.30

2030.05.30

2.19.0_x.x.x_x

Commercial use

2025.08.15

2029.08.15

2030.08.15

2031.02.15

3.4.0_x.x.x_x

Commercial use

2026.04.15

Not planned

Not planned

Not planned

Logstash Version Lifecycle

Table 3 provides the lifecycle of CSS Logstash cluster versions, helping you plan your version upgrade schedule.

Table 3 Logstash version lifecycle

Version

Status

Released

EOM

EOFS

EOS

5.6.16_x.x.x_x

EOS

2020.12.30

2024.12.30

2025.12.30

2026.06.30

7.10.0_x.x.x_x

Commercial use

2020.12.30

Not planned

Not planned

Not planned

Recommended Action Upon Version EOX

When a cluster version reaches an EOX state (EOM, EOFS, or EOS), you have the following options:

  • Version upgrade: If your Elasticsearch and OpenSearch clusters can be upgraded, upgrade them. For details, see Upgrading the Version of an Elasticsearch Cluster or Upgrading the Version of an OpenSearch Cluster.
  • Cluster migration: If your Elasticsearch or OpenSearch clusters cannot be upgraded, migrate them to achieve cross-version upgrade. For details, see Elasticsearch Data Migration. The Logstash engine does not support direct upgrades. You are advised to first save the Logstash configuration files (.conf) as custom templates in the original cluster. After creating a cluster, select the saved .conf templates from the custom templates in the new cluster to perform cluster restoration and achieve cluster migration.