Organizations opt to use multiple AWS accounts for a variety of reasons including:
Users and groups within one AWS account will often need to access resources in another AWS account. Instead of creating separate IAM users and groups in each account, access can be delegated to IAM users and groups in a different AWS account using cross-account IAM roles. Certain services also provide resource-based policies to allow access across accounts. This lab walks through the mechanics of configuring and using cross-account roles and resource-based policies, specifically S3 bucket policies. Policy evaluation logic is also discussed.
Upon completion of this intermediate-level lab, you will be able to:
Familiarity with the following is recommended:
The following content can be used to fulfill the prerequisite:
May 9th, 2024 - Resolved an issue causing validation checks to fail
September 15th, 2023 - Resolved an issue causing the build account S3 bucket to not provision