A Control Tower Landing Zone with Governed Regions, Logging Kept a Year, and Controls per Unit

A Control Tower landing zone from a manifest the module writes: the governed regions (the only usable ones), the Security and Sandbox units, centralized logging in the log archive account you name kept a year (access logs ten) under your KMS key (the AWS-managed key by name), the audit account, Identity Center access, and the controls you map to organizational units.

This is the operations reference: version drift, dependants and neighbours. For what the module provisions, its inputs and outputs, and how to buy it, see the catalogue entry.

terraformAWSLanding Zones & Foundationsv1.0.0static-validated

Provider drift

This artifact declares no Terraform provider requirements, so there is nothing to drift. Provider freshness applies to Terraform and OpenTofu modules.

What depends on this

No reference architecture names this module, so changing it affects only configurations that reference it directly.

Nearest alternatives

Same cloud, same category. These are what you would weigh against it without changing provider.

A Budget Somebody Actually Hears About Organizations, OUs and Service Control Policies

The same job on other clouds

Landing Zone on other providers. Useful when the cloud is still open, or when you are pricing a second one. How far a comparison like that can be trusted is covered in comparing clouds.

A Resource Directory Where Policy Can Attach and Accounts Can Be DeletedAlibaba Cloud An Organization That Says It Is a Billing Hierarchy, Not a Policy OneTencent Cloud An Organization Whose Policy Types Are Enabled Before a Policy Needs ThemHuawei Cloud Azure Landing Zone CoreAzure GCP Project FactoryGoogle Cloud

Installing it

module "aws_control_tower" {
  source  = "www.iac-bazaar.com/iac-bazaar/aws-control-tower/aws"
  version = "1.0.0"
}

A registry token is required for the download itself. Installing through the registry protocol has the two credential steps.