If you want Packetbeat to connect to a cluster that has X-Pack security enabled, there are extra configuration steps:
To send data to a secured cluster through the
elasticsearchoutput, Packetbeat 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.
To search the indexed Packetbeat data and visualize it in Kibana, users need access to the indices Packetbeat creates.
If encryption is enabled on the cluster, you need to enable HTTPS in the Packetbeat configuration.
Packetbeat uses the
beats_systemuser to send monitoring data to Elasticsearch. If you plan to monitor Packetbeat 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.
Packetbeat features that require authorizationedit
After securing Packetbeat, make sure your users have the roles (or associated
privileges) required to use these Packetbeat features. You must create the
packetbeat_reader roles (see Configure authentication credentials and
Grant users access to Packetbeat indices). The
kibana_user roles are
Send data to a secured cluster
Run Filebeat modules
Load index templates
Load Packetbeat dashboards into Kibana
Load machine learning jobs
Read indices created by Packetbeat
View Packetbeat dashboards in Kibana