RPM install is not supported on distributions with old versions of RPM, such as SLES 11. Refer to Install from archive on Linux or macOS instead.
This package contains both free and subscription features. Start a 30-day trial to try out all of the features.
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.
4609 5ACC 8548 582C 1A26 99A9 D27D 666C D88E 42B4
Download and install the public signing key:
rpm --import https://artifacts.elastic.co/GPG-KEY-elasticsearch
Create a file called
kibana.repo in the
for RedHat based distributions, or in the
/etc/zypp/repos.d/ directory for
OpenSuSE based distributions, containing:
[kibana-8.x] name=Kibana repository for 8.x packages baseurl=https://artifacts.elastic.co/packages/8.x/yum gpgcheck=1 gpgkey=https://artifacts.elastic.co/GPG-KEY-elasticsearch enabled=1 autorefresh=1 type=rpm-md
And your repository is ready for use. You can now install Kibana with one of the following commands:
The RPM for Kibana v8.12.2 can be downloaded from the website and installed as follows:
When you start Elasticsearch for the first time, the following security configuration occurs automatically:
Authentication and authorization are enabled, and a password is generated for the
- Certificates and keys for TLS are generated for the transport and HTTP layer, and TLS is enabled and configured with these keys and certificates.
The password and certificate and keys are output to your terminal.
You can then generate an enrollment token for Kibana with the
bin/elasticsearch-create-enrollment-token -s kibana
Start Kibana and enter the enrollment token to securely connect Kibana with Elasticsearch.
To configure Kibana to start automatically when the system starts, run the following commands:
sudo /bin/systemctl daemon-reload sudo /bin/systemctl enable kibana.service
Kibana can be started and stopped as follows:
sudo systemctl start kibana.service sudo systemctl stop kibana.service
These commands provide no feedback as to whether Kibana was started
successfully or not. Log information can be accessed via
journalctl -u kibana.service.
Kibana loads its configuration from the
file by default. The format of this config file is explained in
The RPM places config files, logs, and the data directory in the appropriate locations for an RPM-based system:
Kibana home directory or
Binary scripts including
Configuration files including
The location of the data files written to disk by Kibana and its plugins
Logs files location
Plugin files location. Each plugin will be contained in a subdirectory.