# Grant roles at the narrowest scope that works

Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.

Check 10 of 30: Grant roles at the narrowest scope that works. A role granted on a whole account, project or subscription covers every resource in it, including ones created later. Granting on specific resources keeps new resources out of the agent's reach by default.

## Why it matters

A role granted on a whole account, project or subscription covers every resource in it, including ones created later. Granting on specific resources keeps new resources out of the agent's reach by default.

## How, in each cloud

- **AWS:** Name specific resource ARNs in the policy; AWS's Bedrock guidance says to replace the wildcard with specific agent IDs once they exist.
- **Google Cloud:** Add IAM Conditions so a role binding applies only when conditions are met.
- **Azure:** Assign the role at resource or resource group scope instead of subscription or management group scope.

## What the documentation says

- "As a best practice for security purposes, replace the * with specific agent IDs after you have created them." ([source](https://docs.aws.amazon.com/bedrock/latest/userguide/agents-permissions.html))
- "You can use IAM Conditions to define and enforce conditional," ([source](https://cloud.google.com/iam/docs/conditions-overview))
- "Scope is the set of resources that the access applies to." ([source](https://learn.microsoft.com/en-us/azure/role-based-access-control/overview))

- [Previous: Compare the agent's granted permissions with what it used and remove the rest](/checklist/remove-unused-permissions/)
- [Next: Keep the encryption keys for agent data under your control and limit who can use them](/checklist/control-the-keys/)

## Related pages

- [Keep the encryption keys for agent data under your control and limit who can use them: the check, and how in AWS, Google Cloud and Azure](/checklist/control-the-keys/)
- [Block public access on storage the agent can write to: the check, and how in AWS, Google Cloud and Azure](/checklist/block-public-exposure/)
- [Put data stores the agent reads inside a perimeter that blocks copying data out: the check, and how in AWS, Google Cloud and Azure](/checklist/data-perimeter/)

## Sources

- docs.aws.amazon.com/bedrock/latest/userguide/agents-permissions.html: https://docs.aws.amazon.com/bedrock/latest/userguide/agents-permissions.html (read 10 Nov 2026)
- cloud.google.com/iam/docs/conditions-overview: https://cloud.google.com/iam/docs/conditions-overview (read 10 Nov 2026)
- learn.microsoft.com/en-us/azure/role-based-access-control/overview: https://learn.microsoft.com/en-us/azure/role-based-access-control/overview (read 10 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://aiagentaccesscontrol.com/checklist/narrowest-scope/
