Elasticsearch API keys still inherit the principal's limits
An Elasticsearch API key can look like a standalone credential, especially when an automation stores it in a secret manager. The key is not an independent superuser. It represents a principal and can carry role descriptors that narrow access. Teams should review both the requested key permissions and the permissions of the user who created it.
The effective permission set
Elastic documents API keys as a way to authenticate and authorize requests to Elasticsearch resources. For a user API key, the creator can choose predefined roles or custom privileges. Role descriptors on the key limit the resulting permissions. The documented result is an intersection: the key cannot have more access than the authenticated user who created it.
That intersection is useful, but it has two sides. A narrowly scoped key created by a broad administrator may still be safe for the automation if the descriptor is correct.…