A newer version is available. For the latest information, see the current release documentation.

« Configuring authentication credentials for APM Server Configuring APM Server to use encrypted connections »

›

Granting users access to APM Server indices

IMPORTANT: This documentation is no longer updated. Refer to Elastic's version policy and the latest documentation.

Granting users access to APM Server indices

To enable users to access the indices a APM Server creates, grant them read and view_index_metadata privileges on the APM Server indices:

Create a role that has the read and view_index_metadata privileges for the APM Server indices. You can create roles from the Management > Roles UI in Kibana or through the role API. For example, the following request creates a apm_reader role:
```
POST _xpack/security/role/apm_reader
{
  "indices": [
    {
      "names": [ "apm-*" ], 
      "privileges": ["read","view_index_metadata"]
    }
  ]
}
```
If you use a custom APM Server index pattern, specify that pattern instead of the default apm-* pattern.
Assign your users the reader role so they can access the APM Server indices:
1. If you’re using the native realm, you can assign roles with the Management > Users UI in Kibana or through the user API. For example, the following request grants apm_user the apm_reader role:
```
POST /_xpack/security/user/apm_user
{
  "password" : "x-pack-test-password",
  "roles" : [ "apm_reader"],
  "full_name" : "APM Server User"
}
```
2. If you’re using the LDAP, Active Directory, or PKI realms, you assign the roles in the role_mapping.yml configuration file. For example, the following snippet grants APM Server User the apm_reader role:
```
apm_reader:
  - "cn=APM Server User,dc=example,dc=com"
```
  For more information, see Using Role Mapping Files.

« Configuring authentication credentials for APM Server Configuring APM Server to use encrypted connections »