Installing Elasticsearchedit

Hosted Elasticsearchedit

You can run Elasticsearch on your own hardware or use our hosted Elasticsearch Service that is available on AWS, GCP, and Azure. Try the Elasticsearch Service for free.

Installing Elasticsearch Yourselfedit

Elasticsearch is provided in the following package formats:

Linux and MacOS tar.gz archives

The tar.gz archives are available for installation on any Linux distribution and MacOS.

Install Elasticsearch from archive on Linux or MacOS

Windows .zip archive

The zip archive is suitable for installation on Windows.

Install Elasticsearch with .zip on Windows


The deb package is suitable for Debian, Ubuntu, and other Debian-based systems. Debian packages may be downloaded from the Elasticsearch website or from our Debian repository.

Install Elasticsearch with Debian Package


The rpm package is suitable for installation on Red Hat, Centos, SLES, OpenSuSE and other RPM-based systems. RPMs may be downloaded from the Elasticsearch website or from our RPM repository.

Install Elasticsearch with RPM


Images are available for running Elasticsearch as Docker containers. They may be downloaded from the Elastic Docker Registry.

Install Elasticsearch with Docker


Formulae are available from the Elastic Homebrew tap for installing Elasticsearch on macOS with the Homebrew package manager.

Install Elasticsearch on macOS with Homebrew

Java (JVM) Versionedit

Elasticsearch is built using Java, and includes a bundled version of OpenJDK from the JDK maintainers (GPLv2+CE) within each distribution. The bundled JVM is the recommended JVM.

To use your own version of Java, set the ES_JAVA_HOME environment variable. If you must use a version of Java that is different from the bundled JVM, it is best to use the latest release of a supported LTS version of Java. Elasticsearch is closely coupled to certain OpenJDK-specific features, so it may not work correctly with other JVMs. Elasticsearch will refuse to start if a known-bad version of Java is used.

If you use a JVM other than the bundled one, you are responsible for reacting to announcements related to its security issues and bug fixes, and must yourself determine whether each update is necessary or not. In contrast, the bundled JVM is treated as an integral part of Elasticsearch, which means that Elastic takes responsibility for keeping it up to date. Security issues and bugs within the bundled JVM are treated as if they were within Elasticsearch itself.

The bundled JVM is located within the jdk subdirectory of the Elasticsearch home directory. You may remove this directory if using your own JVM.