Management and Governance
AWS Control Tower
Service for setting up and governing a multi-account AWS environment following best practices. It creates a landing zone by orchestrating AWS Organizations and other services, and applies controls (guardrails) to keep accounts from drifting away from those practices.
Exam phrases that point here
«set up a secure multi-account environment following best practices with the least operational overhead»
AWS Control Tower sets up a ready-made landing zone: OUs, accounts for logs and auditing, centralized identity, and security and compliance controls, without having to design it piece by piece.
When not: If the scenario only asks to group accounts, apply your own SCPs, or consolidate billing, AWS Organizations is enough, as it is the foundation Control Tower works on.
«landing zone»
A landing zone is the recommended starting point of a cloud environment: accounts, OU structure, network, and security. Control Tower is the AWS service that creates and governs it in a managed way.
When not: The term alone is not enough: a landing zone can also be built custom, as your own solution on AWS Organizations. The clue points to Control Tower when the question also asks for a managed, fast approach or one with controls included.
«apply preventive and detective guardrails to all accounts in an OU»
Controls (formerly called guardrails) are applied to an entire OU: preventive ones are implemented with Organizations policies such as SCPs, detective ones with AWS Config rules, and proactive ones with CloudFormation hooks.
When not: If you only need to evaluate resource configuration in one account, AWS Config rules are enough; if the question asks to collect security findings from several tools, AWS Security Hub fits.
«provision new accounts already configured to the company standard»
Account Factory creates accounts within the landing zone and applies the baseline configuration and the controls of the target OU, in a repeatable, self-service way.
When not: If creating an empty account within the organization is enough, Organizations does that on its own. If the team wants to manage account creation with Terraform, it is still Control Tower, through Account Factory for Terraform (AFT).
«centralize the activity logs of all accounts in a dedicated account with restricted access»
The landing zone includes a log archive account (since version 4.0, CloudTrail administrator) with a central Amazon S3 bucket that receives the CloudTrail logs of all accounts, separate from the people who operate the workloads.
When not: Without Control Tower, the same result is achieved with an AWS CloudTrail organization trail that writes to a bucket in a logging account. If the scenario is a single account, a trail to S3 is enough.
Often paired with
- AWS Service Catalog
- AWS IAM Identity Center