Installing the Elastic Stackedit

When installing the Elastic Stack, you must use the same version across the entire stack. For example, if you are using Elasticsearch 8.13.2, you install Beats 8.13.2, APM Server 8.13.2, Elasticsearch Hadoop 8.13.2, Kibana 8.13.2, and Logstash 8.13.2.

If you’re upgrading an existing installation, see Upgrading the Elastic Stack for information about how to ensure compatibility with 8.13.2.

For an example of installing and configuring the Elastic Stack, you can try out our Tutorial 1: Installing a self-managed Elastic Stack. After that, you can also learn how to secure your installation for production following the steps in Tutorial 2: Securing a self-managed Elastic Stack.

Network requirementsedit

To install the Elastic Stack on-premises, the following ports need to be open for each component.

Each Elastic integration has its own ports and dependencies. Verify these ports and dependencies before installation. Refer to Integrations.

For more information on supported network configurations, refer to Elasticsearch Ingest Architectures.

Installation orderedit

Install the Elastic Stack products you want to use in the following order:

Installing in this order ensures that the components each product depends on are in place.

Installing on Elastic Cloudedit

Our hosted Elasticsearch Service is available on AWS, GCP, and Azure, and you can try it for free.

Installing on Elastic Cloud is easy: a single click creates an Elasticsearch cluster configured to the size you want, with or without high availability. The subscription features are always installed, so you automatically have the ability to secure and monitor your cluster. Kibana is enabled automatically, and a number of popular plugins are readily available.

Some Elastic Cloud features can be used only with a specific subscription. For more information, see https://www.elastic.co/pricing/.