# Permissions boundary

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

A permissions boundary is a managed policy set on a user or role that defines the maximum permissions its identity-based policies can grant. It grants nothing by itself. The effective permissions are the intersection of the boundary and the identity-based policies, and an explicit deny in either one overrides an allow.

## An example, sourced

AWS says a permissions boundary does not define the maximum permissions that a resource-based policy can grant to an entity, and recommends boundaries for delegating permissions management inside an account, for example when developers create roles.

## Why it matters here

The workbench builds a boundary policy as one of its five policy types and checks it as an identity policy.

## Related pages

- [Service control policy: meaning and an example](/glossary/service-control-policy/)
- [Resource control policy: meaning and an example](/glossary/resource-control-policy/)
- [Session policy: meaning and an example](/glossary/session-policy/)
- [All of them](/glossary/)

## Sources

- https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_boundaries.html (read 16 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://iampolicygenerator.com/glossary/permissions-boundary/

This site is not affiliated with Amazon Web Services. AWS service and product names are used only to describe AWS services.
