If you want Winlogbeat 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, Winlogbeat 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 Winlogbeat data and visualize it in Kibana, users need access to the indices Winlogbeat creates.
If encryption is enabled on the cluster, you need to enable HTTPS in the Winlogbeat configuration.
Winlogbeat uses the
beats_systemuser to send monitoring data to Elasticsearch. If you plan to monitor Winlogbeat 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.
Winlogbeat features that require authorizationedit
After securing Winlogbeat, make sure your users have the roles (or associated
privileges) required to use these Winlogbeat features. You must create the
winlogbeat_reader roles (see Configure authentication credentials and
Grant users access to Winlogbeat indices).
kibana_user roles are built-in.
Send data to a secured cluster
Load index templates
Load Winlogbeat dashboards into Kibana
Load machine learning jobs
Read indices created by Winlogbeat
View Winlogbeat dashboards in Kibana