cross-account access
A principal in one AWS account using resources in another, allowed only when policies on both sides agree.
In more detail
It is the normal way for shared pipelines, security tooling and vendors to work across a multi-account organisation. The usual pattern is a role in the target account whose trust policy names the caller, plus an identity policy in the caller's account that allows sts:AssumeRole on it.
Related terms
- AssumeRole — The STS operation a principal calls to take on an IAM role and receive that role's temporary credentials.
- trust policy — A JSON document on a cloud role that says who may assume the role and under which conditions.
- external ID — Identities from outside an organisation, such as the work accounts of partners or the social accounts of customers, that are allowed to sign in to its apps.
Taught in
- Surviving A Hundred And Eighty Minutes — AWS Certified DevOps Engineer – Professional (DOP-C02) Exam Prep
- CodePipeline: Stages, Actions And The Key Nobody Shared — AWS Certified DevOps Engineer – Professional (DOP-C02) Exam Prep
- StackSets: Eighty Failures Before Lunch — AWS Certified DevOps Engineer – Professional (DOP-C02) Exam Prep
- Recovery To RTO And RPO: Backups Nobody Could Delete — AWS Certified DevOps Engineer – Professional (DOP-C02) Exam Prep
- Collecting Logs And Metrics: The Disk Nobody Measured — AWS Certified DevOps Engineer – Professional (DOP-C02) Exam Prep
- Automating Data Protection: Keys, Secrets And A Partner Shortcut — AWS Certified DevOps Engineer – Professional (DOP-C02) Exam Prep
- Cross-Account AssumeRole Chains & Temporary STS — Cloud Security & DevSecOps Engineering