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
- Set up a landing zoneA multi-account environment containing the accounts, identities, and resources subject to governance..
- Control Tower configures accounts and services such as Organizations.
- 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)
Control behaviors and guidance
A ControlAn ongoing governance rule applied to an AWS environment. Tower control is an ongoing governance rule, also called a guardrail. Behavior describes how the rule works. Guidance describes whether AWS categorizes it as mandatory, strongly recommended, or elective.
How it works
- Choose the required outcome: block a prohibited action, report an existing violation, or evaluate a CloudFormation resource before provisioning. A CloudFormation hookA check that evaluates a CloudFormation resource before provisioning and can block a noncompliant resource. is a check on the provisioning operation.
- Preventive implementations include service control policies (SCPs), which limit member-account identity permissions; resource control policies (RCPs), which limit permissions on member-account resources; and declarative policies, which enforce service configuration.
- Enable the suitable control for the target OUA grouping of accounts within an AWS organization hierarchy.. Controls generally affect every account in that OU.
- Read the status using the control’s behavior. A detective violation reports noncompliance; a proactive failure stops the relevant CloudFormation provisioning.
- Check version and integration prerequisites. Landing zoneA multi-account environment containing the accounts, identities, and resources subject to governance. 4.0 can use ConfigBaseline for detective controls without the full AWSControlTowerBaseline.
Exam cues
- If the question says stop a prohibited action, think preventive control, because Organizations policies restrict the operation.
- If the question says report existing configuration violations, think detective control, because Config rules evaluate resource compliance.
- If the question says reject a noncompliant CloudFormation resource before provisioning, think proactive control, because a hook checks that provisioning path.
Remember
| Behavior | Implementation | Status or result |
|---|---|---|
| Preventive | Organizations SCPs, RCPs, or declarative policies | enforced / not enabled |
| Detective | Config rules | clear / in violation / not enabled |
| Proactive | CloudFormation hooks | PASS / FAIL / SKIP |
- Preventive controls are supported in all Regions; detective controls apply in Control Tower-supported Regions.
- Guidance and behavior are independent categories.
- Starting with landing zone 4.0, released in November 2025, mandatory controls are no longer applied by default.
- The management account root user and administrators have an exception to control restrictions.
- AWS-GR_REGION_DENY applies across the landing zone’s baselined OUs. CT.MULTISERVICE.PV.1 targets selected OUs. The home Region and certain global services are exempt from landing-zone Region deny.
Trap: A proactive control covers CloudFormation provisioning. It does not evaluate a resource created through a direct service API call.
Da documentação da AWS (18)
- A control is an ongoing governance rule, also called a guardrail.
- Controls generally apply at OU scope and affect all accounts in the selected OU.
- Preventive controls block actions that violate policy and use Organizations SCPs, RCPs, or declarative policies.
- Detective controls use Config rules to identify resource noncompliance and report it in the dashboard.
- Proactive controls use CloudFormation hooks to evaluate supported CloudFormation resources before provisioning and block noncompliant resources.
- Preventive status is enforced or not enabled, and preventive controls are supported in all AWS Regions.
- Detective status is clear, in violation, or not enabled; detective controls apply only in Control Tower-supported Regions.
- Proactive evaluation results are PASS, FAIL, or SKIP.
- Mandatory, strongly recommended, and elective are guidance categories independent of control behavior.
- Starting in landing zone 4.0, mandatory controls are not applied by default; deployment depends on enabled capabilities.
- Landing zone 4.0 was released in November 2025.
- The management account root user and administrators can perform actions that controls would otherwise deny.
- The landing-zone Region deny control cannot deny the home Region and exempts global services such as IAM and Organizations.
- AWS-GR_REGION_DENY governs the landing zone on OUs with AWSControlTowerBaseline, while CT.MULTISERVICE.PV.1 is configurable for selected OUs.
- Landing zone 4.0 introduces ConfigBaseline for detective controls without requiring AWSControlTowerBaseline.
- A service control policy (SCP) limits the permissions available to identities in member accounts and does not grant permissions.
- A resource control policy (RCP) limits permissions available on resources in member accounts and does not grant permissions.
- A declarative policy enforces the desired configuration of a supported AWS service across an organization.
Account Factory and enrollment
Account Factory standardizes AWS account creation and enrollment. A baselineA collection of resources and configurations applied to a governance target. is the set of resources and settings used for governance. Account Factory Customization (AFC) adds a blueprintA Service Catalog product defining the resources and configuration applied to an account by AFC., a Service Catalog product describing the resources and configuration an account should receive.
How it works
- For single-account provisioning, select an OUA grouping of accounts within an AWS organization hierarchy. with AWSControlTowerBaseline enabled. By default, provisioning IAM Identity Center users belong to AWSAccountFactory or the management group.
- In the standard Service Catalog workflow, a console or ProvisionProduct request calls ControlAn ongoing governance rule applied to an AWS environment. Tower. Control Tower first calls Organizations CreateAccount, applies the required resources and controls, and Service Catalog polls for the result.
- For manual enrollment, prepare AWSControlTowerExecution with AdministratorAccess and management-account trust. Use the same organization and a registered target OU, and resolve conflicting Config resources. Auto-enrollment and Register OU do not require you to precreate the role.
- For AFC, store one Service Catalog blueprint in a hub accountThe account that stores Service Catalog blueprint products for AFC. in the landing zoneA multi-account environment containing the accounts, identities, and resources subject to governance. home Region. Choose deployment in the home Region only or all governed Regions. AFC blueprint provisioning does not create an Account Factory provisioned product in the management account.
- For automation after provisioning, match successful lifecycle eventsAn event recording the completed result of a Control Tower operation. in EventBridge. A lifecycle event marks operation completion. An active CloudTrail trail with logging enabled is required for delivery. Handle both CreateManagedAccount and UpdateManagedAccount because retries can emit the latter.
- For custom CloudFormation resources and organizational policies, use Customizations for AWS Control Tower (CfCT). Its manifestA file describing the resources and targets in a CfCT configuration package., a file listing resources and targets, drives source retrieval, build validation, optional approval, service control policyAn organization policy that limits the permissions available to identities in member accounts without granting permissions. (SCP) deployment, resource control policyAn organization policy that limits permissions available on member-account resources without granting permissions. (RCP) deployment, and CloudFormation StackSets, which deploy related stacks across accounts and Regions. SCPs limit member-account identity permissions; RCPs limit access to member-account resources. Resource order in the manifest expresses dependencies. Target OUs need AWSControlTowerBaseline.
Exam cues
- If the question says create or enroll accounts consistently, think Account Factory, because it applies standardized account configuration.
- If the question says apply one Service Catalog blueprint from a hub account, think AFC, because it customizes accounts during provisioning or update.
- If the question says start automation only after account provisioning finishes, think a successful lifecycle event, because an initial CreateAccount request is not the completed workflow.
- If the question says automatically distribute custom templates and organizational policies to new accounts, think CfCT, because it integrates custom deployment with account lifecycle events.
Remember
| Requirement | Mechanism |
|---|---|
| Standard account provisioning | Account Factory |
| One catalog blueprint per account | AFC |
| Automation after operation completion | Lifecycle event and EventBridge rule |
| Custom templates, SCPs, and RCPs across accounts or OUs | CfCT |
- Single-account provisioning and CfCT target OUs require AWSControlTowerBaseline.
- AFC allows one blueprint per account and two Region choices: home only or all governed Regions.
- Lifecycle event state is Succeeded or Failed. Filter for the result your workflow requires.
- CfCT validates its configuration before policy and resource deployment; manual approval is optional.
Trap: The account can already exist when a provisioning retry begins. Listen for UpdateManagedAccount as well as CreateManagedAccount before deciding which automation to run.
An authorized user starts a standard Account Factory request through the console or Service Catalog ProvisionProduct API.
Service Catalog calls Control Tower and keeps polling it until the workflow finishes.
As its first step Control Tower calls Organizations
CreateAccount.Control Tower applies the required account configuration and controls, and Service Catalog reports the workflow result.
A lifecycle event records completion and success or failure. Delivery to EventBridge requires an active CloudTrail trail with logging enabled.
An EventBridge rule can trigger the next automation step after a successful lifecycle event.
Detalhes das caixas (5)
- Requester
An authorized user requests standard Account Factory provisioning through the console or Service Catalog API.
- Service Catalog
This standard flow uses a Service Catalog provisioned product. AFC blueprint provisioning has a different representation and does not create this product in the management account.
- Control Tower
Runs the workflow, then applies the baseline and the controls enabled on the target OU. The target OU must have the baseline enabled.
- Organizations
Control Tower calls
CreateAccountfirst. The new account lands in the chosen OU.- New account
Control Tower applies resources and controls required by the account and target OU configuration.
Read the configuration package and validate its manifest and templates.
Pause for approval if the optional approval stage is enabled.
Deploy the service control policies.
Deploy the resource control policies.
Deploy CloudFormation resources through StackSets in manifest order.
Da documentação da AWS (27)
- Account Factory provides configurable account templates to standardize account provisioning and enrollment.
- Single-account provisioning, update, and customization require a target OU with AWSControlTowerBaseline enabled.
- A baseline is a group of resources and settings used to establish governance on a target OU or account.
- By default, IAM Identity Center users who provision accounts belong to AWSAccountFactory or the management group.
- A standard Account Factory request can start in the Control Tower console, Service Catalog console, or Service Catalog ProvisionProduct API.
- Service Catalog calls Control Tower; Control Tower first calls Organizations CreateAccount, then applies blueprints and controls.
- Service Catalog polls the workflow and reports the completed provisioning result.
- Manual single-account enrollment requires AWSControlTowerExecution with AdministratorAccess and trust in the management account.
- An existing account must be in the same organization and enrolled into a registered OU; conflicting Config resources must be handled before enrollment.
- Precreating AWSControlTowerExecution is not required for auto-enrollment or enrollment through Register OU.
- Optional auto-enrollment applies destination OU baseline resources and controls when an account moves into a registered OU.
- AFC applies one Service Catalog blueprint product per account, stored in a hub account in the landing zone home Region.
- AFC supports home-Region-only or all-governed-Region deployment, not an arbitrary subset.
- With AFC blueprint customization, Control Tower does not create an Account Factory provisioned product in its management account.
- Lifecycle events record completed Control Tower operations with Succeeded or Failed state and are recorded as non-API CloudTrail service events.
- Lifecycle events are delivered to EventBridge; an active CloudTrail trail with logging enabled is required.
- EventBridge rules can trigger subsequent automation based on completed lifecycle events.
- A creation retry for an account that already exists can emit UpdateManagedAccount; automation should consider both CreateManagedAccount and UpdateManagedAccount.
- CfCT deploys CloudFormation templates, SCPs, and RCPs to accounts or OUs and integrates with lifecycle events to apply configured customizations to new Account Factory accounts.
- CfCT target OUs require AWSControlTowerBaseline.
- The CfCT configuration package contains a manifest, templates, and policy JSON; the manifest defines resources and deployment targets.
- CfCT pipeline order is source, build validation, optional manual approval, SCP, RCP, and CloudFormation resources.
- CfCT deploys CloudFormation resources through StackSets in manifest order; manifest order expresses dependencies.
- A service control policy (SCP) limits the permissions available to identities in member accounts and does not grant permissions.
- A resource control policy (RCP) limits permissions available on resources in member accounts and does not grant permissions.
- A declarative policy enforces the desired configuration of a supported AWS service across an organization.
- CloudFormation StackSets deploy related stacks across accounts and Regions.
Account Factory for Terraform
Account Factory for Terraform (AFT) turns Terraform account request files in Git into ControlAn ongoing governance rule applied to an AWS environment. Tower account provisioning and customization. This GitOpsA model in which account requests and configurations stored in Git drive automated workflows. model uses repository changes as workflow inputs. AFT runs in its own management account, separate from the Control Tower management account.
How it works
- Start with an existing Control Tower landing zoneA multi-account environment containing the accounts, identities, and resources subject to governance. and deploy AFT capabilities in the separate AFT management account.
- Commit and push an account request Terraform file to trigger the provisioning workflow.
- After provisioning and the provisioning framework, AFT applies global customizations and then account-specific customizations.
- Select optional feature flagsA configuration option that explicitly enables an optional AFT behavior. in the AFT deployment configuration. Each flag below is disabled by default.
- For retroactive customization of existing accounts, push the changed customization files and invoke the aft-invoke-customizations Step Functions workflow. A customization repository push alone does not start that rerun.
Exam cues
- If the question says provision governed accounts from Terraform files in Git, think AFT, because account request commits trigger its workflow.
- If the question says enroll AFT-provisioned accounts in Enterprise Support, think aft_feature_enterprise_support=true, because the option requests enrollment when the payer already has that plan.
- If the question says delete default VPCsThe virtual network AWS initially provides in a Region for a new account. in every provisioned account, think account customization logic, because AFT’s deletion flag applies only to its own management account. A VPC is a virtual network for AWS resources.
Remember
| Feature flag | Effect when true | Scope or prerequisite |
|---|---|---|
| aft_feature_cloudtrail_data_events | Organization trail for S3 and Lambda data events | All organization accounts; CloudTrail trusted access required |
| aft_feature_enterprise_support | Requests Enterprise Support enrollment | AFT-provisioned accounts; payer already enrolled |
| aft_feature_delete_default_vpcs_enabled | Removes default VPCs across Regions | AFT management account only |
- These feature flags are opt-in and disabled by default.
- Data-event logs use KMS encryption and log validation in an aws-aft-logs-* bucket in the logging account. Existing logging-account buckets are excluded from S3 data events.
- AFT customizes accounts; its pipeline is not intended for application workload deployment.
Trap: An AFT account request commit and a customization repository commit have different effects. Existing accounts need the explicit customization rerun workflow.
An account request commit triggers AFT provisioning.
After the provisioning framework, global customizations run.
Account-specific customizations run after global customizations.
Da documentação da AWS (14)
- AFT provides a Terraform pipeline for provisioning and customizing Control Tower accounts through account request files committed to Git.
- AFT requires an existing Control Tower landing zone and uses a separate AFT management account.
- The AFT management account is separate from the Control Tower management account and hosts AFT capabilities.
- AFT is intended for account provisioning and customization, not deployment of application workload resources.
- Global customizations run after the provisioning framework, followed by account-specific customizations.
- To customize existing AFT accounts retroactively, push the customization changes and invoke the aft-invoke-customizations Step Functions workflow; a customization repository push alone does not run it.
- CloudTrail data events, Enterprise Support enrollment, and default-VPC deletion are opt-in AFT features, disabled by default.
- Setting aft_feature_cloudtrail_data_events to true creates an organization trail for S3 and Lambda data events and requires CloudTrail trusted access.
- The AFT data-event option affects all organization accounts, including accounts not managed by AFT.
- The data-event option enables log validation and KMS-encrypted log delivery to an aws-aft-logs-* bucket in the logging account; existing logging-account buckets are excluded from S3 data events.
- Setting aft_feature_enterprise_support to true requests Enterprise Support enrollment for AFT-provisioned accounts; the payer account must already have Enterprise Support.
- Setting aft_feature_delete_default_vpcs_enabled to true deletes default VPCs only in the AFT management account across Regions, not in accounts AFT provisions or enrolls.
- Default-VPC deletion in accounts AFT provisions or enrolls requires custom deletion logic; Control Tower account creation separately deletes default VPCs in governed Regions but enrollment does not.
- A VPC is a virtual network for AWS resources.
Landing zone drift
DriftA mismatch between an expected governance configuration and the current managed environment. means the managed environment no longer matches the governance configuration ControlAn ongoing governance rule applied to an AWS environment. Tower expects. The repair depends on whether the mismatch affects a baselineA collection of resources and configurations applied to a governance target., inherited control, managed policy, or landing-zone resource.
How it works
- Control Tower monitors governance configuration and scans managed policies daily. Service control policies (SCPs) limit member-account identity permissions. Resource control policies (RCPs) limit access to member-account resources. Declarative policies enforce service configuration.
- Route notifications according to the landing-zone version. Starting with 4.0, released in November 2025, drift events go to EventBridge in the management account instead of SNS.
- Create an EventBridge rule matching source aws.controltower and detail-type Drift Detected. Configure an SNS or Lambda target to receive the event.
- Identify the affected object before choosing a repair. Baseline drift, leftover inherited controls, and landing-zone drift have different remediation paths.
- Consider auto-enrollment for future account moves. It applies destination OUA grouping of accounts within an AWS organization hierarchy. configurations, but does not repair leftover controls from moves that already happened.
Exam cues
- If the question says an old OU’s detective or proactive control remains after an account move, think DisableControl on the inherited control, because account updates and control resets do not remove that leftover inheritance.
- If the question says drift notifications disappeared after moving to landing zoneA multi-account environment containing the accounts, identities, and resources subject to governance. 4.0, think management-account EventBridge rule, because the notification destination changed.
- If the question says a managed SCPAn organization policy that limits the permissions available to identities in member accounts without granting permissions. was edited or detached, think policy drift and landing-zone update, because Control Tower expects to maintain that policy configuration.
Remember
| Drift type | Documented repair |
|---|---|
| Baseline inheritance mismatch | Update the account, re-register its OU, or ResetEnabledBaseline |
| Old inherited detective or proactive control | DisableControl with its EnabledControlIdentifier |
| Managed SCP changed or detached | Update the landing zone |
| Shared account moved | Update the landing zone |
| Control Tower trusted access disabled | Reset the landing zone |
- Preventive controls are not subject to the old-OU control inheritance driftA mismatch between an account configuration and the baseline or controls associated with its parent OU. described above.
- Older landing zones use SNS aggregation in the audit account; the drift guide excludes these SNS notifications when auto-enrollment is enabled.
- Missing required roles can make the landing zone unavailable. Drift can also block console enrollment.
- Governance drift detection does not find every resource change inside a baseline.
Trap: Enabling auto-enrollment prevents problems on future moves. It does not remove controls left behind by a previous move.
Control Tower sends a Drift Detected event to EventBridge in the management account.
A matching rule routes the event to the configured notification target.
Da documentação da AWS (19)
- Governance drift occurs when managed accounts, OUs, or policies change from the configuration expected by Control Tower.
- Baseline inheritance drift means an account baseline configuration differs from its parent OU; use an account update, OU re-registration, or ResetEnabledBaseline to repair it.
- With auto-enrollment off, moving accounts can leave detective and proactive controls inherited from the previous OU; preventive controls are not subject to this inheritance drift.
- Leftover inherited controls must be removed with DisableControl using their EnabledControlIdentifier; updating the account, re-registering the OU, or ResetEnabledControl does not remove them.
- Auto-enrollment applies destination OU configurations on future moves but does not remove leftover controls from earlier moves.
- Editing or detaching a Control Tower-managed SCP causes policy drift; updating the landing zone is a documented remediation.
- Control Tower scans managed SCPs, RCPs, and declarative policies daily.
- Landing zone 4.0 and later sends drift notifications to EventBridge in the management account instead of SNS.
- Landing zone 4.0 was released in November 2025.
- The documented drift event uses source aws.controltower and detail-type Drift Detected; a rule can target SNS or Lambda.
- Older landing zones use SNS drift notifications aggregated in the audit account; the drift guide notes these notifications are unavailable with auto-enrollment enabled.
- Missing required IAM roles can make the landing zone unavailable until role drift is resolved.
- A moved shared account is repaired by updating the landing zone.
- Disabling Control Tower trusted access interrupts Organizations change events and is remediated by resetting the landing zone.
- Landing zone drift can prevent the console Enroll account feature from working; use the documented alternate provisioning path while repairing drift.
- Control Tower governance drift detection does not detect arbitrary changes to resources contained in a baseline.
- A service control policy (SCP) limits the permissions available to identities in member accounts and does not grant permissions.
- A resource control policy (RCP) limits permissions available on resources in member accounts and does not grant permissions.
- A declarative policy enforces the desired configuration of a supported AWS service across an organization.
Landing zone integrations and Config scope
AWS ControlAn ongoing governance rule applied to an AWS environment. Tower orchestrates AWS Organizations, AWS Service Catalog, and AWS IAM Identity Center to set up and govern a multi-account landing zoneA multi-account environment containing the accounts, identities, and resources subject to governance.. Landing zone versions differ in their account structure and service integrations.
How it works
- In versions 3.3 and earlier, the Security organizational unitA grouping of accounts within an AWS organization hierarchy. (OU) contains the shared Log Archive and Audit accounts. Version 4.0 no longer requires a Security OU and makes AWS Config, AWS CloudTrail, SecurityRoles, and AWS Backup integrations optional.
- For centralized CloudTrail logging, create or select a CloudTrail administrator account, formerly Log Archive. When Config integration is enabled, create or select a Config aggregatorA resource that collects configuration data across accounts. account, formerly Audit.
- In version 4.0, CloudTrail logs remain in the logging account, while Config logs use a dedicated bucket in the Config aggregator account. A service-linked Config aggregator collects configuration data across accounts.
- Landing-zone Config integration configures service integration accounts. To configure member accounts, enable the Config baselineA collection of resources and configurations applied to a governance target. on their managed OU.
Exam cues
- If the question says a team needs its own organizational structure, think landing zone 4.0, because it does not require a Security OU.
- If the question says to locate CloudTrail logs and Config data, think the CloudTrail administrator and Config aggregator accounts, because version 4.0 uses dedicated Config log storage and an aggregator.
- If the question says member accounts lack Config recorders after landing-zone integration is enabled, think the Config baseline on their managed OU, because the landing-zone integration configures service integration accounts.
Remember
- Versions 3.3 and earlier place Log Archive and Audit in a Security OU.
- Version 4.0 makes the listed service integrations optional and does not require a Security OU.
- The Config aggregator collects configuration data across accounts; Config logs and CloudTrail logs use separate buckets in version 4.0.
Trap: Enabling landing-zone Config integration alone does not configure member accounts. Enable the Config baseline on their managed OU as well.
Da documentação da AWS (8)
- Control Tower orchestrates AWS services including Organizations, Service Catalog, and IAM Identity Center to set up and govern a multi-account landing zone.
- Landing zone 3.3 and earlier use a Security OU containing the shared Log Archive and Audit accounts.
- Landing zone 4.0 allows optional Config, CloudTrail, SecurityRoles, and Backup integrations and no longer requires a Security OU.
- The CloudTrail administrator account, formerly Log Archive, is created or selected for centralized CloudTrail logging.
- The Config aggregator account, formerly Audit, is created or selected when Config integration is enabled.
- In landing zone 4.0, Config log files use a dedicated bucket in the Config aggregator account; CloudTrail logs remain in the logging account.
- Landing zone 4.0 uses a service-linked Config aggregator, which collects configuration data across accounts.
- In landing zone 4.0, landing-zone Config integration configures service integration accounts; member accounts require the Config baseline enabled on their managed OU.
Flashcards
Nada para revisar aqui agora. Escolha outros tópicos ou outro filtro.
·
Todos os 35 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.
Which AWS Control Tower control behavior should prevent actions, find existing violations, or check CloudFormation resources before provisioning?
Preventive uses Organizations policies; detective uses Config rules; proactive uses CloudFormation hooks.
What are AWS Control Tower control guidance categories, and do they determine the implementation?
Mandatory, strongly recommended, and elective. Guidance is independent of preventive, detective, or proactive behavior. In landing zone 4.0, mandatory controls are not applied by default.
An AWS Control Tower proactive control is enabled, but a user directly calls a service API to create a noncompliant resource. Does that proactive control evaluate the request?
No. Proactive controls evaluate resources provisioned through CloudFormation hooks. Use suitable preventive controls or detective rules for other provisioning paths.
How does AWS Region coverage differ for AWS Control Tower preventive and detective controls?
Preventive controls are supported in all Regions. Detective controls apply in Control Tower-supported Regions. Region deny is a separate preventive restriction with home-Region and global-service exceptions.
Can the root user or administrators in the AWS Control Tower management account perform actions that controls otherwise deny?
Yes. The management account has a documented exception intended to keep it usable.
A governance team needs AWS Control Tower to stop noncompliant CloudFormation provisioning and identify existing resource violations. Which behaviors should it combine?
Proactive controls for CloudFormation provisioning and detective controls for existing violations.
An AWS Control Tower administrator wants Region restrictions on selected OUs rather than the entire landing zone. Which control fits?
Use the configurable OU Region deny control CT.MULTISERVICE.PV.1. AWS-GR_REGION_DENY is the separate landing-zone control.
What status values should an AWS Control Tower operator expect for preventive, detective, and proactive controls?
Preventive: enforced or not enabled. Detective: clear, in violation, or not enabled. Proactive: PASS, FAIL, or SKIP.
What does AWS Control Tower Account Factory do, and which OU prerequisite applies to single-account provisioning?
It standardizes account creation and enrollment from configurable templates. The target OU must have AWSControlTowerBaseline enabled. By default, provisioning Identity Center users belong to AWSAccountFactory or the management group.
An administrator must manually enroll an existing AWS account into AWS Control Tower. What must be prepared?
Use an account in the same organization and a registered target OU. Add AWSControlTowerExecution with AdministratorAccess and management-account trust, and resolve conflicting Config resources. Precreating the role is not required for auto-enrollment or Register OU.
A team wants a standard AWS Control Tower account customized with a Service Catalog blueprint from a central account. Which feature fits?
Account Factory Customization (AFC). Store one blueprint product in a hub account in the landing zone home Region.
An AWS Control Tower AFC team wants a different blueprint deployment subset for each account. What Region choices does AFC support?
Home Region only or all governed Regions. Arbitrary Region subsets are not supported.
A team must trigger automation after AWS Control Tower finishes provisioning an account. What event path should it use?
Use an EventBridge rule matching successful lifecycle completion. Enable logging on an active CloudTrail trail and handle both CreateManagedAccount and UpdateManagedAccount for retries.
New AWS Control Tower accounts must receive custom CloudFormation resources and organizational policies automatically. Which extension fits?
Customizations for AWS Control Tower (CfCT). It uses configured templates and policies with lifecycle integration; target OUs require AWSControlTowerBaseline.
How does an AWS Control Tower CfCT administrator express a dependency between custom CloudFormation resources?
Place the resources in dependency order in the manifest. CfCT deploys them through StackSets in that order.
An AWS Control Tower AFC account was provisioned with a blueprint, but no Account Factory provisioned product appears in the management account. Is this expected?
Yes. Blueprint customization does not create that Account Factory provisioned product in the management account.
A team needs AWS Control Tower accounts provisioned from Terraform account requests committed to Git. What should it use?
Account Factory for Terraform (AFT). It runs account provisioning and customization pipelines in a separate AFT management account and requires an existing landing zone.
A team needs Enterprise Support on accounts provisioned by AWS Control Tower AFT. Which setting and prerequisite apply?
Set aft_feature_enterprise_support to true in the AFT deployment configuration. The payer account must already be enrolled in Enterprise Support.
Does enabling aft_feature_delete_default_vpcs_enabled remove default VPCs from every account AWS Control Tower AFT provisions?
No. The flag affects only the AFT management account. Use account customization logic for other accounts.
Which AWS Control Tower AFT flag enables organization-wide S3 and Lambda data-event logging, and is its scope limited to AFT-managed accounts?
Set aft_feature_cloudtrail_data_events to true after enabling CloudTrail trusted access. It affects all accounts in the organization.
An AWS Control Tower AFT team pushes new global customizations but existing accounts do not change. What must it do?
Invoke the aft-invoke-customizations Step Functions workflow for the selected accounts after pushing the changes.
In what order does AWS Control Tower AFT apply global and account-specific customizations?
After the provisioning framework, apply global customizations and then account-specific customizations.
An AWS Control Tower account was moved between OUs with auto-enrollment disabled. Detective controls from the old OU remain. How are they removed?
Disable the leftover inherited controls using DisableControl and their EnabledControlIdentifier. Account updates, OU re-registration, and ResetEnabledControl do not remove these old inherited controls. Preventive controls are not subject to this inheritance drift.
What can cause AWS Control Tower governance drift, and how should operators choose remediation?
Changes to managed OUs, accounts, or policies can cause drift. Repair the affected object: reset a baseline for baseline drift, disable leftover inherited controls after a move, or update/reset the landing zone for the documented landing-zone drift type.
An AWS Control Tower landing zone 4.0 team receives no drift alerts on its old audit-account SNS subscription. What should it configure?
Create an EventBridge rule in the management account for source aws.controltower and detail-type Drift Detected, then route it to SNS or Lambda.
Does enabling AWS Control Tower auto-enrollment remove inherited controls left over from an earlier account move?
No. It handles future moves. Remove earlier leftover controls explicitly with DisableControl.
An operator detached an AWS Control Tower-managed SCP from an OU. Which repair path is documented?
Update the landing zone to restore its managed policy configuration. Managed policies are scanned daily for drift.
Does AWS Control Tower governance drift detection identify every resource edit inside an account baseline?
No. It does not detect arbitrary resource drift inside a baseline.
What environment does AWS Control Tower set up, and how does its landing zone 4.0 structure differ from earlier versions?
A governed multi-account landing zone. Versions through 3.3 use Log Archive and Audit accounts in a Security OU; 4.0 makes service integrations optional and removes the required Security OU structure.
What are AWS Control Tower's CloudTrail administrator and Config aggregator accounts for?
The CloudTrail administrator account centralizes CloudTrail logs. The Config aggregator account supports Config integration and aggregation; in 4.0 it has its own Config log bucket. Earlier names were Log Archive and Audit.
A team enables AWS Config integration for an AWS Control Tower 4.0 landing zone but member accounts lack Config recorders. What additional configuration is needed?
Enable the Config baseline on the managed member-account OUs. The landing-zone integration alone configures only service integration accounts.