﻿---
title: Available stack versions
description: This section describes our version policy for Elastic Cloud Hosted, including: What Elastic Stack versions are available, When we make new Elastic Stack...
url: https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/5412/deploy-manage/deploy/elastic-cloud/available-stack-versions
products:
  - Elastic Cloud Hosted
applies_to:
  - Elastic Cloud Hosted: Generally available
---

# Available stack versions
This section describes our version policy for Elastic Cloud Hosted, including:
- [What Elastic Stack versions are available](#ec-version-policy-available)
- [When we make new Elastic Stack versions available](#ec-version-policy-new)
- [When we might force an upgrade or restart to keep your cluster safe](#ec-version-policy-critical)
- [What release candidates and cutting edge builds we make available](#ec-release-builds)
- [What happens when a version reaches its end-of-life (EOL)](#ec-version-policy-eol)


## Available Elastic Stack versions

Elastic Stack uses a version numbering scheme based on three numbers separated by dots. The leftmost number indicates the major release, the middle number indicates the minor release, and the rightmost number indicates the maintenance release. For example, `8.3.2` represents major release 8, minor release 3, and maintenance release 2.
By default, the following versions are available in the [Elastic Cloud Console](https://cloud.elastic.co?page=docs&placement=docs-body):
- The two latest minor versions of the latest major version
- The latest minor version of the previous major version

For example, if the latest Elastic Stack version is 9.2.3, Elastic Cloud Hosted makes the following versions available:
- 9.1 and 9.2
- 8.19

Additional versions can appear in the UI, such as [release candidate builds](#ec-release-builds) or older versions that are not [end-of-life (EOL)](#ec-version-policy-eol) and that you already have a running deployment on. This allows you, for example, to [clone an existing deployment](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/5412/deploy-manage/tools/snapshot-and-restore/ece-restore-snapshots-into-new-deployment) that uses one of those versions.
Separately from the UI, the Elastic Cloud Hosted API allows you to [deploy any Elastic Stack version as long as it is not EOL](https://docs-v3-preview.elastic.dev/elastic/cloud/tree/master/reference/cloud-hosted/ec-api-deployment-crud#ec_using_the_api_to_create_deployment_with_non_eol_versions), even if that version is not listed in the UI.

## New Elastic Stack versions

Whenever a new Elastic Stack version is released, we do our best to provide the new version on our hosted service at the same time. We send you an email and add a notice to the console, recommending an upgrade. You’ll need to decide whether to upgrade to the new version with new features and bug fixes or to stay with a version you know works for you a while longer.
There can be [breaking changes](https://docs-v3-preview.elastic.dev/elastic/elasticsearch/tree/main/release-notes/breaking-changes) in some new versions of Elasticsearch that break what used to work in older versions. Before upgrading, you’ll want to check if the new version introduces any changes that might affect your applications. A breaking change might be a function that was previously deprecated and that has been removed in the latest version, for example. If you have an application that depends on the removed function, the application will need to be updated to continue working with the new version of Elasticsearch.
To learn more about upgrading to newer versions of the Elastic Stack on our hosted service, check [Upgrade Versions](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/5412/deploy-manage/upgrade/deployment-or-cluster).

## Upgrades or restart for critical issues

We reserve the right to force upgrade or restart a cluster immediately and without notice in advance if there is a critical security or stability issue. Such upgrades happen only within minor versions.
A forced upgrade or restart might become necessary in a situation that:
- Bypasses Shield, where knowing only the cluster endpoint is sufficient to gain access to data.
- Disrupts our ability to effectively manage a cluster in disaster scenarios
- Impairs stability to the point where we cannot guarantee cluster node or data integrity
- Impairs or risks impairing our infrastructure


## Release candidates and cutting-edge releases

Interested in kicking the tires of Elasticsearch releases at the cutting edge? We sometimes make release candidate builds and other cutting-edge releases available in Elastic Cloud for you to try out.
<warning>
  Remember that cutting-edge releases are used to test new function fully. These releases might still have issues and might be less stable than the GA version. There’s also no guaranteed upgrade path to the GA version when it becomes available.
</warning>

If you’re interested in trying out one of these cutting-edge releases, we don’t recommended upgrading an existing deployment directly. Instead, use a copy of your existing data with a test deployment, first.
Cutting-edge releases do not remain available forever. Once the GA version of Elasticsearch is released, your deployment needs to be removed after a grace period. We cannot guarantee that you will be able to upgrade to the GA version when it becomes available.

## Version Policy and Product End of Life

For Elastic Cloud, we follow the [Elastic Version Maintenance and Support Policy](https://www.elastic.co/support/eol), which defines the support and maintenance policy of the Elastic Stack.