Grant privileges and roles needed for monitoring
Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud. Availability This functionality is generally available and ready for production usage. Serverless interfaces and procedures might differ from classic Elastic Stack deployments. The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability This functionality is generally available and ready for production usage. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
Serverless
Generally available
Stack
Generally available
Elasticsearch security features provides built-in users and roles for monitoring. The privileges and roles needed depend on the method used to collect monitoring data.
Built-in users are not available when running Elastic Cloud Hosted. To send monitoring data securely, create a monitoring user and grant it the roles described in the following sections.
If you’re using internal collection to collect metrics about Filebeat, Elasticsearch security features provides the
beats_systembuilt-in user andbeats_systembuilt-in role to send monitoring information. You can use the built-in user, if it’s available in your environment, or create a user who has the privileges needed to send monitoring information.If you use the
beats_systemuser, make sure you set the password.If you don’t use the
beats_systemuser:Create a monitoring role, called something like
filebeat_monitoring, that has the following privileges:Type Privilege Purpose Cluster monitorRetrieve cluster details (e.g. version) Index create_indexon.monitoring-beats-*indicesCreate monitoring indices in Elasticsearch Index create_docon.monitoring-beats-*indicesWrite monitoring events into Elasticsearch Assign the monitoring role, along with the following built-in roles, to users who need to monitor Filebeat:
Role Purpose kibana_adminUse Kibana monitoring_userUse Stack Monitoring in Kibana to monitor Filebeat
If you’re using Metricbeat to collect metrics about Filebeat, Elasticsearch security features provides the
remote_monitoring_userbuilt-in user, and theremote_monitoring_collectorandremote_monitoring_agentbuilt-in roles for collecting and sending monitoring information. You can use the built-in user, if it’s available in your environment, or create a user who has the privileges needed to collect and send monitoring information.If you use the
remote_monitoring_useruser, make sure you set the password.If you don’t use the
remote_monitoring_useruser:Create a user on the production cluster who will collect and send monitoring information.
Assign the following roles to the user:
Role Purpose remote_monitoring_collectorCollect monitoring metrics from Filebeat remote_monitoring_agentSend monitoring data to the monitoring cluster Assign the following role to users who will view the monitoring data in Kibana:
Role Purpose monitoring_userUse Stack Monitoring in Kibana to monitor Filebeat