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.
Locate the cross-account failure at the relevant ownership boundary.
The cases use fictional inputs.
What to predict
Check the federated identity, target trust and caller permission in succession.
- Federated identity → Target trust matchesAlign conditions
- Target trust matches → Caller permission to assume the roleCompare outcomes
- 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
| Case | Conditions | Decision |
|---|---|---|
| Trial 1 | 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. |
| Trial 2 | Federated identity Different job, Target trust matches Yes, Caller permission to assume the role Yes | Identity mismatch. Identify the expected workflow job. |
| Trial 3 | 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. |
| Trial 4 | Federated identity Expected job, Target trust matches Yes, Caller permission to assume the role No | Caller 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.
{"origin":"Identity mismatch. Identify the expected workflow job.","trust":"Trust mismatch. Check the principal evaluated in the target account.","policy":"Caller lacks the grant. Inspect the permission for this target role.","allowed":"The three modeled conditions pass. Check target operation permissions separately."}Check your understanding
Choose an option to see the result and explanation.
Check, then explain in your own words
- Read the initial conditions and operational goal.
- Change one condition and compare the decision.
- 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.
Scope and conditionsCheck the federated identity, target trust and caller permission in succession.
Used in this lessonWhat to predict Acceptance and limits