Case 0283DB · Cloud · L5 Expert
AWS Policy Evaluation Logic
- 01 Context
- 02 Mechanism
- 03 Lessons
What a strong answer covers
Try it out loud first. Then check yourself:
- One request can meet identity, resource, boundary, session, SCP and RCP policies; misreading them causes outages and holes
- An explicit deny in any applicable policy wins; with no allow at all, the default is implicit deny
- SCPs, RCPs, permission boundaries and session policies only cap permissions; they never grant anything
- Cross-account needs both sides: the caller identity policy and the resource policy in the other account must allow
- SCPs skip the management account and service-linked roles; validate with the policy simulator and Access Analyzer
If the interviewer pushes back
- A role in account A has s3:* and the bucket in account B has no bucket policy. Can it read? What changes in the same account?