Topic lessonTopic: IAM: roles and permission limits
IAM permissions boundaries: permission limits, grants and exceptions
A permissions boundary sets the maximum permissions identity-based policies can grant to an IAM user or role. It does not grant permissions on its own. Compare read, write and delete access for a report role, then examine why direct resource-policy grants cannot all be reduced to one intersection formula.
Work through an identity-grant ceiling and distinguish grants to user, role and session principals in resource policies.
Know IAM Allow/Deny and role sessions. A managed policy is a reusable permissions policy; an ARN identifies an identity or resource. These are fixed reading examples, not instructions to create or change live policies.
A grant policy and a ceiling play different roles
The same kind of managed policy plays a different role when attached as a permissions policy versus used as a boundary. The former grants identity permissions; the latter constrains identity-policy grants. An Allow in a boundary alone does not establish access.
- Identity grant → This grant pathOperations offered by this grant; not a traffic path or execution order.
- Boundary ceiling → This grant pathLimits this grant path; direct resource grants are addressed separately below.
- Identity grant
- ReportWriter is granted read and write.
- Boundary ceiling
- Read and delete are inside the ceiling; this grants nothing.
- This grant path
- Reading appears in both; any applicable explicit Deny still wins.
Work through read, write and delete
| Operation | Identity Allow | Inside boundary | Result for this grant path |
|---|---|---|---|
| GetObject: read | Present | Yes | Within the permitted grant |
| PutObject: write | Present | No | Denied outside the ceiling |
| DeleteObject: delete | Absent | Yes | Denied for lack of a grant |
For this teaching example, the boundary includes GetObject and DeleteObject, while identity policies grant GetObject and PutObject. Only GetObject is in both. DeleteObject being inside the boundary does not create the missing identity grant. The table is not a live S3 access test.
Choose an option to see the result and explanation.
For resource grants, identify the recipient principal
The following table compares resource-policy grants within the same account. Implicit denial is missing permission; explicit denial comes from an applicable Deny statement. “Not limited” refers to the specified implicit denial; it does not remove applicable explicit Deny or organization controls.
| Resource-policy recipient | How the grant relates to implicit limits | Distinction to retain |
|---|---|---|
| IAM user ARN, not a federated session | Not limited by implicit denial in identity policy/boundary | A user grant differs from grants involving derived sessions |
| IAM role ARN named in Principal | Limited by implicit denial in boundary/session policies | A role ARN differs from an assumed-role session ARN |
| Direct grant to role session ARN | Not limited by implicit denial in identity/boundary/session policies | This is a direct grant to the specific session |
| Wildcard Principal with aws:PrincipalArn condition | Do not assume identity-side implicit ceilings always constrain it | Different from naming the role ARN directly in Principal |
Choose an option to see the result and explanation.
Read session policies and explicit Deny in context
When a session policy is passed, the role’s identity-policy grant path is limited by role permissions, boundary and session policy. Do not extend that explanation unconditionally to the direct resource grants above. The grant path and recipient principal are essential assumptions.
AWS warns against NotPrincipal combined with Deny in resource policies for IAM users or roles with a boundary. Such a statement can deny those principals regardless of the intended exclusions. This is a review consideration, not a live-policy change performed by this lesson.
Choose an option to see the result and explanation.
Record the grant path before considering a change
- Fix the user/role/session principal, requested action/resource and account relationship.
- Write the identity grant and boundary ceiling separately.
- Check session policies and any resource grants, including their recipient.
- Review applicable explicit Deny and organization/service controls.
- Explain the intended scope and evidence to an administrator instead of removing safeguards to test.
Check, then explain in your own words
- Separate a grant from its ceiling.
- Compare three operations in the restricted identity example.
- Distinguish user/role/session grants and explicit Deny.
Check your understanding: Does attaching a boundary make one intersection formula sufficient for all access?
No. Check resource-grant recipients and account relationships.
An identity-grant ceiling and direct same-account resource grants have different conditions. Applicable explicit Deny and other controls still remain.
Sources and conditions checked
The official references used in this lesson are collected here with their scope, conditions and corresponding sections. Independent expert review and live AWS comparison have not been performed.
Scope and conditionsIdentity permission ceiling; no grant by boundary; same-account user/role/session direct resource grants; explicit deny and NotPrincipal warning.
Used in this lessonA grant policy and a ceiling play different roles Work through read, write and delete For resource grants, identify the recipient principal Read session policies and explicit Deny in context
Scope and conditionsApplicable request context, explicit versus implicit deny, identity/resource/session evaluation and service exceptions; not a universal union/intersection equation.
Used in this lessonFor resource grants, identify the recipient principal Read session policies and explicit Deny in context
Scope and conditionsAccount delegation versus root user; IAM role ARN versus role-session ARN; same-account direct grants and wildcard conditions.
Used in this lessonFor resource grants, identify the recipient principal
- AssumeRole API referenceChecked:
Scope and conditionsPermissions; same/cross-account trust; temporary credentials; session policies; DurationSeconds/role chaining. No API executed.
Used in this lessonRead session policies and explicit Deny in context