Skip to content
Cloud Governance Tools

IAM permissions boundaries: what it can block and where it stops

IAM permissions boundaries is a AWS mechanism. AWS documents a permissions boundary as a managed policy attached to an IAM user or role that sets the maximum permissions that an identity-based policy can grant to that entity. It applies to a single IAM user or role it is attached to; it does not apply to other principals or to resources.

All mechanisms ยท AWS guardrails

AWS documents a permissions boundary as a managed policy attached to an IAM user or role that sets the maximum permissions that an identity-based policy can grant to that entity. It is evaluated within the account with the entity's other policies.

AWS documents a permissions boundary as a managed policy attached to an IAM user or role that sets the maximum permissions an identity-based policy can grant that entity. It limits permissions but grants none, applies only to the one user or role it is attached to, and is supported for users and roles only.

A NotPrincipal element with a Deny effect in a resource-based policy always denies any principal that has a boundary attached. The IAM policy simulator can test boundaries, one at a time. The library holds 2 permissions boundary entries; one example limits a user to S3, CloudWatch and EC2 and shows an iam:CreateUser policy failing because the boundary does not allow the action.

Documented limits

  • A permissions boundary limits permissions but does not grant them on its own. (source)
  • Permissions boundaries are supported for IAM users and roles only. (source)
  • A NotPrincipal element with a Deny effect in a resource-based policy always denies any principal that has a permissions boundary attached. (source)

Testing before enforcement

AWS documents that the IAM policy simulator can test IAM permissions boundaries, one boundary at a time. (source)

The 2 library entries written in it

Where Act is behind

Act writes guardrails in the provider's own mechanisms and hands them to your pipeline to enforce, so it is bounded by what those mechanisms can express in each cloud. It does not apply them itself, the boundary types it names are AWS's and Azure's, and exception and waiver handling after a guardrail ships was described as roadmap.

Sources

  1. IAM permissions boundaries, read 10 Nov 2026
  2. Testing, read 10 Nov 2026

Last reviewed 16 Nov 2026.