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: Applied GitHub Actions and SQL Server recovery labs

GitHub Actions cross-account role exercise|Issuer, trust and permissions

Check the federated identity, target trust and caller permission in succession.

What you will learn

Locate the cross-account failure at the relevant ownership boundary.

Prerequisite

The cases use fictional inputs.

Start the exercise →

What to predict

Check the federated identity, target trust and caller permission in succession.

From conditions to the decision
From conditions to the decision1: Federated identity — Align conditions — Target trust matches. 2: Target trust matches — Compare outcomes — Caller permission to assume the role. 3: Caller permission to assume the role — Verify the decision — Decision123Federated identityTarget trustmatchesCaller permissionto assume the roleDecisionFrom conditions to the decision1: Federated identity — Align conditions — Target trust matches. 2: Target trust matches — Compare outcomes — Caller permission to assume the role. 3: Caller permission to assume the role — Verify the decision — Decision123FederatedidentityTarget trustmatchesCallerpermission toassume the roleDecision
  1. Federated identity → Target trust matchesAlign conditions
  2. Target trust matches → Caller permission to assume the roleCompare outcomes
  3. Caller permission to assume the role → DecisionVerify the decision
Federated identity
Expected job / Different job
Target trust matches
Yes / No
Caller permission to assume the role
Yes / No
Decision
Locate the cross-account failure at the relevant ownership boundary.

Compare the cases

Synthetic observations
CaseConditionsDecision
Trial 1Federated identity Expected job, Target trust matches Yes, Caller permission to assume the role YesThe three modeled conditions pass. Check target operation permissions separately.
Trial 2Federated identity Different job, Target trust matches Yes, Caller permission to assume the role YesIdentity mismatch. Identify the expected workflow job.
Trial 3Federated identity Expected job, Target trust matches No, Caller permission to assume the role YesTrust mismatch. Check the principal evaluated in the target account.
Trial 4Federated identity Expected job, Target trust matches Yes, Caller permission to assume the role NoCaller lacks the grant. Inspect the permission for this target role.

Acceptance and limits

Uses synthetic identities and roles. No credentials, live policies or STS requests are used.

Read the initial conditions and operational goal.

Change one condition and compare the decision.

Record the model boundary and outstanding checks.

Change a condition

Uses synthetic identities and roles. No credentials, live policies or STS requests are used.

The three modeled conditions pass. Check target operation permissions separately.

Check your understanding

Choose an option to see the result and explanation.

What happens in trial 1?
Read the answer and reason

Answer: The three modeled conditions pass. Check target operation permissions separately. · Federated identity Expected job, Target trust matches Yes, Caller permission to assume the role Yes → The three modeled conditions pass. Check target operation permissions separately.

What happens in trial 2?
Read the answer and reason

Answer: Identity mismatch. Identify the expected workflow job. · Federated identity Different job, Target trust matches Yes, Caller permission to assume the role Yes → Identity mismatch. Identify the expected workflow job.

What happens in trial 3?
Read the answer and reason

Answer: Trust mismatch. Check the principal evaluated in the target account. · Federated identity Expected job, Target trust matches No, Caller permission to assume the role Yes → Trust mismatch. Check the principal evaluated in the target account.

Check, then explain in your own words

  1. Read the initial conditions and operational goal.
  2. Change one condition and compare the decision.
  3. Record the model boundary and outstanding checks.
Check your understanding: Locate the cross-account failure at the relevant ownership boundary.

Uses synthetic identities and roles. No credentials, live policies or STS requests are used.

Record the model boundary and outstanding checks.

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.