Docs
Metricbeat Reference [7.8] » Secure Metricbeat » Configure Metricbeat to use security features
« Secure communication with Logstash Grant users access to secured resources »

Configure Metricbeat to use security featuresedit

If you want Metricbeat 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 Metricbeat 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, Metricbeat must either provide basic authentication credentials or present a client certificate.

  4. Configure Metricbeat to use encrypted connections.

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

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

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