INFRASTRUCTURE LEARNINGINFRASTRUCTURE LEARNING
インフラ大全インフラ大全IT INFRASTRUCTURE / LEARNING
Infrastructure learning guide
Find a lesson or lab/

Esc to close · Search terms stay on your device

LEARNING日本語

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.

What you will learn

Compare an approved read with a blocked change and locate the relevant policy layer.

Prerequisite

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.

Layers of the authorization decision
Layers of the authorization decision1: Request — Match the request — Role. 2: Role — Read grant scope — Boundary. 3: Boundary — Check upper limits — Organization123RequestRoleBoundaryOrganizationLayers of the authorization decision1: Request — Match the request — Role. 2: Role — Read grant scope — Boundary. 3: Boundary — Check upper limits — Organization123RequestRoleBoundaryOrganization
  1. Request → RoleMatch the request
  2. Role → BoundaryRead grant scope
  3. 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

Federation succeeds and listing in a member account works. A protected configuration change fails.
EvidenceResultMeaning
OIDCTemporary session issuedThe identity is established
List actionAllowedThis request meets the applicable conditions
Protected configuration updateExplicit denyCheck the applicable SCP
AcceptanceExercise required actions onlyInclude 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.

Does successful federation permit a configuration change?
Read the answer and reason

Answer: Evaluate the actual action · Authentication and API authorization are evaluated separately.

What if you add a broad Allow to an explicitly denied request?
Read the answer and reason

Answer: Review the deny with its owner · An applicable explicit deny takes precedence.

What establishes acceptance after a change?
Read the answer and reason

Answer: Required actions succeed and prohibited actions fail · Prove both service continuity and enforcement.

Check, then explain in your own words

  1. Identify the principal and action.
  2. Read the relevant grants and denials.
  3. 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.