STS · CI/CD · Intermediate
The token expires mid-deploy
A long deployment succeeds initially and then receives ExpiredToken.
INITIAL ALERT
A long deployment succeeds initially and then receives ExpiredToken.
You are primary on-call. Establish the failure domain, protect healthy capacity, and choose the safest next action.
Role assumption and early API calls succeed.
The decisive evidence and solution remain locked inside the simulation.WHAT THIS TESTS
Production judgment across STS · CI/CD.
An attached Allow is only one part of effective authorization. Production diagnosis requires checking explicit denies, boundaries, resource policies, session conditions, and credential lifetime.
- 01Evaluate layered AWS authorization
- 02Recognize token and rotation failures
- 03Restore access without broad permissions
SIMULATION STRUCTURE
Four evidence layers. No answer shown here.
The full exercise unlocks each layer as you commit to decisions.
Alert
Confirm the reported symptom and customer impact.
Baseline
Compare the failing path with a known-good condition.
Finding
Identify the evidence that separates plausible causes.
Change
Choose a controlled recovery and a durable prevention step.
Can you make the call without seeing the solution?
Try three incidents free. Paid incidents unlock only after Stripe confirms lifetime access.