A landing zone is a well-architected, multi-account AWS environment based on security and compliance best practices. AWS Control Tower automates the setup of a new landing zone using best-practices blueprints for identity, federated access, and account structure.
Examples of blueprints that are automatically implemented in your landing zone include the following:
- Create a multi-account environment using AWS Organizations.
- Provide identity management using the default directory found within AWS IAM Identity Center.
- Provide federated access to accounts using IAM Identity Center.
- Centralize logging from AWS CloudTrail and AWS Config stored in Amazon Simple Storage Service (Amazon S3).
- Enable cross-account security audits using IAM Identity Center.
Within your landing zone you can optionally configure log retention, AWS CloudTrail trails, AWS KMS Keys, and AWS account access. The landing zone set up by AWS Control Tower is managed using a set of mandatory and optional controls. Mandatory controls are always applied on your behalf by AWS Control Tower, while optional controls can be self-selected based on your unique needs to ensure accounts and configurations comply with your policies.