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 Grant users access to secured resources »
Elastic Docs ›Packetbeat Reference [7.4] ›Securing Packetbeat

Configure Packetbeat to use X-Pack security

edit

Configure Packetbeat to use X-Pack security

edit

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

  1. Grant users access to secured resources.

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

  2. Configure authentication credentials.

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

  3. Configure Packetbeat to use encrypted connections.

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

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

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