Skip to main content
A request IAM refuses answers 403 with the code 10010. The detail names the action the request needed and says whether no role allowed it or a role denied it, and a deny names the roles behind it. A route with no action is the one refusal whose detail names no action.

No Role Allows the Action

Output
The principal holds no role with an allow statement for the action, or holds no grant at all. Add the action to a role the principal holds, or grant one, and the request passes within five seconds.

A Role Denies the Action

Output
denied_role_ids lists every granted role with a deny statement matching the action. A deny wins over any allow, so the request passes only once no granted role denies it.

The Route Has No Action

A route that declares no action is refused for a principal IAM manages. The detail names the request and the principal instead of an action, and for a service account token it names the service account.
Output
No role can cover the route until it has an action.

Other Refusals

What to Check

  1. GET /v2/iam/settings shows whether IAM is enabled. With it disabled, grants decide nothing.
  2. GET /v2/iam/grants?filter[principal_type]=...&filter[principal_id]=... lists the principal’s roles.
  3. GET /v2/iam/roles/{role_id}/statements shows each role’s statements. The action must appear in an allow statement, exactly or under a wildcard, and in no deny statement.
  4. GET /v2/iam/actions?filter[path][contains]=... confirms which action the route declares.
  5. A change made in the last five seconds may not have reached the request yet.
Explain answers the first four questions in one request.

Errors From the IAM Endpoints