# Resource-based policy

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

A permission policy attached to the resource being accessed, such as a Lambda function, an S3 bucket or a KMS key, naming who may use it. It works alongside the caller's own identity-based policy and always names a principal. It is the counterpart of the policy attached to the caller.

## An example, sourced

AWS documents that for an Amazon Bedrock agent to use a Lambda function, you must attach a resource-based policy to the function to provide permissions for the agent. The step is separate from the agent\'s own role: the policy lives on the function and says who may call it. The page points to the AWS Lambda Developer Guide for more information about resource-based policies in Lambda, which is where the policy syntax and the principals it can name are documented.

## Why it matters here

The same role can reach a resource through its own policy or through the resource's policy. A review that reads only the role misses grants written on the targets. It also shows which other principals, including other accounts, were granted the same resource.

## Related pages

- [AI agent: meaning and an example](/glossary/ai-agent/)
- [AI workload: meaning and an example](/glossary/ai-workload/)
- [Execution role: meaning and an example](/glossary/execution-role/)
- [All of them](/glossary/)

## Sources

- https://docs.aws.amazon.com/bedrock/latest/userguide/agents-lambda.html (read 10 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://aiagentaccesscontrol.com/glossary/resource-based-policy/
