WARNING: Version 6.1 of Kibana has passed its EOL date.

This documentation is no longer being maintained and may be removed. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation.

« Reporting and Security Reporting Troubleshooting »
Elastic Docs ›Kibana User Guide [6.1] ›Reporting from Kibana ›Configuring Reporting

Securing the Reporting Endpoints

edit

Securing the Reporting Endpoints

edit

In a production environment, you should restrict access to the X-Pack reporting endpoints to authorized users. This requires that you:

  1. Enable X-Pack security on your Elasticsearch cluster. For more information, see Getting Started with Security.
  2. Configure an SSL certificate for Kibana. For more information, see Configuring Security.

  3. Configure Watcher to trust the Kibana server’s certificate by adding it to the Watcher truststore on each node:

    1. Import the Kibana server certificate into the Watcher truststore using Java Keytool:

      keytool -importcert -keystore watcher-truststore.jks -file server.crt

      If the truststore doesn’t already exist, it is created.

    2. Make sure the xpack.http.ssl.truststore.path setting in elasticsearch.yml specifies the location of the Watcher truststore.
  4. Add one or more users who have the permissions necessary to use Kibana and X-Pack reporting. For more information, see Reporting and Security.

Once you’ve enabled SSL for Kibana, all requests to the X-Pack reporting endpoints must include valid credentials. For example, see the following page which includes a watch that submits requests as the built-in elastic user: Automating Report Generation.

For more information about configuring watches, see How Watcher Works.

« Reporting and Security Reporting Troubleshooting »