Install Kibana with RPM
editInstall Kibana with RPM
editThe 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.
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.
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.
Import the Elastic PGP key
editWe sign all of our packages with the Elastic 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
Installing from the RPM repository
editVersion 9.0.0-beta1 of Kibana has not yet been released.
Download and install the RPM manually
editVersion 9.0.0-beta1 of Kibana has not yet been released.
Start Elasticsearch and generate an enrollment token for Kibana
editWhen 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
elasticbuilt-in superuser. - 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
elasticsearch-create-enrollment-token tool:
bin/elasticsearch-create-enrollment-token -s kibana
Start Kibana and enter the enrollment token to securely connect Kibana with Elasticsearch.
Run Kibana with systemd
editTo 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.
Configure Kibana via the config file
editKibana 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 RPM
editThe 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 |
|
|
bin |
Binary scripts including |
|
|
config |
Configuration files including |
|
|
data |
The location of the data files written to disk by Kibana and its plugins |
|
|
logs |
Logs files location |
|
|
plugins |
Plugin files location. Each plugin will be contained in a subdirectory. |
|