Topic lessonTopic: Multi-account guardrails and deployment checks
AWS STS AssumeRole across accounts: trust, authorization and session scope
A successful role assumption does not establish permission for the business operation. Evaluate a cross-account read in three separate stages.
Evaluate a cross-account read in three separate stages.
The exercise uses fictional roles and contains no real credentials or tokens.
Separate role assumption from the operation itself
Cross-account AssumeRole needs caller authorization and trust in the target role. A successful request creates a temporary session.
- Caller → Role assumptionAsk for the role
- Role assumption → SessionCheck both sides
- Session → Business operationVerify the operation
- Caller
- Reporting service
- Role assumption
- Caller authorization and trust
- Session
- Scope restricted to reads
- Business operation
- Read the intended report
Compare attempts to use the same role
| Attempt | Observation | Next check |
|---|---|---|
| Caller lacks AssumeRole grant | Role assumption fails | Check caller authorization |
| Caller excluded from target trust | Role assumption fails | Check target trust |
| Assumption and permitted read | Report is readable | Record the session and scope |
| Assumption succeeds; session excludes write | Write denied | Check post-assumption permissions |
A session policy can restrict a role’s permissions. It cannot grant actions beyond those allowed by the role’s policy.
Match the evidence to the failing stage
Identify the failure stage. Separate a denied AssumeRole request from an operation such as an S3 request returning a denial after assumption.
Define the minimum scope. Choose required operations, resources and lifetime for the target session.
Keep credentials out of the record. Record roles, operation names, timestamps and results without copying secret values.
Check the worked example
Choose an option to see the result and explanation.
Check, then explain in your own words
- Identify the caller and requested role.
- Check whether role assumption succeeded.
- Verify permissions for the business operation separately.
Check your understanding: Does AssumeRole success prove that deployment or an audit export succeeded?
Verify the required operation under the resulting session.
Role assumption establishes a prerequisite.
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.
- AWS STS AssumeRoleChecked:
Scope and conditionsCross-account trust and authorization, temporary sessions and session policy limits.
Used in this lessonSeparate role assumption from the operation itself Compare attempts to use the same role Match the evidence to the failing stage