IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.
« Secure communication with Logstash by using SSL Heartbeat features that require authorization »
Elastic Docs ›Heartbeat Reference [6.7] ›Securing Heartbeat

Configure Heartbeat to use X-Pack security

edit

Configure Heartbeat to use X-Pack security

edit

If you want Heartbeat to connect to a cluster that has X-Pack security enabled, there are extra configuration steps:

  1. Configure authentication credentials.

    To send data to a secured cluster through the elasticsearch output, Heartbeat needs to authenticate as a user who can manage index templates, monitor the cluster, create indices, and read and write to the indices it creates.

  2. Grant users access to Heartbeat indices.

    To search the indexed Heartbeat data and visualize it in Kibana, users need access to the indices Heartbeat creates.

  3. Configure Heartbeat to use encrypted connections.

    If encryption is enabled on the cluster, you need to enable HTTPS in the Heartbeat configuration.

  4. Set the password for the built-in monitoring user.

    Heartbeat uses the beats_system user to send monitoring data to Elasticsearch. If you plan to monitor Heartbeat in Kibana and have not yet set up the password, set it up now.

For more information about X-Pack security, see Securing the Elastic Stack.

« Secure communication with Logstash by using SSL Heartbeat features that require authorization »