IAM policy evaluation: explicit deny, SCPs, RCPs, permissions boundaries and session policies
- An explicit Deny in any applicable policy overrides every Allow, so a NotAction Deny can block far more actions than its author intended.
- SCPs limit principals in member accounts and RCPs limit resources in member accounts; neither policy type ever grants a permission on its own.
- A permissions boundary caps a role's identity-based permissions, so an action must be allowed by both the boundary and an identity policy to succeed.
- Session policies passed on AssumeRole narrow a single session to the intersection of the role's permissions and the session policy document.
- Cross-account access needs an Allow in the caller's identity policy and in the resource owner's resource-based policy, such as a bucket or key policy.