This section lists the privileges that you can assign to a role.
|
All cluster administration operations, like snapshotting, node shutdown/restart, settings update, rerouting, or managing users and roles. |
|
All cluster read-only operations, like cluster health & state, hot threads, node info, node & cluster stats, snapshot/restore status, pending cluster tasks. |
|
Builds on |
|
All security related operations such as CRUD operations on users and roles and cache clearing. |
|
All operations on index templates. |
|
All operations on ingest pipelines. |
|
All privileges necessary for a transport client to connect. |
|
Any action on an index |
|
All actions that are required for monitoring (recovery, segments info, index stats & status). |
|
All |
|
Read-only access to information about an index (aliases, aliases exists, get index, exists, field mappings, mappings, search shards, type exists, validate, warmers, settings). |
|
Read only access to actions (count, explain, get, mget, get indexed scripts, more like this, multi percolate/search/termvector, percolate, scroll, clear_scroll, search, suggest, tv). Also grants access to the update mapping action. |
|
Privilege to index and update documents. Also grants access to the update mapping action. |
|
Privilege to index documents. Also grants access to the update mapping action. |
|
Privilege to delete documents. |
|
Privilege to perform all write operations to documents, which includes the permission to index, update, and delete documents as well as performing bulk operations. Also grants access to the update mapping action. |
|
Privilege to delete an index. |
|
Privilege to create an index. A create index request may contain aliases to be
added to the index once created. In that case the request requires the |
|
Privilege to view the the index metadata such as its mappings and settings. This privilege is primarily available for use by Kibana users. |
The run_as
permission enables an authenticated user to submit requests on
behalf of another user. The value can be a user name or a comma-separated list
of user names. (You can also specify users as an array of strings or a YAML
sequence.) For more information, see
Submitting Requests on Behalf of Other Users.