Loading

Upgrade your deployment or cluster

Stack ECE ECK ECH Self-Managed

This section contains the upgrade instructions for Elasticsearch clusters and Kibana instances. Upgrade procedures depend on whether you installed Elastic components using Elastic-managed or self-managed infrastructure.

Before proceeding with the upgrade, review the Plan your upgrade guidance to understand compatibility and timing considerations, and follow the steps in Prepare to upgrade to get your environment ready for the upgrade.

Elastic maintains several minor versions of Elasticsearch at the same time. This means releases do not always happen in order of their version numbers. You can only upgrade to 9.1.1 if the version you are currently running meets both of these conditions:

  • Has a lower version number than 9.1.1
  • Has an earlier release date than 9.1.1

If you are currently running a version with a lower version number but a later release date than 9.1.1, wait for a newer release before upgrading.

Additionally, upgrading from a release candidate build, such as 9.0.0-rc1, is unsupported. Use pre-releases only for testing in a temporary environment.

If you’re using Elastic-managed infrastructure, use the following options:

If you’re using self-managed infrastructure - either on-prem or public cloud - use the following options:

Note

With Elastic Cloud Serverless, upgrades of the Elastic-managed infrastructure and project components are fully handled by Elastic. Users automatically receive the latest features and improvements, with no need to plan or perform project-level upgrades.

Keep in mind that the ingest components or clients you manage externally, such as Elastic Agent, Beats, Logstash, or custom applications, still need to be updated manually.

Once you've successfully upgraded your deployment, you can upgrade your ingest components, such as Logstash, Elastic Agent, or Beats.