Loading

Install Kibana with RPM

Self Managed

The RPM for Kibana can be downloaded from our website or from our RPM repository. It can be used to install Kibana on any RPM-based system such as OpenSuSE, SLES, Red Hat, and Oracle Enterprise.

Note

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.

The latest stable version of Kibana can be found on the Download Kibana page. Other versions can be found on the Past Releases page.

We sign all of our packages with the Elasticsearch signing key (PGP key D88E42B4, available from https://pgp.mit.edu) with fingerprint:

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

You have the following options for installing the Elasticsearch RPM package:

Create a file called kibana.repo in the /etc/yum.repos.d/ directory for RedHat based distributions, or in the /etc/zypp/repos.d/ directory for OpenSuSE based distributions, containing:

[kibana-9.X]
name=Kibana repository for 9.x packages
baseurl=https://artifacts.elastic.co/packages/9.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:

sudo yum install kibana 1
sudo dnf install kibana 2
sudo zypper install kibana 3
  1. Use yum on older Red Hat based distributions.
  2. Use dnf on Fedora and other newer Red Hat distributions.
  3. Use zypper on OpenSUSE based distributions

The RPM for Kibana 9.0.0 can be downloaded from the website and installed as follows:

wget https://artifacts.elastic.co/downloads/kibana/kibana-9.0.0-x86_64.rpm
wget https://artifacts.elastic.co/downloads/kibana/kibana-9.0.0-x86_64.rpm.sha512
shasum -a 512 -c kibana-9.0.0-x86_64.rpm.sha512 1
sudo rpm --install kibana-9.0.0-x86_64.rpm
  1. Compares the SHA of the downloaded RPM and the published checksum, which should output kibana-<version>-x86_64.rpm: OK.

Start Elasticsearch.

When you start Elasticsearch for the first time, the following security configuration occurs automatically:

  • Certificates and keys for TLS are generated for the transport and HTTP layers.
  • The TLS configuration settings are written to elasticsearch.yml.
  • A password is generated for the elastic user.
  • An enrollment token is generated for Kibana, which is valid for 30 minutes.

You can then start Kibana and enter the enrollment token. This token automatically applies the security settings from your Elasticsearch cluster, authenticates to Elasticsearch with the built-in kibana service account, and writes the security configuration to kibana.yml.

Note

There are some cases where security can’t be configured automatically because the node startup process detects that the node is already part of a cluster, or that security is already configured or explicitly disabled.

If your enrollment token has expired, then you can generate a new enrollment token for Kibana with the elasticsearch-create-enrollment-token tool:

bin/elasticsearch-create-enrollment-token -s kibana

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 using journalctl -u kibana.service.

  1. Run the status command to get details about the {{{kib}}} service.

    sudo systemctl status kibana
    

    In the status command output, a URL is shown with:

    • A host address to access Kibana
    • A six digit verification code

    For example:

    Kibana has not been configured.
    Go to http://<host>:5601/?code=<code> to get started.
    

    Make a note of the verification code.

  2. Go to the host address.

    It can take a minute or two for Kibana to start up, so refresh the page if you don’t see a prompt right away.

  3. When Kibana starts, you’re prompted to provide an enrollment token. Paste in the Kibana enrollment token that you generated earlier.

  4. Click Configure Elastic.

  5. If you’re prompted to provide a verification code, copy and paste in the six digit code that was returned by the status command. Then, wait for the setup to complete.

  6. When you see the Welcome to Elastic page, provide the elastic as the username and provide the password that you copied from the install command output when you set up your first Elasticsearch node.

  7. Click Log in.

Kibana loads its configuration from the /etc/kibana/kibana.yml 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:

Type Description Default Location Setting
home Kibana home directory or $KIBANA_HOME /usr/share/kibana
bin Binary scripts including kibana to start the Kibana server and kibana-plugin to install plugins /usr/share/kibana/bin
config Configuration files including kibana.yml /etc/kibana [KBN_PATH_CONF](configure.md)
data The location of the data files written to disk by Kibana and its plugins /var/lib/kibana path.data
logs Logs files location /var/log/kibana [Logging configuration](../../monitor/logging-configuration/kibana-logging.md)
plugins Plugin files location. Each plugin will be contained in a subdirectory. /usr/share/kibana/plugins