Easy ReviewSAA-C03
Design Secure Architectures4

Control Tower

Govern a multi-account landing zone with account provisioning, controls, customizations, and drift management.

Este conteúdo de estudo ainda não foi traduzido, então aparece em inglês. Ajude a traduzir

AWS Control Tower coordinates account provisioning and governance across an organization. Landing-zone version and enabled service integrations determine the account structure, controls, and drift notification path.

Control Tower basics

AWS ControlAn ongoing governance rule applied to an AWS environment. Tower builds and governs a multi-account environment using AWS best practices.

How it works

  1. Set up a landing zoneA multi-account environment containing the accounts, identities, and resources subject to governance..
  2. Control Tower configures accounts and services such as Organizations.
  3. Controls keep accounts within the rules.

Exam cues

  • If the question says set up a governed multi-account environment quickly, think Control Tower.

Remember

  • Prescriptive multi-account setup.

Trap: Control Tower builds on AWS Organizations; it does not replace it.

Da documentação da AWS (2)
  • AWS Control Tower sets up and governs a multi-account AWS environment following prescriptive best practices, orchestrating other AWS services.
  • AWS Control Tower applies controls (guardrails), which are preventive, detective or proactive rules, to the accounts in its landing zone.

Landing zone and shared accounts

AWS ControlAn ongoing governance rule applied to an AWS environment. Tower sets up and governs a multi-account landing zoneA multi-account environment containing the accounts, identities, and resources subject to governance.. A landing zone is the environment containing the accounts, identities, and resources that follow your governance rules. An organizational unitA grouping of accounts within an AWS organization hierarchy. (OU) groups accounts under the organization hierarchy.

How it works

  1. Use the management account to launch and administer Control Tower.
  2. Choose service integrations and the accounts that host their central resources. Service integration accounts share a parent OU; this placement rule excludes the management account.
  3. Apply controls to landing zone accounts. Controls can be preventive, detective, or proactive rules.

Exam cues

  • If the question says apply governance controls across accounts, think Control Tower landing zone, because its controls apply to landing zone accounts.
  • If the question says keep an existing organizational structure and choose integrations, think landing zone 4.0, because integrations are optional and a Security OU is no longer required.
  • If the question says change the home Region after setup, think choose it during setup, because it cannot be changed later.

Remember

Earlier default name Version 4.0 default name
Log Archive CloudTrail Administrator
Audit AggregatorA resource that collects configuration data across accounts. account
  • Landing zone 4.0 was released in November 2025. It makes service integrations optional and removes the mandatory Security OU structure.
  • Account names can be customized. The home Region cannot change after setup.

Trap: Do not assume every landing zone always creates the same shared-account structure. The version and enabled service integrations determine the configuration.

Landing zone 4.0 optional integration accounts
Integration OUCloudTrail enabledConfig enabledManagementControl TowerLogging accountCloudTrail logsConfig accountConfig data + aggregator
Da documentação da AWS (9)
  • A landing zone contains the organizational units, accounts, identities, and resources subject to governance.
  • An organizational unit groups accounts within the organization hierarchy.
  • The management account launches and administers Control Tower.
  • Landing zone 4.0 was released in November 2025.
  • Landing zone 4.0 allows optional Config, CloudTrail, SecurityRoles, and Backup integrations and no longer requires a Security OU.
  • Accounts configured for service integrations must share the same parent OU; the management account is exempt from this placement rule.
  • The home Region cannot be changed after landing zone setup.
  • Shared account default names changed with version 4.0 from Log Archive and Audit to CloudTrail Administrator and Aggregator account; names can be customized.
  • A baseline is a group of resources and configurations applied to a target.

Flashcards

toque para virar
Resposta

·

Todos os 4 flashcards em lista

A company wants a ready, best-practice multi-account setup with governance from day one. Which service fits?

AWS Control Tower.

Which AWS service sets up a multi-account landing zone and applies preventive and detective guardrails to its accounts?

AWS Control Tower.

A team wants AWS Control Tower landing zone 4.0 controls while keeping its own logging and organizational structure. Must it use every service integration and a mandatory Security OU?

No. Version 4.0 makes service integrations optional and lets customers define their organizational structure.

Can an AWS Control Tower administrator change the home Region after landing zone setup?

No. The home Region is fixed after setup.

Você concluiu todos os tópicos da SAA-C03!

Seu badge ficou dourado. Próximo passo: agendar a prova na AWS. Depois de passar, adicione-se ao Quem passou.

Compartilhar

Conte que você concluiu esta certificação

Concluí todos os tópicos da AWS Certified Solutions Architect - Associate (SAA-C03) no Easy Review. Venha estudar também!