Update an agent's access control list
https://{kibana_url}
- PUT /api/agent_builder/agents/{id}/access_control
- PUT /s/{space_id}/api/agent_builder/agents/{id}/access_control
Refer to Spaces for more information.
Replace the per-agent access-control entries. The agent owner, cluster admins, and anyone access control grants Manager can call this endpoint. Each call replaces the entire entries list — the most recent successful update wins. To learn more about agents, refer to the agents documentation.
[Required authorization] Route required privileges: agentBuilder:manageAgents.
Path Parameters
-
idstringrequired -
The unique identifier of the agent whose access control to update.
Request
-
entriesobject · max: 100required -
Access-control entries to apply to the agent. Each entry has a
type(currently onlyuseris supported), aname(the principal username), and arole. -
namestring · min: 1 · max: 1024required -
Case-sensitive Kibana username of the principal to grant access to.
-
rolerequired -
Role granted to the principal. Roles are hierarchical:
userallows viewing, listing, reading, and running the agent;editoradds updating the agent and its access control;manageradds deleting the agent and managing access control. -
Values:
usereditormanager -
typerequired -
Values:
user
Responses
Indicates a successful response
Bad Request — the request body failed validation, or the request targets the built-in Elastic default agent (which cannot have custom access control).
Not Found — no agent with this ID is visible to the caller, or the caller lacks write access. Matches the existing agentNotFound shape so unprivileged callers cannot probe for hidden agents.