If you're evaluating AWS Control Tower alternatives, you've probably already felt the frustration. A 2023 HackerNews comment repeats a line that has followed the service for years: "friends don't let friends use Control Tower."
I've built production CDK landing zones for enterprise clients at Towards the Cloud and hit the same walls: guardrails you can't customize through code, account vending through Service Catalog forms, and a console that fights you every time you want to treat infrastructure as software.
Many "alternatives" roundups skip CfCT and AFT and conflate AWS-native governance tools with cross-cloud CSPM products like Wiz and Prisma Cloud. I compare all five here: AWS CDK Landing Zone (my top recommendation), LZA, CfCT, AFT, and OrgFormation, with code examples, real operational constraints, and a decision framework.
If you would rather not build the replacement yourself, our AWS CDK Landing Zone is a multi-account AWS foundation built with AWS CDK and deployed in about a week, with CIS AWS Foundations Benchmark controls from day one and every line of CDK in your repository.
Excalidraw diagram loading.
If you're unfamiliar with the foundation, start with the difference between a landing zone and Control Tower or review AWS Control Tower vs AWS Organizations for context on how they relate.
Why Teams Leave AWS Control Tower
The limitations that actually cause teams to look elsewhere are concrete, not vague.
The ClickOps Management Problem
Control Tower's default workflow is the console, not a pull request. Controls are switched on in the console, and Account Factory runs through Service Catalog forms, not Terraform modules. Its APIs and CloudFormation resources can automate this, but you build and maintain that automation yourself. The result is a ClickOps vs IaC problem: your workload infrastructure is version-controlled in CI/CD, but the foundation it runs on is managed by point-and-click.
SCP Slot Exhaustion and the Guardrail Drift Problem
In May 2026, AWS doubled the Service Control Policy quota: Organizations now allows 10 SCPs per node and 10,240 characters per SCP, and Control Tower's landing zone documents the same limit of ten SCPs per OU. That headroom helps, but the slots are shared. Control Tower's own managed guardrails consume some of them, so layering custom compliance SCPs (blocking regions, restricting S3 public access, enforcing MFA) on top still runs into the ceiling on a heavily governed OU.
Guardrail drift is a separate issue. In August 2025, AWS removed two drift types: a control's SCP attached to another OU or to a member account through Organizations no longer counts as drift. But other changes made outside Control Tower still cause drift, and reconciling it means resetting or updating the landing zone through Control Tower's console or API rather than running cdk deploy.
Account Vending Latency via Service Catalog
Control Tower's Account Factory provisions accounts through Service Catalog, which isn't supported in seven Control Tower Regions: Calgary, Malaysia, Thailand, Mexico Central, New Zealand, Taipei, and the AWS European Sovereign Cloud. Everywhere else, each Account Factory account is a Service Catalog provisioning request rather than a step in your own pipeline, unless you turn on automatic enrollment and create accounts through Organizations. For teams running a multi-account strategy at scale, every step outside your own pipeline is a bottleneck.
What Control Tower Still Does Well
Control Tower landing zone 4.0 (November 17, 2025) made real improvements: Config, CloudTrail, and Backup integrations are now optional, the Security OU is no longer required, and a "Controls-Only" experience lets you adopt managed controls without a full landing zone baseline. Control Catalog now holds 750+ managed controls, mapped to frameworks including FedRAMP, NIST CSF, PCI DSS, and SOC 2. For teams that want a managed service with built-in compliance coverage and don't need deep IaC customization, 4.0 is a meaningfully better product than the versions before it.
Two Categories of "Alternatives": Only One Applies Here
Some software review sites list Wiz, Prisma Cloud, and Microsoft Defender for Cloud as Control Tower alternatives. They're not. They're Cloud Security Posture Management (CSPM) tools that govern security posture across multiple cloud providers. They don't replace Control Tower's account vending, OU governance, or SCP enforcement.
The five tools in this post are all AWS-native, operating within AWS Organizations to manage accounts, OUs, SCPs, and baseline resources. A CDK Landing Zone or LZA deployment can have Wiz layered on top. The AWS Deployment Framework is left out on purpose: it is a CodePipeline delivery framework that also bootstraps accounts, so it works better as a pipeline layer than as a foundation.
All Five AWS-Native Alternatives at a Glance
The rows that matter most for your first decision are Control Tower Dependency and IaC Framework. Those two rows will eliminate at least two options immediately.
Side-by-Side Comparison Matrix
| Dimension | CDK Landing Zone (Recommended) | LZA | CfCT | AFT | OrgFormation |
|---|---|---|---|---|---|
| CT Dependency | None (CT-independent) | Optional (CT recommended) | Required | Required | None (CT-independent) |
| IaC Framework | Native CDK (TypeScript) | Config-driven YAML (CDK under the hood) | CloudFormation + SCPs via CodePipeline | Terraform (GitOps) | CloudFormation YAML (custom CLI) |
| Diff / Preview | cdk diff | Opt-in Review stage (cdk diff + approval) | None (optional approval stage) | Opt-in plan-only runs (since 1.22.0) | create-change-set (opt-in) |
| Account Creation | Yes, CDK + Organizations API | Yes, via Organizations API + LZA pipeline | No (uses CT Account Factory) | Yes, via CT Account Factory or Organizations API (GitOps) | Yes, via Organizations API |
| GitOps Model | Yes (any Git + CDK CI/CD) | Partial (config repo + pipeline release) | No | Yes (commit to aft-account-request repo) | Optional (init-pipeline) |
| Compliance Frameworks | Customer-defined | FedRAMP, CMMC, NIST 800-171, HIPAA, DoD IL4/IL5 | Customer-defined | Customer-defined | Customer-defined |
| Deployment Time | 5-10 min (StackSets, observed) | Core pipeline (10 named stages) | CodePipeline run | FIFO pipeline (variable; default 5 concurrent) | CLI or pipeline run |
| Baseline Cost | Security services you enable (CloudFormation is free) | ~$430/mo sandbox | ~$3/mo | AFT infrastructure charges | Free (open source) |
| Networking | Customer-defined | Full (VPC, TGW, Network Firewall) | None | None | Customer-defined |
| Security Service Orchestration | Security Hub, GuardDuty, Inspector, Macie | GuardDuty, Security Hub, Macie, Detective | None | Via customizations | Customer-defined |
| Support Model | Towards the Cloud + AWS Support | GitHub Issues + AWS Support | GitHub Issues + AWS Support | GitHub Issues + AWS Support | Community only |
How to Read This Table
Control Tower Dependency is the first filter. Want to escape Control Tower entirely? Cross AFT and CfCT off immediately: both require an existing landing zone. CDK Landing Zone and OrgFormation are fully CT-independent. LZA can run on AWS Organizations alone, though AWS recommends Control Tower as its foundation.
Diff/preview support separates tools that show what will change from those that execute blind. CDK Landing Zone puts cdk diff in the deploy path. AFT applies with --auto-approve by default, but since version 1.22.0 it can run customizations in plan-only mode. That mode, OrgFormation's change sets, and LZA's Review stage all exist but are opt-in, so a preview only happens if you turn it on. CfCT has an optional approval stage but no diff. For SCP and OU changes, that's a meaningful operational risk.
Compliance frameworks built-in determines whether you need FedRAMP, CMMC, or HIPAA alignment out of the box (LZA only) or build your own governance controls (everyone else). A federal compliance deadline may make this row the deciding factor.
Alternative 1: AWS CDK Landing Zone (Custom IaC Pattern, Recommended)
The AWS CDK Landing Zone is not an AWS-managed service. It's a CDK application in a repository you own: native AWS CDK manages Organizations resources, and CloudFormation StackSets handle cross-account deployments. The reusable foundation ships as versioned packages that we maintain, while your stacks, StackSet targeting, and configuration live in your own starter repo. Upgrades are two pinned version bumps you schedule, and cdk diff shows what they change before anything deploys, so no upstream release schedule decides when your landing zone changes. This is also distinct from the original "AWS Landing Zone Solution" (now in long-term support) and from LZA (launched in 2022). It's the same pattern I use at Towards the Cloud for production enterprise deployments.
What CDK Landing Zone Actually Is (and Is Not)
Two components. First, CDK manages AWS Organizations resources directly (OUs, accounts, and Service Control Policies) using programming languages instead of console clicks or YAML. Second, CloudFormation StackSets deploy baseline resources across all accounts in those OUs automatically. When an account joins a targeted OU, StackSets fire. When you need new behavior, you write code and run cdk deploy.
Native CDK for Organizations Management
import * as cdk from 'aws-cdk-lib';
import * as organizations from 'aws-cdk-lib/aws-organizations';
// Create organizational units
const productionOu = new organizations.CfnOrganizationalUnit(this, 'ProductionOU', {
name: 'Production',
parentId: root.id,
});
const developmentOu = new organizations.CfnOrganizationalUnit(this, 'DevelopmentOU', {
name: 'Development',
parentId: root.id,
});
// Create accounts in specific OUs
new organizations.CfnAccount(this, 'ProductionAccount', {
accountName: 'prod-workload-01',
email: 'prod-workload-01@example.com',
parentIds: [productionOu.attrId],
});
Version-controlled, code-reviewed, testable. Need 50 accounts following a naming convention? Write a loop. With LZA, copy-paste 50 YAML entries. You can implement production-ready SCP examples using the same CDK patterns.
CloudFormation StackSets: Automatic Account Provisioning
import * as stacksets from 'aws-cdk-lib/aws-cloudformation';
new stacksets.CfnStackSet(this, 'BaselineStackSet', {
stackSetName: 'account-baseline',
permissionModel: 'SERVICE_MANAGED',
capabilities: ['CAPABILITY_NAMED_IAM'],
autoDeployment: {
enabled: true,
retainStacksOnAccountRemoval: false,
},
stackInstancesGroup: [{
deploymentTargets: {
organizationalUnitIds: [productionOu.attrId, developmentOu.attrId],
},
regions: ['us-east-1', 'eu-west-1'],
}],
templateBody: baselineTemplate.templateJson,
});
Add an account to an OU, it gets the baseline automatically. Move an account between OUs, StackSets update accordingly.
Deployment Speed: Parallel StackSets vs. a 10-Stage Pipeline
In our deployments, baseline StackSets roll out to accounts and Regions in parallel and finish in 5-10 minutes. LZA routes every configuration change through a Core pipeline with 10 named stages. That difference compounds during incident response and governance iteration.
Production-Ready StackSet Catalog
A full CDK Landing Zone ships 8 baseline StackSets in two groups. Four self-managed foundation StackSets run in dedicated accounts: the organization CloudTrail trail with encrypted log buckets in an observability account, secure defaults for the management account, the security services (Security Hub, GuardDuty, Inspector, Macie, and IAM Access Analyzer) from the security account, and cost tooling in a FinOps account. Four service-managed member-account StackSets deploy automatically when an account joins a targeted OU: account security defaults, Resource Explorer, CDK bootstrap, and Service Quotas.
Beyond StackSets: SCPs, OIDC, and Lifecycle Automation
Around the StackSets, the organization stack ships five baseline SCPs as code (the service control policy reference lists them), a GitHub Actions OIDC role so the pipeline deploys without long-lived access keys, and alternate contacts on every account. Moving an account to the Suspended OU locks it down; accounts in its nested close-account OU are closed automatically. Daily CloudFormation drift detection runs in both the management and landing zone accounts.
The Build Cost: What You Give Up for Full Control
CDK Landing Zone trades initial effort for long-term flexibility. If you build the pattern yourself and need a compliance-ready foundation by next quarter, LZA may be more practical. For teams that want the benefits without the build time, check the public roadmap or explore our CDK Landing Zone service.
When CDK Landing Zone Is the Right Choice
CDK Landing Zone fits when your team has strong AWS expertise, prefers programming languages over YAML, and prioritizes long-term flexibility. An account the Towards the Cloud implementation provisions scores 100% on the CIS AWS Foundations Benchmark and 96% on AWS Foundational Security Best Practices in Security Hub. The Control Tower vs CDK landing zone comparison shows how that baseline is built and where Control Tower's coverage depends on which optional controls you enable. It's a natural fit for teams building toward SOC 2 compliance because every control maps to an auditable CDK construct.
The two scenarios where it's not the right choice: you want AWS to maintain a pre-mapped compliance baseline for FedRAMP, CMMC, or DoD IL4/IL5 workloads (that's LZA's job), or you're already on Control Tower and just need a lightweight customization layer rather than a full IaC foundation.
Next step
Want the CDK Landing Zone Without Building It Yourself?
Alternative 2: AWS Landing Zone Accelerator (LZA)
Landing Zone Accelerator (LZA) is AWS's open-source CDK-based solution for highly regulated workloads. AWS's official position is that you deploy AWS Control Tower as your foundational landing zone and then add LZA capabilities on top as needed.
Framework-Heavy Despite CDK Foundation
LZA uses CDK internally but surfaces a configuration-driven interface. You maintain YAML files, and when they change, you release the CodePipeline, which runs through 10 named stages. The trade-off: broad coverage across 35+ AWS services without writing custom CDK, but you're a configuration consumer, not a code owner.
The Eight Configuration Files
LZA splits its configuration across six required YAML files (accounts, global, IAM, network, organization, and security) plus optional customizations and replacements files, and every account is declared as its own YAML entry. The LZA vs CDK landing zone comparison walks through those files, who owns them, and how LZA upgrades land.
LZA Standalone vs. LZA on Control Tower
AWS documents an Organizations-only installation but recommends Control Tower as the foundation, including in the AWS GovCloud (US) Regions, so in most deployments LZA is the enhancement layer rather than a standalone replacement.
Real-World Operational Costs: Baseline Spend
AWS's sample estimate for a non-production sandbox running the LZA sample configuration with Control Tower in us-east-1 comes to approximately $430/month with no workload activity, most of it VPC networking and CloudTrail. For small teams, that floor is worth knowing before committing to the architecture.
LZA MCP Server: AI-Assisted Configuration (March 2026)
AWS launched an open-source LZA MCP Server in March 2026 with 20 specialized tools covering document search, configuration management, pipeline monitoring, and failure diagnostics. It's compatible with Kiro, Amazon Q Developer, and Claude Code.
Locked Out of CDK Constructs: The Fork Dilemma
LZA's CDK constructs are not yours to modify. When something doesn't behave the way you need, you either file a GitHub issue and wait, or fork the repository and maintain your own version of upstream changes.
Built-In Compliance Frameworks: FedRAMP, CMMC, HIPAA, and DoD IL4/IL5
LZA's pre-built compliance coverage is where it genuinely differentiates. AWS lists FedRAMP Moderate and High, CMMC, NIST SP 800-171, HIPAA, ISO/IEC 27001, and C5, and in the AWS GovCloud (US) Regions the solution follows the DISA Cloud Computing SRG for IL4 and IL5 workloads. It also automates delegated administrator setup for Security Hub, GuardDuty, Macie, Detective, and Audit Manager. For federal agencies or healthcare organizations with an ATO deadline, LZA compresses months of custom implementation work.
When LZA Earns Its Complexity
LZA is the right choice when you need pre-built compliance frameworks for federal, healthcare, or financial services workloads with a deadline, including DoD IL4/IL5 workloads in the AWS GovCloud (US) Regions. Small teams without a federal compliance requirement will find the $430/month sandbox cost and 8-YAML configuration surface area are overhead that CDK Landing Zone avoids.
Alternative 3: Customizations for AWS Control Tower (CfCT)
CfCT is a free, open-source AWS Solutions package that extends a Control Tower landing zone with CloudFormation templates and SCPs, delivered through a CodePipeline that triggers automatically when Control Tower creates new accounts. Lighter than LZA by design: no networking, no security service toggles, no pre-built compliance frameworks. AWS lists CfCT alongside AFT and LZA as ways to customize Control Tower outside the console.
What CfCT Does: SCPs and StackSets via CodePipeline
When Account Factory creates a new account, Control Tower emits a lifecycle event. CfCT's EventBridge rule catches it, triggers a CodePipeline, and deploys your custom CloudFormation templates and SCPs to the new account and its OU:
region: us-east-1
version: 2021-03-15
resources:
- name: baseline-iam-roles
resource_file: templates/baseline-iam-roles.template
deploy_method: stack_set
deployment_targets:
organizational_units:
- Workloads:Production
- Workloads:Development
- name: deny-root-access-scp
resource_file: policies/deny-root-access.json
deploy_method: scp
deployment_targets:
organizational_units:
- Workloads
Cost is approximately $3/month for 100 small pipeline builds, among the lowest of the five options.
What CfCT Cannot Do (No Account Creation, No OU Management, No Security Service Toggles)
CfCT is a customization layer on top of Control Tower, not a replacement. Account creation still runs through Control Tower's Account Factory. OU structure is still managed through the Control Tower console. Security service enablement (GuardDuty, Security Hub, Macie) is not orchestrated by CfCT. Its StackSets deploy through Control Tower's AWSControlTowerExecution role, so target accounts must be enrolled in Control Tower.
In December 2024, CfCT gained GitHub as a source (previously CodeCommit or S3 only) and Resource Control Policy (RCP) support. Like AFT, it's unavailable in 10 Regions, including Zurich, Spain, Calgary, Melbourne, and the AWS European Sovereign Cloud, so confirm your home Region before planning around it.
CfCT vs LZA: The Capability Gap in Plain Terms
Think of CfCT as the stepping stone and LZA as the full escalation path. CfCT deploys SCPs and CloudFormation, the governance basics. LZA adds VPC and Transit Gateway networking, configuration across 35+ AWS services, and pre-configured compliance frameworks. If you need baseline SCPs applied consistently to every new account, CfCT is right. If you need FedRAMP or CMMC alignment and hub-and-spoke networking with Network Firewall, LZA is where you need to be. CfCT is also the right stepping stone before LZA: start lightweight, then evaluate whether LZA's additional capabilities justify its cost as your requirements grow.
When CfCT Is the Right Starting Point
CfCT makes sense when you're already on Control Tower and want a lightweight, low-cost customization layer. It's a good fit for small platform engineering teams (1-2 people) who need consistent baseline configuration on new accounts but don't have a federal compliance deadline driving them toward LZA. CfCT is built for teams that are staying on Control Tower and want lightweight customization. AFT is for Terraform shops with the same starting point.
Alternative 4: Account Factory for Terraform (AFT)
Account Factory for Terraform (AFT) is an AWS-published Terraform module (github.com/aws-ia/terraform-aws-control_tower_account_factory, v1.24.0, November 2026, min Terraform 1.6.1) that brings GitOps-style account provisioning to a Control Tower landing zone. Version 1.24.0 added an optional vending method that creates accounts through the Organizations API and lets Control Tower auto-enroll them, instead of going through Service Catalog. It needs landing zone 3.1 or later with auto-enrollment turned on.
AFT's GitOps Terraform Pipeline Model
Commit a Terraform account request file and the pipeline queues it in FIFO order at a default concurrency of 5:
module "account-request" {
source = "./modules/aft-account-request"
control_tower_parameters = {
AccountEmail = "prod-workload-01@example.com"
AccountName = "prod-workload-01"
ManagedOrganizationalUnit = "Production (ou-abcd-12345678)"
SSOUserEmail = "admin@example.com"
SSOUserFirstName = "Platform"
SSOUserLastName = "Admin"
}
account_tags = {
Environment = "production"
Owner = "platform-team"
}
change_management_parameters = {
change_requested_by = "platform-team"
change_reason = "New production workload account"
}
}
Commit to aft-account-request. The ct-aft-account-request CodePipeline provisions the account through Control Tower Account Factory, which assigns the IAM Identity Center user from the SSO fields. AFT then runs your optional provisioning state machine, followed by global and account-specific customizations.
The Control Tower Hard Dependency: AFT Is Not a Replacement
AFT requires an existing Control Tower landing zone and relies on Control Tower to enroll every account it vends. There is no exit ramp here. CDK Landing Zone and OrgFormation are the CT-independent options.
CodeCommit and CodeConnections: What New AFT Customers Must Know
AWS CodeCommit reopened to new customers on November 25, 2025, but AWS's AFT deployment guide still says that first-time deployers without an existing CodeCommit repository must choose an external VCS provider such as GitHub or Bitbucket. Until the guide changes, plan on GitHub, Bitbucket, or GitLab through AWS CodeConnections, which new AFT customers can't use in 13 Regions: Hong Kong, Cape Town, Bahrain, Zurich, Jakarta, Hyderabad, Osaka, Melbourne, Tel Aviv, Spain, UAE, Thailand, and Mexico Central.
Regional Availability Gaps (10 Regions Without AFT)
AFT itself is unavailable in 10 Regions: Europe (Zurich), Europe (Spain), Canada West (Calgary), Asia Pacific (Melbourne), Asia Pacific (Malaysia), Asia Pacific (Thailand), Mexico (Central), Asia Pacific (New Zealand), Asia Pacific (Taipei), and the AWS European Sovereign Cloud. The two lists overlap but aren't the same, so check both. In these 10, AFT is off the table; in a CodeConnections gap, only an existing CodeCommit repository keeps it open.
The Deprovisioning Gap
AFT vends accounts but has no native workflow for closing them. Closing an account is a separate manual or custom-automated step, which adds up for teams with high sandbox churn.
When AFT Is the Right Choice for Terraform Teams
AFT fits one profile: Terraform-native, already on Control Tower, wanting GitOps-style account provisioning. Its opt-in plan-only mode for customizations gives a preview that CfCT's pipeline doesn't have. Rule it out if you want to leave Control Tower, if you're starting fresh, or if you're in a blocked Region.
Alternative 5: OrgFormation
OrgFormation is a community-built infrastructure as code tool for managing AWS Organizations using CloudFormation templates and a custom CLI. No Control Tower dependency, no pipeline infrastructure required: just CloudFormation templates and the org-formation CLI. For teams standardized on CloudFormation who want to manage their Organizations structure as code without adopting CDK or standing up pipeline infrastructure, OrgFormation is the most direct path.
CloudFormation-Based with Custom CLI Framework
Organization:
Root:
Type: OC::ORG::MasterAccount
Properties:
AccountName: My Organization Root
AccountId: '123456789012'
RootEmail: root@example.com
ProductionOU:
Type: OC::ORG::OrganizationalUnit
Properties:
OrganizationalUnitName: Production
Accounts:
- !Ref ProductionAccount
ProductionAccount:
Type: OC::ORG::Account
Properties:
AccountName: Production Account
RootEmail: production@example.com
CLI commands such as org-formation update and org-formation perform-tasks apply that template. You learn OrgFormation-specific commands, where a CDK landing zone uses the standard cdk deploy.
The Opt-In Preview: Why Your Pipeline Has to Enforce It
OrgFormation does have a preview step, but it's opt-in. For organization resources, org-formation create-change-set produces a change set you can review before execute-change-set applies it. For the cross-account CloudFormation layer, validate-stacks and print-stacks check and print the generated templates without deploying them. The gap is perform-tasks, the end-to-end command most automation runs: it has no dry-run flag. Unless your pipeline runs the preview commands as a separate gate, OU moves, SCP attachments, and account assignments apply straight to the organization, and a misconfigured SCP on a production OU takes effect immediately. The OrgFormation vs CDK landing zone comparison maps both preview workflows step by step.
What OrgFormation Does Well
OrgFormation delivers real value for its target use case: Organizations management as code with version control and declarative syntax, cross-account CloudFormation deployment through its task-based system, and a free open-source tool with no pipeline infrastructure required (init-pipeline scaffolds one if you want it). It's still maintained: the repository received commits in January 2026 and the npm package shipped v1.0.17 in March 2026. The org-formation-reference repository is a genuine asset, with shared multi-account patterns you can adapt.
CloudFormation Template Size Limits in Practice
CloudFormation accepts a template of up to 51,200 bytes passed inline, or up to 1 MB uploaded to S3. Complex Organizations configurations with many accounts and cross-account resources end up split across files with OrgFormation's !Include and Foreach long before any size limit, because a single flat organization.yml gets hard to review. CDK handles the same growth with ordinary functions and loops.
When OrgFormation's Trade-offs Are Acceptable
OrgFormation makes sense if your team is already standardized on CloudFormation, your requirements are straightforward, and you're committed to open-source tooling. The opt-in preview is the main reason I don't recommend it for production use at scale: safety depends on every pipeline remembering to run it. For a sandbox environment or a small organization with low SCP change frequency, it's workable. For a production multi-account environment where a misconfigured SCP has immediate blast radius, make the change-set step a mandatory gate.
Decision Framework: Choosing Based on Your Team Profile
Work through these five questions in order. Each one narrows the field.
1. Are you already on AWS Control Tower? If yes, you're choosing a customization layer, and CfCT and AFT are designed for this. CDK Landing Zone or OrgFormation require a full rebuild, not an incremental addition. If no (starting fresh), CfCT and AFT mean adopting Control Tower first.
2. Is your team Terraform-native or CDK/CF-native? Terraform teams on Control Tower should look hard at AFT. CDK/CF teams on Control Tower should look at CfCT (lightweight) or LZA (comprehensive). Teams starting fresh: CDK teams point toward CDK Landing Zone. CF teams point toward OrgFormation. No strong preference? Default to CDK Landing Zone for long-term flexibility.
3. Do you have a federal, healthcare, or financial services compliance deadline? For regulated federal workloads that benefit from AWS-maintained config (FedRAMP, CMMC, or DoD IL4/IL5 in AWS GovCloud), CT + LZA is the AWS-recommended path. For SOC 2, HIPAA, or PCI-DSS workloads where you want production-grade IaC without framework lock-in, CDK Landing Zone covers the infrastructure controls those audits ask about, and your controls remain auditable as code rather than as YAML config.
4. What is your team size? A 1-2 person platform team running CfCT at ~$3/month is well-matched. The same team running LZA at ~$430/month is over-invested. Larger teams (4+ engineers) with dedicated capacity for pipeline management get more value from LZA's comprehensive coverage.
5. How much build effort is acceptable? CDK Landing Zone: highest initial effort if you build it yourself, lowest long-term maintenance. CfCT: low initial effort, stays low. AFT: moderate (requires Terraform expertise and an existing Control Tower installation). LZA: moderate configuration effort, ongoing YAML maintenance. OrgFormation: low to moderate, with a change-set preview you have to remember to run.
Migration Paths: Getting from Control Tower to Something Better
If you're already on Control Tower and evaluating a move, the paths have different friction levels.
Path A: Stay on Control Tower, Add CfCT or AFT
Lowest friction. No landing zone rebuild. CfCT deploys as a single AWS Solutions package and starts applying custom SCPs and CloudFormation templates to new accounts. AFT takes longer (requires its own management account, VCS configuration, and Terraform module deployment) but gives you GitOps account provisioning. Both options keep all your existing Control Tower guardrails and Account Factory workflows intact. The constraint: you stay on Control Tower's architecture, with its shared 10-SCP-per-OU budget, Service Catalog vending unless you adopt AFT 1.24.0's Organizations method, and console-driven management.
Path B: Add LZA on Top of Control Tower for Compliance Framework Coverage
Medium complexity. LZA doesn't replace Control Tower here; it deploys alongside it as the AWS-recommended pattern. The Control Tower controls you've enabled stay active. LZA adds networking architecture, security service orchestration, and pre-built compliance configurations (FedRAMP, CMMC, HIPAA, DoD IL4/IL5) on top of what Control Tower already manages. The main commitment is the ~$430/month baseline infrastructure cost and the operational discipline of managing 8 YAML configuration files. This is the right path when you specifically want AWS-maintained compliance config rather than implementing equivalent controls in CDK.
Path C: Full IaC Departure with CDK Landing Zone + StackSets
Highest initial effort, maximum long-term flexibility, and you don't lose compliance posture in the trade. This path means decommissioning Control Tower guardrails and rebuilding the baseline as CDK + StackSets, which (in the Towards the Cloud implementation) ships the organization CloudTrail trail, security services, and centralized logging via 8 baseline StackSets. A workable approach: provision a parallel management account structure, migrate accounts by OU, validate StackSet coverage before deprovisioning CT controls. For teams migrating from a single account or rebuilding a Control Tower environment they've outgrown, this path takes weeks to months. Budget for parallel operation of both environments during transition and strong CDK expertise on the team.
Frequently Asked Questions
Can LZA be used without Control Tower?
Is AFT a replacement for Control Tower or an add-on?
Does CDK Landing Zone mean building everything from scratch?
What is CfCT and is it still maintained?
What is the fastest path from Control Tower to IaC-managed governance?
Small team: is LZA overkill?
What replaced the original AWS Landing Zone solution?
Conclusion: Match the Abstraction Level to Your Team
The right Control Tower alternative depends on where you are today, your team's tooling preferences, and how much initial build effort you can absorb.
CDK Landing Zone is the clear pick for IaC-first teams starting fresh or migrating off Control Tower: native CDK, StackSets, zero framework lock-in, and parallel StackSet rollouts instead of a 10-stage pipeline. LZA is the fastest path to pre-mapped compliance coverage for regulated industries, and AWS recommends running it on top of Control Tower. CfCT and AFT are the customization layers for teams staying on Control Tower: CfCT for CloudFormation templates and SCPs, AFT for Terraform teams whose home Region supports AFT and CodeConnections. OrgFormation fits CloudFormation-native teams with straightforward requirements, provided its opt-in change-set preview becomes part of every production SCP change.
If five options feels like too many, start with the core question: do you want AWS to run your landing zone, or do you want to own it as CDK code?
The pattern for leaving Control Tower entirely: CDK for Organizations, StackSets for cross-account baseline resources, production-ready SCP examples for governance, everything in Git. Start with one OU and one StackSet, validate, expand. Pair this with AWS multi-account best practices and AWS Organizations best practices before committing.
Next step