Install Kibana with RPMedit

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, Centos, Red Hat, and Oracle Enterprise.

RPM install is not supported on distributions with old versions of RPM, such as SLES 11 and CentOS 5. Please see Install Kibana with .tar.gz instead.

This package is free to use under the Elastic license. It contains open source and free commercial features and access to paid commercial features. Start a 30-day trial to try out all of the paid commercial features. See the Subscriptions page for information about Elastic license levels.

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

Import the Elastic PGP Keyedit

We sign all of our packages with the Elastic Signing Key (PGP key D88E42B4, available from with fingerprint:

4609 5ACC 8548 582C 1A26 99A9 D27D 666C D88E 42B4

Download and install the public signing key:

rpm --import

Installing from the RPM repositoryedit

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:

name=Kibana repository for 6.x packages

And your repository is ready for use. You can now install Kibana with one of the following commands:

sudo yum install kibana 
sudo dnf install kibana 
sudo zypper install kibana 

Use yum on CentOS and older Red Hat based distributions.

Use dnf on Fedora and other newer Red Hat distributions.

Use zypper on OpenSUSE based distributions

An alternative package, kibana-oss, which contains only features that are available under the Apache 2.0 license is also available. To install it, use the following baseurl in your kibana.repo file:


Download and install the RPM manuallyedit

The RPM for Kibana v6.8.23 can be downloaded from the website and installed as follows:

shasum -a 512 kibana-6.8.23-x86_64.rpm 
sudo rpm --install kibana-6.8.23-x86_64.rpm

Compare the SHA produced by shasum with the published SHA.

Alternatively, you can download the following package, which contains only features that are available under the Apache 2.0 license:

SysV init vs systemdedit

Kibana is not started automatically after installation. How to start and stop Kibana depends on whether your system uses SysV init or systemd (used by newer distributions). You can tell which is being used by running this command:

ps -p 1

Running Kibana with SysV initedit

Use the chkconfig command to configure Kibana to start automatically when the system boots up:

sudo chkconfig --add kibana

You can start and stop Kibana using the service command:

sudo -i service kibana start
sudo -i service kibana stop

If Kibana fails to start for any reason, it will print the reason for failure to STDOUT. Log files can be found in /var/log/kibana/.

Running Kibana with systemdedit

To configure Kibana to start automatically when the system boots up, 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.

Configuring Kibana via config fileedit

Kibana loads its configuration from the /etc/kibana/kibana.yml file by default. The format of this config file is explained in Configuring Kibana.

Directory layout of RPMedit

The RPM places config files, logs, and the data directory in the appropriate locations for an RPM-based system:

Type Description Default Location Setting


Kibana home directory or $KIBANA_HOME



Binary scripts including kibana to start the Kibana server and kibana-plugin to install plugins



Configuration files including kibana.yml



The location of the data files written to disk by Kibana and its plugins



Transpiled source code. Certain administrative actions (e.g. plugin install) result in the source code being retranspiled on the fly.



Plugin files location. Each plugin will be contained in a subdirectory.