GREENFIELD ONLY — This tool generates landing zone configurations for brand new AWS accounts with no existing Organizations, Control Tower, or workloads. Do not run on existing AWS environments.
WIPRO

Landing Zone Accelerator

AWS Control Tower — Automated Setup

Deployment Journey

1
Pre-flightChecks
2
QualifyQuestions
3
LZ TypeCT or Custom
4
BlueprintAI generates
5
ReviewEdit + Approve
6
VariablesFill values
7
GenerateCode
8
DeployPush + Monitor
Manual — engineer does this
Automated — accelerator does this

Step 1 — Pre-flight Checklist

Complete all checks before proceeding. This tool is for GREENFIELD deployments only.

Verify this is a brand new AWS account with no existing Organizations, Control Tower, CloudTrail, Config, or workloads before ticking these items.
AWS Account Setup
Technical Pre-checks
Pre-flight complete — proceed to Step 2

Step 2 — Customer Qualifier

Answer all questions. Sector auto-suggests compliance. Compliance auto-suggests SCPs.

Used as DR / governed region
Minimum 4: Management, Audit, Log Archive, Shared Services
Suggested based on your sector selection are highlighted in orange — click to select

Q10 Service Control Policies (SCPs)

Orange = mandatory. Purple = suggested from your compliance selection. Maximum 20 SCPs.

SCPs selected 0  / 20 max

Step 3 — Choose Landing Zone Approach

Select the approach that fits your customer. The right choice depends on their existing AWS environment and requirements.

AWS Control Tower Recommended

Control Tower

AWS managed governance framework. Best for greenfield environments where compliance is critical.

  • Pre-built guardrails — 300+ controls
  • Automated account vending (AFT)
  • Built-in Log Archive + Audit accounts
  • Security Hub integration
  • CT dashboard for visibility
  • 30–60 minute setup
Generates: Terraform (CT resource) + CloudFormation (3 stacks)
Custom Solution

Custom AWS Organizations

Build governance directly using AWS Organizations and SCPs. More flexible but more complex to maintain.

  • Full control over every setting
  • No Control Tower overhead
  • Works with existing Org setups
  • Custom OU structures allowed
  • More manual ongoing maintenance
  • Longer setup — more manual steps
Generates: Terraform (Org resources) + CloudFormation (custom stacks)
Not sure which to choose? Use Control Tower for greenfield + compliance. Use Custom if existing Organizations or non-standard configurations are needed.
Generating blueprint using AI... please wait 30–60 seconds.
Approved

Step 4 — Review Your Blueprint

Edit anything that needs to change. Click Check Changes to see the diff. Then click Approve Blueprint to proceed to variable input.
Editable Blueprint Click anywhere to edit
No changes — matches original AI output.
Original
Edited
Blueprint approved. Fill in your variable values below to unlock code generation.

Step 6 — Enter Your Variable Values

Fill in all required values. These are passed directly into the generated scripts — no placeholders in the final code.

Four accounts are mandatory for every landing zone: Management, Audit, Log Archive, Shared Services. Break Glass is strongly recommended.
Mandatory Account IDs
Account Email Addresses
Naming and Network
0 of 8 required fields completed
Fill in all required fields above to unlock code generation.
Generating infrastructure code using AI... please wait 30–60 seconds.

Step 7 — Your Infrastructure Code

All values pre-filled. Download files or push directly to your repository.


Deployment Sequence


Hover any highlighted line to see what it does
Script does this automatically
Set from your answers

Push to Repository

Push generated files to your repo

Monitor Repository

Commits and workflow runs

Recent Commits
Push code first
Workflow Runs
No runs yet