Topic lessonTopic: AWS authorization, encryption, audit and response
Trace AWS IAM permissions for a GitHub Actions deployment
A single role can receive different decisions for different actions. Compare an approved read with a blocked change and locate the relevant policy layer.
Compare an approved read with a blocked change and locate the relevant policy layer.
This exercise uses fictional evidence and makes no changes in a live environment.
Evaluate the same deployment identity
A permissions boundary limits identity-based permissions. This example uses a same-account role and has no separate grant from a resource policy.
- Request → RoleMatch the request
- Role → BoundaryRead grant scope
- Boundary → OrganizationCheck upper limits
- Request
- Principal, action and resource
- Role
- Candidate identity grant
- Boundary
- Permission limit
- Organization
- Effective controls
An update from a fictional deployment role
| Evidence | Result | Meaning |
|---|---|---|
| OIDC | Temporary session issued | The identity is established |
| List action | Allowed | This request meets the applicable conditions |
| Protected configuration update | Explicit deny | Check the applicable SCP |
| Acceptance | Exercise required actions only | Include the expected denial in the same test |
Using the exact request separates authentication from each authorization decision.
Evidence for the decision
Identify the request Record issuer, principal, action, resource, account and policy evaluation time.
Read the controls first Ask the responsible owner to compare the effective organization and resource policies for the denied request.
Keep a negative control Verify required operations and denial of out-of-scope changes.
Check your decision
Choose an option to see the result and explanation.
Check, then explain in your own words
- Identify the principal and action.
- Read the relevant grants and denials.
- Run approved positive and negative checks.
Check your understanding: Does a successful list action allow every action in the account?
Check the policy on the actual action and resource.
Different conditions may apply to reads and writes.
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.
- Policy evaluation logicChecked:
Scope and conditionsExplicit deny, permissions boundaries and SCPs.
Used in this lessonEvaluate the same deployment identity An update from a fictional deployment role Evidence for the decision