Installing Elasticsearch
editInstalling Elasticsearch
editHosted Elasticsearch Service
editElastic Cloud offers all of the features of Elasticsearch, Kibana, and Elastic’s Observability, Enterprise Search, and Elastic Security solutions as a hosted service available on AWS, GCP, and Azure.
To set up Elasticsearch in Elastic Cloud, sign up for a free Elastic Cloud trial.
Self-managed Elasticsearch options
editIf you want to install and manage Elasticsearch yourself, you can:
- Run Elasticsearch using a Linux, MacOS, or Windows install package.
- Run Elasticsearch in a Docker container.
- Set up and manage Elasticsearch, Kibana, Elastic Agent, and the rest of the Elastic Stack on Kubernetes with Elastic Cloud on Kubernetes.
To try out Elasticsearch on your own machine, we recommend using Docker and running both Elasticsearch and Kibana. For more information, see Run Elasticsearch locally. Please note that this setup is not suitable for production use.
Elasticsearch install packages
editElasticsearch is provided in the following package formats:
|
Linux and MacOS |
The |
|
Windows |
The |
|
|
The |
|
|
The |
For a step-by-step example of setting up the Elastic Stack on your own premises, try out our tutorial: Installing a self-managed Elastic Stack.
Elasticsearch container images
editYou can also run Elasticsearch inside a container image.
|
|
Docker container images may be downloaded from the Elastic Docker Registry. |
Java (JVM) Version
editElasticsearch 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.
JVM and Java agents
editDon’t use third-party Java agents that attach to the JVM. These agents can reduce Elasticsearch performance, including freezing or crashing nodes.