You can use role-based access control to grant users access to secured resources. The roles that you set up depend on your organization’s security requirements and the minimum privileges required to use specific features.
Typically you need the create the following separate roles:
- Setup role for enabling Monitor Management.
- Writer role for creating, modifying, and deleting monitors.
- Reader role for Kibana users who need to view and create visualizations that access Synthetics data.
Elasticsearch security features provides built-in roles that grant a subset of the privileges needed by Synthetics users. When possible, assign users the built-in roles to minimize the affect of future changes on your security strategy. If no built-in role is available, you can assign users the privileges needed to accomplish a specific task.
In general, these are types of privileges you’ll work with:
- Elasticsearch cluster privileges: Manage the actions a user can perform against your cluster.
- Elasticsearch index privileges: Control access to the data in specific indices your cluster.
- Kibana space privileges: Grant users write or read access to features and apps within Kibana.
Intro to Kibana
ELK for Logs & Metrics