This functionality is experimental and may be changed or removed completely in a future release. Elastic will take a best effort approach to fix any issues, but experimental features are not subject to the support SLA of official GA features.
« Secure communication with Logstash Grant users access to secured resources »
Elastic Docs ›Journalbeat Reference [7.7] ›Secure Journalbeat

Configure Journalbeat to use security features

edit

Configure Journalbeat to use security features

edit

If you want Journalbeat to connect to a cluster that has security features enabled, there are extra configuration steps:

  1. Grant users access to secured resources.

    You can use role-based access control to grant Journalbeat users access to secured resources.

  2. Grant access using API keys.

    You can use API keys to grant access to Elasticsearch more securely.

  3. Configure authentication credentials.

    To interact with a secured cluster, Journalbeat must either provide basic authentication credentials or present a client certificate.

  4. Configure Journalbeat to use encrypted connections.

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

For more information about security features, see Secure a cluster.

« Secure communication with Logstash Grant users access to secured resources »