Start here
This guide takes you from "what is a landing zone?" to being ready to brief a customer and run a Landing Zone Accelerator (LZA) deployment with the Universal Configuration. No prior AWS multi-account experience is assumed.
By the end you will be able to
- Explain what a landing zone is and why customers need one
- Describe what LZA is, what it is not, and how it relates to AWS Control Tower
- Walk through how LZA is installed and how its pipelines work
- Name the 8 configuration files and what each one controls
- Describe every account, OU, and guardrail the Universal Configuration creates
- Trace network traffic through the hub-and-spoke design
- Explain the security, logging and backup services that get turned on
- Collect the right inputs from a customer before deploying
- Handle common customer questions and objections
- Operate the environment after day one: add accounts, upgrade, troubleshoot
How to use this guide
1. Read in order
Modules build on each other. Each ends with a Mark complete button so the sidebar tracks your progress (saved in this browser).
2. Click everything
Diagrams are interactive: click accounts, VPCs, pipeline stages and pools to see details. Play the traffic flows in the network module.
3. Test yourself
Finish with the flash cards and the quiz. Aim for 85%+ on the quiz before your first customer briefing.
Suggested learning path
| Session | Modules | Goal | Time |
|---|---|---|---|
| 1 | Landing zones & LZA, AWS building blocks | Speak the vocabulary | 45 min |
| 2 | How LZA works, Deploying LZA (with the interactive walkthrough) | Understand the machinery | 60 min |
| 3 | Universal Configuration: overview, accounts & guardrails | Know what gets built | 45 min |
| 4 | UC networking, UC security & logging | Explain the architecture | 60 min |
| 5 | Day 2 operations, Briefing a customer | Be customer-ready | 45 min |
| 6 | Flash cards, Quiz, Glossary | Lock it in | 30 min |
What is a landing zone, and what is LZA?
Before any technology: the problem LZA solves, in plain language.
The problem: one AWS account doesn't scale
A brand-new organization often starts with a single AWS account. Everything lives together: development experiments, production databases, security logs. That becomes a problem quickly:
- Blast radius. A mistake (or an attacker) in one workload can affect everything else in the account.
- Permissions sprawl. It's hard to give the dev team freedom without also giving them access to production.
- Billing confusion. You can't easily tell which team or project spent what.
- Compliance. Auditors want logs that nobody can delete, and evidence that controls are applied everywhere.
The AWS best practice is to use many accounts: one per environment, team or workload, grouped and governed centrally.
What is a landing zone?
A landing zone is a pre-built, secure, multi-account AWS environment, ready for teams to "land" their workloads in. A good one includes:
Account structure
Accounts grouped into organizational units (OUs) by purpose: security, infrastructure, workloads.
Identity
One place where people sign in (single sign-on) and get the right access to the right accounts.
Guardrails
Rules that prevent risky actions (preventive) and spot misconfigurations (detective).
Central logging
Every API call and important log copied to an account that nobody can tamper with.
Security services
Threat detection, posture checks and findings, managed centrally.
Networking
Shared, inspected connectivity between accounts, to the internet, and to on-premises.
What is the Landing Zone Accelerator on AWS?
LZA is a free, open-source AWS solution that builds and maintains a landing zone from configuration files. You describe what you want in YAML text files, and LZA's pipeline deploys it across all your accounts and Regions, and keeps it that way.
What it is
- An AWS Solution, published by AWS, open source on GitHub (
awslabs/landing-zone-accelerator-on-aws) - Built with the AWS Cloud Development Kit (CDK), deployed through AWS CodePipeline
- Driven by 8 YAML configuration files, not code you write
- Covers 35+ AWS services and features
- No additional charge: you pay only for the AWS services it turns on
- Works in commercial Regions, AWS GovCloud (US), and other partitions
What it is not
- Not a compliance certificate: it helps you align with frameworks
- Not a managed service: the customer owns and runs it
- Not an application platform: it builds the foundation, not workloads (for example it doesn't deploy your load balancers or apps)
- Not a replacement for Control Tower: it is designed to work with Control Tower
LZA and AWS Control Tower
AWS Control Tower is an AWS service that sets up a basic landing zone: an organization, a Security OU with Log Archive and Audit accounts, an organization CloudTrail, IAM Identity Center, and a catalog of controls. AWS recommends Control Tower as the foundation and LZA on top to extend it.
| Capability | Control Tower alone | Control Tower + LZA |
|---|---|---|
| Organization, OUs, Log Archive and Audit accounts | ✓ | ✓ (LZA can even set up Control Tower for you) |
| Controls (guardrails) from the Control Tower catalog | ✓ | ✓ plus custom SCPs, RCPs, declarative, tag and backup policies |
| Centralized networking (Transit Gateway, firewall, IPAM, endpoints) | — | ✓ |
| Security services org-wide (GuardDuty, Security Hub, Macie, Config rules) | Partial | ✓ configured and delegated |
| Everything as version-controlled configuration with a deployment pipeline | — | ✓ |
| Drift detection and automatic re-application | Control Tower drift only | ✓ every pipeline run re-applies the config |
Related tools you may hear about: Customizations for Control Tower (CfCT) and Account Factory for Terraform (AFT) also extend Control Tower. LZA is the most complete "configuration-file driven" option, especially for regulated customers.
Who uses LZA?
LZA was designed for customers with strict security and compliance needs: public sector, defense, healthcare, financial services, and anyone who wants a well-architected foundation fast. AWS publishes best-practice configurations for it, and the Universal Configuration (covered later) is the recommended general-purpose starting point.
The AWS building blocks you need to know
LZA wires together dozens of AWS services. These are the ones you must be able to explain simply. Click a category to filter.
How LZA works under the hood
Two pipelines, one set of configuration files, and a lot of CloudFormation. Once you understand this loop, everything else makes sense.
The big picture
- You launch one CloudFormation template (
AWSAccelerator-InstallerStack) in the management account. It takes about 8 minutes. - The Installer pipeline (
AWSAccelerator-Installer) downloads the LZA source code from GitHub and deploys the second pipeline. Its only job is to install or upgrade LZA itself. - The Core pipeline (
AWSAccelerator-Pipeline) reads your configuration files and deploys everything they describe, account by account and Region by Region, using AWS CDK and CloudFormation. The first run takes about 45 minutes and deploys a minimal baseline. - You edit the configuration files and push the change to the configuration repository. The Core pipeline runs again and makes the environment match.
Why two pipelines?
They are separate by design. Upgrading LZA to a new version only means changing one parameter (the release branch name, such as release/v1.17.0) on the installer CloudFormation stack. The Installer pipeline then rebuilds the Core pipeline with the new code, and the Core pipeline re-applies your unchanged configuration.
Inside the Core pipeline
Click each stage to see what it does. Stages run in order; if one fails, the pipeline stops there and you fix the cause and retry.
Where the configuration lives
When you launch the installer, the Configuration Repository Location parameter decides where your config files are stored. You cannot change it later without stack failures, so decide up front:
Amazon S3
The files live in an S3 bucket (aws-accelerator-config-…) as a zip. Simple; you upload a new zip to deploy.
AWS CodeCommit
A Git repository in the management account. The historical default. Check CodeCommit availability for new customers.
CodeConnections
A Git repository you already use (for example GitHub or GitLab) connected through AWS CodeConnections. Best for teams that review changes with pull requests.
The 8 configuration files
Every LZA environment is described by these YAML files, plus folders of supporting files (policy JSON, firewall rules, SSM documents). Click a file.
Replacements: variables for your config
replacements-config.yaml defines named values that the other files reference with double curly braces. LZA substitutes them before reading the files. Change a value once, and it updates everywhere.
replacements-config.yaml
globalReplacements:
- key: HomeRegion
type: String
value: us-east-1
- key: GlobalCidr
type: String
value: "10.0.0.0/8"network-config.yaml
transitGateways:
- name: "{{ AcceleratorPrefix }}-{{ HomeRegion }}-tgw"
region: "{{ HomeRegion }}"
# becomes: AWSAccelerator-us-east-1-tgwPolicy files can also use tokens that LZA fills in at deploy time, such as ${ORG_ID}, ${PARTITION} and ${ACCELERATOR_PREFIX}.
Three behaviors to remember
Validation first
The Build stage checks your files against a schema. Typos and invalid values fail fast, before anything changes.
Desired state
Every run re-applies the full configuration. Manual console changes to LZA-managed resources get overwritten (and many are blocked by SCPs).
Optional approval
With Enable Approval Stage = Yes, the pipeline pauses after a CDK diff so someone can review and approve changes. Recommended for any landing zone that runs real workloads: one pipeline run deploys to every account at once, Dev and Prod alike.
Because a config change hits Prod the same moment it hits Dev, some customers build a second, separate landing zone (its own AWS organization and its own LZA install) only to try out config changes and LZA upgrades safely before applying them to the real one. When this guide says "test in a non-production landing zone", it means that separate organization, not the Dev OU.
Deploying LZA, step by step
The full journey from a brand-new AWS account to a running landing zone, with and without Control Tower. Use the interactive walkthrough below, then the checklist.
Phases at a glance
| Phase | What you do | What happens | Time |
|---|---|---|---|
| 0. Plan | Collect inputs: emails, home Region, Regions, IP ranges, identity provider, network model | Nothing in AWS yet | Days–weeks (customer decisions) |
| 1. Prepare | Create the management account, enable AWS Organizations (all features), raise quotas if needed | An empty organization | ~1 hour |
| 2. Launch | Deploy AWSAccelerator-InstallerStack with your parameters | Installer pipeline, then Core pipeline | ~8 min stack + pipelines |
| 3. Await | Watch the first Core pipeline run | Control Tower (if enabled), Log Archive and Audit accounts, keys, log buckets | ~45 min (longer with Control Tower setup) |
| 4. Configure | Copy in the Universal Configuration, update emails, Region, CIDRs | Nothing until you push | Hours |
| 5. Deploy config | Push to the configuration repository | Accounts, OUs, guardrails, security services, networking | 1–several hours |
| 6. Validate | Check the pipeline, sign in through Identity Center, run the Controls Test Pack | Evidence the controls work | Hours |
Interactive walkthrough
Three tutorials in one: building a landing zone with Control Tower, without Control Tower, and what happens inside one pipeline run. Click through each step and watch the diagram grow.
Control Tower prerequisites (when LZA sets it up for you)
The Universal Configuration expects Control Tower. LZA can deploy Control Tower itself if the organization is clean:
If the customer already has Control Tower, LZA can work with it, but plan carefully. The Universal Configuration docs recommend starting with a new organization for the best experience.
cdk bootstrap anywhere yourself. The Installer pipeline bootstraps the management account automatically (in the home Region and the global Region, such as us-east-1) with a stack named AWSAccelerator-CDKToolkit. The Core pipeline's Bootstrap stage then does the same for every other account and Region in your configuration. If the customer later deploys their own CDK apps, they should use their own bootstrap template so it doesn't collide with LZA's.Installer stack parameters that matter
| Parameter | What to enter | Watch out |
|---|---|---|
| Branch Name | The LZA release branch, for example release/v1.17.0 | Changing it later is how you upgrade |
| Enable Approval Stage | Yes (default) and an approval email list | Someone must approve every run |
| Management / LogArchive / Audit Account Email | Three unique, monitored email addresses | An email address can belong to only one AWS account |
| Control Tower Environment | Yes for the Universal Configuration | — |
| Accelerator Resource name prefix | Leave AWSAccelerator | Changing it after install causes stack failure |
| Configuration Repository Location | S3, CodeCommit, or CodeConnections | Cannot be changed after install |
| Enable Diagnostics Pack | Yes | Helps troubleshooting |
Deployment day checklist
The Universal Configuration
An AWS-published, ready-to-deploy set of LZA configuration files that turns an empty LZA into a well-architected, security-focused landing zone.
What it is
The LZA Universal Configuration (UC) lives on GitHub at aws/lza-universal-configuration. It is based on the AWS Well-Architected Framework, the AWS Security Reference Architecture and the "Organizing your AWS environment using multiple accounts" whitepaper. Instead of starting from a blank slate, a customer starts from proven patterns and adjusts.
Opinionated
Makes sensible decisions for you: account layout, guardrails, security services, logging, networking.
Built on Control Tower
Uses Control Tower as the foundation and layers extra controls on top.
Meant to be adjusted
A strong starting point. Customers should review every setting against their own requirements.
How it's packaged: modules + replacements
A UC release is assembled from building blocks. Each release ships ready-made zips for common combinations; under the hood the recipe is:
1. Base module
modules/base/default: accounts, OUs, guardrails, IAM, security, logging, backup, budgets. Always used.
2. Network module
Pick one: hub-and-spoke (default, a VPC per workload account) or shared-vpc (central VPCs shared by subnet).
3. Partition replacements
Adjust for where it runs: AWS standard (commercial), AWS GovCloud (US), or the AWS European Sovereign Cloud.
The partition files remove or change what isn't available there. For example, the GovCloud variant leaves out Amazon Macie, central root user management and one Config rule, because those aren't available in GovCloud (US).
What the UC deploys: a tour
| Area | Highlights | Config file |
|---|---|---|
| Accounts & OUs | 6 core accounts; Security, Infrastructure, Workloads (Sandbox/Dev/Test/Prod) and Suspended OUs | accounts, organization |
| Control Tower | Landing zone version 4.0, Identity Center access, 11 extra Control Tower controls (detective checks) | global |
| Guardrails | 8 SCPs (including quarantine for new accounts), 1 RCP for a data perimeter, 1 declarative policy blocking VPC internet access by default, tag and backup policies | organization |
| Identity | IAM Identity Center delegated to the SharedServices account; standard Backup and EC2 SSM roles; a sample permission boundary | iam, global |
| Security services | GuardDuty, Security Hub (AWS Foundational Security Best Practices, NIST 800-53 Rev 5, CIS v3.0.0), Macie, AWS Config rules, IAM Access Analyzer, EBS default encryption, S3 Block Public Access, all delegated to the Audit account | security |
| Logging | Control Tower organization trail; all CloudWatch Logs replicated to the Log Archive account; VPC, Transit Gateway, firewall and DNS query logs | global, network |
| Networking | Transit Gateway hub, AWS Network Firewall inspection, central ingress/egress, central VPC endpoints, IPAM, DNS Firewall, 2 Availability Zones | network |
| Backup & cost | Tag-driven AWS Backup plans (continuous to monthly), backup vault per account, a $2,000 monthly budget alert, Cost and Usage Report | organization, global |
What a customer must change before deploying
Controls Test Pack (new in v1.4.0)
Each UC release now includes a Controls Test Pack (lza-universal-config-cats-<version>.zip) that runs on CATS, the Control Acceptance Testing Suite. After deployment it checks the live environment against all 193 controls in the LZA Compliance Workbook and reports results that can be mapped to a compliance framework in OSCAL format. It deploys temporary test resources and deliberately tries actions the SCPs and RCPs should block, so run it in a separate test landing zone first, or before real workloads move in.
Accounts, OUs and guardrails
Who lives where, and which rules apply to them. Click any OU or account on the map.
Select an account or OU
Each one shows its purpose, what the UC deploys there, and which policies apply.
Layers of protection
The UC uses defense in depth: several kinds of controls that overlap, so one gap doesn't expose everything. Click a layer.
The SCPs in the Universal Configuration
| Policy | Attached to | In plain English |
|---|
Networking: hub and spoke
All traffic between VPCs, to the internet and to AWS services goes through one hub and gets inspected by a firewall. Play the traffic flows to see exactly how.
The pieces
Transit Gateway
The central router in the Network account. Every VPC attaches to it. Two route tables decide where traffic goes: spoke (everything → inspection) and firewall (back to the right VPC, or out to egress).
Inspection VPC
In the Network account. Holds AWS Network Firewall, which checks traffic against Suricata-style rules. The default rule set ends with drop everything.
Egress VPC
In the Perimeter account. Shared NAT gateways (one per AZ) and an internet gateway for outbound internet access.
Ingress VPC
In the Perimeter account. Public subnets for customer-deployed load balancers that receive traffic from the internet. LZA doesn't deploy the load balancers.
Endpoints VPC
In the Network account. Central interface endpoints (EC2, SSM, KMS, CloudWatch Logs, ECR and more) so workloads reach AWS APIs privately.
Workload VPCs
One VPC per account in the Dev, Test and Prod OUs, created automatically from VPC templates, with app, data and TGW subnets in two AZs.
Interactive network diagram
Pick a traffic flow to animate it, or click a VPC for details.
Pick a flow or a VPC
Orange dashed lines show the path. Numbers mark each hop.
pass rules (for example by domain name) to firewall-rules/rules.txt.IP address plan (IPAM)
AWS IPAM hands out address ranges from a hierarchy of pools, so VPCs never overlap. These are the UC defaults from replacements-config.yaml. Click a pool.
Workload VPC layout (from the VPC template)
Every Dev, Test and Prod account gets a /22 VPC (1,024 addresses) from its environment's pool:
App subnets /24 (251 usable IPs each), data subnets /26 (59 usable each), TGW attachment subnets /28. AWS reserves 5 addresses in every subnet. Each environment pool is a /14, so it fits 256 of these VPCs (one per account).
Hub and spoke vs shared VPC
| Hub and spoke (default) | Shared VPC | |
|---|---|---|
| Workload networking | Each workload account gets its own VPC from a template | Three central VPCs (shared-dev, shared-test, shared-prod) in the Network account; subnets shared to accounts with AWS RAM |
| Who controls routing | Account teams own their VPC (within guardrails) | The central network team |
| IP efficiency | Moderate: every account reserves a whole VPC | High: accounts share address space |
| Isolation | Strong account-level boundaries | Workloads in the same environment share a VPC |
| Choose when | DevOps teams, clear ownership, strong isolation | Tight IP space, central network operations, chatty workloads |
More network services in the UC
- DNS Firewall (Route 53 Resolver) on every VPC, blocking domains on AWS-managed threat lists (aggregate threats, malware, botnet command-and-control).
- DNS query logging, VPC Flow Logs (all traffic, custom fields, 30 days in CloudWatch then centralized) and Transit Gateway Flow Logs.
- Default VPCs deleted in every account and Region (they have open internet access).
- VPC Block Public Access declarative policy: Security OU, Dev/Test/Prod OUs and the Network and SharedServices accounts can't use internet gateways. Perimeter is excluded because ingress and egress need them.
- Two Availability Zones (a and b) for every VPC. Adding a third AZ is a supported customization (more subnets, NAT gateway and firewall endpoint).
- Hybrid connectivity (Direct Connect or VPN to on-premises) is documented but not deployed by default; it attaches to the same Transit Gateway.
- Optional Transit Gateway encryption support (LZA v1.17.0+, commented out by default) for encryption in transit with VPC Encryption Controls.
Security, identity, logging and backup
The services that watch, record and protect the environment, and which account runs each one.
Who does what: delegated administration
Instead of running everything from the powerful management account, the UC delegates each service to a specialist account. That keeps the management account quiet and limits who needs access to it.
| Account | Administers | Why |
|---|---|---|
| Audit (Security OU) | GuardDuty, Security Hub, Macie, AWS Config aggregation, IAM Access Analyzer | The security team sees findings for every account in one place |
| Log Archive (Security OU) | Central log buckets (CloudTrail, CloudWatch Logs, access logs, ELB logs) | Logs are stored where workload owners can't change or delete them |
| SharedServices (Infrastructure OU) | IAM Identity Center | Separates identity administration from organization management |
| Network (Infrastructure OU) | Transit Gateway, IPAM, Network Firewall, endpoints | Network team owns shared connectivity |
Security services turned on
How logs get to the Log Archive account
Click each step of the pipeline.
Identity: how people sign in
- A user signs in with the customer's identity provider (for example Microsoft Entra ID, Okta or Active Directory), federated to IAM Identity Center with SAML 2.0 and SCIM.
- Identity Center (administered from the SharedServices account) shows the AWS access portal with the accounts and permission sets the user's groups are assigned.
- The user picks an account and role and gets temporary credentials. No long-lived IAM users: an SCP blocks creating them.
Backup-Role and an EC2-Default-SSM-Role in every account, and a sample permission boundary (End-User-Policy) teams can use to limit roles they create.Backups and tags
Backups are driven by a tag. Put BackupPlan on a resource and AWS Backup picks it up automatically in Infrastructure and Workloads accounts:
| BackupPlan tag value | Schedule | Retention |
|---|---|---|
| Continuous (S3 only) | Continuous, point-in-time | 35 days |
| Hourly | Every hour at :05 | 365 days (30 in standard storage, then cold) |
| Daily | 05:00 daily | 365 days (30 in standard, then cold) |
| Weekly | Sundays 05:00 | 365 days (30 in standard, then cold) |
| Monthly | 1st of the month 05:00 | 730 days (60 in standard, then cold) |
Tag policies make sure the tag value is valid; they don't force every resource to have it. Resources without the tag aren't backed up.
Cost visibility
- A monthly AWS Budget of $2,000 with email alerts at 50%, 75%, 90% and 100%.
- A Cost and Usage Report in Parquet format for detailed analysis.
- Security notifications in three SNS topics (High, Medium, Low) so the right people get the right alerts.
BackupPlan tag.Day 2: running the landing zone
Deployment is day one. These are the tasks the customer's team will do every week, and the rules that keep the environment healthy.
The golden rule
Common tasks
Add a new workload account
- Reserve a unique email address.
- Add an entry under
workloadAccountsinaccounts-config.yamlwith a name, email and OU (for exampleWorkloads/Dev). - Push and approve. The Prepare stage creates it through Control Tower Account Factory; quarantine SCP blocks it until the pipeline finishes; the VPC template for its OU gives it a VPC automatically.
Add a new OU
Add it to organizationalUnits in organization-config.yaml, then reference it in policies, VPC templates and share targets as needed. Manage OUs only through LZA after go-live.
Allow workloads to reach an internet site
Add a pass rule above the default drop in firewall-rules/rules.txt, for example a TLS rule that matches an SNI domain like .github.com. Invalid Suricata syntax fails the pipeline, and the firewall is shared by every environment, so try new rules in a separate test landing zone first if you have one.
Change or add an SCP
Edit or add the JSON file in service-control-policies/ and reference it in organization-config.yaml with its deployment targets. Keep under 10,240 characters and remember the 10-SCPs-per-target limit. The UC turns on scpRevertChangesConfig, so manual SCP edits in the console are reverted.
Upgrade LZA to a new version
- Read the release notes for every version between yours and the target.
- Run the Core pipeline once on your current version and fix any failures (a clean baseline).
- Update the installer CloudFormation stack: replace the template with the latest one and set Branch Name to the new release branch.
- The stack updates in about 10 minutes; the Installer and Core pipelines then run (another 20–60 minutes, depending on accounts and Regions).
Upgrade the Universal Configuration
UC releases come with a changelog and upgrade notes for each change. Compare the new release with your current config (a diff tool helps), adopt the changes you want, and push. The UC is configuration, not software: nothing updates until you merge and deploy.
Decommission an account
Move it to the Suspended OU in the config. The Suspended guardrail SCP denies everything, so nothing in it can run while you close it.
Troubleshooting a failed pipeline
- Open the Core pipeline in CodePipeline and find the failed stage.
- Open the CodeBuild logs for that action: they name the account, Region and CloudFormation stack.
- Open that stack's Events in the target account to see the exact resource and error.
- Fix the cause (usually the config, a quota, or a manual change) and choose Retry or release a new change.
Day 2 do's and don'ts
Do
- Keep the config in version control with pull-request reviews
- Keep the approval stage on: each run changes every account, Dev and Prod together
- Upgrade regularly; read release notes
- Try config changes and upgrades in a separate test landing zone (its own organization) first
- Watch Security Hub findings and budget alerts
Don't
- Edit LZA-created resources in the console
- Change the accelerator prefix or config repository location after install
- Create OUs or accounts outside LZA
- Delete the default-deny firewall rule to "fix" connectivity
- Skip versions without reading every release's notes
Briefing a customer
How to explain LZA and the Universal Configuration to different audiences, collect the inputs you need, and answer the questions you will get.
The 30-second pitch
"The Landing Zone Accelerator is a free AWS solution that builds a secure, multi-account AWS environment from configuration files, and keeps it that way through an automated pipeline. With the Universal Configuration, you start from AWS's best-practice design: separate accounts for security, networking and each environment, guardrails that prevent risky actions, centralized logging and threat detection, and inspected networking. You get a well-architected foundation in days instead of months, and every change after that is reviewed and repeatable."
Tailor the message
Suggested briefing agenda (60 minutes)
| Min | Topic | Use from this guide |
|---|---|---|
| 5 | Their goals and constraints (compliance, timeline, existing AWS use) | Discovery questions below |
| 10 | Why multi-account; what a landing zone is | Module 1 analogy |
| 10 | How LZA works: config files and pipelines | Module 3 big picture |
| 15 | What the Universal Configuration builds: accounts, guardrails, network, security | Org map and network diagram |
| 10 | Deployment plan, timeline and responsibilities | Module 4 phases |
| 10 | Questions, decisions needed, next steps | Inputs checklist |
Discovery questions
- Which compliance frameworks matter (for example NIST 800-53, CIS, FedRAMP, DoD SRG, HIPAA)?
- Do you already use AWS? Is there an existing organization, Control Tower, or accounts to bring in?
- Which Regions (and partitions, such as GovCloud) do you need now and later?
- What identity provider will people sign in with?
- What IP ranges are used on-premises and in other clouds? Will you connect with Direct Connect or VPN?
- Which internet destinations do workloads need (package repositories, SaaS APIs)?
- Who will own the landing zone day to day: a platform team, network team, security team?
- How do you manage change today (pull requests, change advisory board)?
Inputs to collect before deployment
Questions you will get
Cost: what drives the bill
LZA itself is free. The AWS services it enables are not. The biggest always-on items in the UC network are hourly charges. Rough us-east-1 list prices to frame the conversation (always build a real estimate with the AWS Pricing Calculator):
| Item in the UC | Quantity (2 AZs) | Approximate list price |
|---|---|---|
| AWS Network Firewall endpoints | 2 (one per AZ) | $0.395 per endpoint-hour ≈ $570/month, plus $0.065/GB processed |
| NAT gateways (egress) | 2 | Hourly plus per-GB charges |
| Transit Gateway attachments | One per VPC (5 core + each workload VPC) | $0.05 per attachment-hour ≈ $36/month each, plus per-GB |
| Interface VPC endpoints | 13 services × 2 AZs | Hourly per endpoint per AZ, plus per-GB |
| Security services | Every account | Usage-based: GuardDuty, Security Hub, Config, Macie scale with resources and data |
| Logging and storage | Central buckets, Kinesis, Firehose | Scales with log volume |
Centralizing NAT, firewall and endpoints is cheaper than putting them in every VPC: that is one of the design goals of the hub. The included $2,000 budget alert helps spot surprises early.
Shared responsibility for the landing zone
AWS provides
- The LZA solution, the Universal Configuration and their documentation
- The underlying services and their security
- Fixes and new versions through GitHub releases
The customer owns
- Reviewing and approving every setting
- Running, upgrading and monitoring the landing zone
- Workload security, data classification and their compliance authorization (for example an ATO)
Flash cards
Click a card (or press Space) to flip it. Mark whether you knew it; cards you miss come back. Arrow keys move between cards.
Readiness quiz
26 questions covering the whole guide. Each answer explains why. Aim for 85% or better before briefing a customer.
Glossary
Every acronym and term in one place.
Sources and further reading
Official sources used for this guide. Check them for the latest details before a deployment.
- Landing Zone Accelerator on AWS: Implementation Guide
- LZA prerequisites (including Control Tower auto-deploy requirements)
- Step 1. Launch the stack (installer parameters)
- Step 2. Await initial environment deployment
- Core pipeline stages and Installer pipeline
- Update the solution
- LZA source code and releases (GitHub)
- LZA Universal Configuration (GitHub): configuration, docs and changelog
- AWS Prescriptive Guidance: LZA overview (DoD SCCA context)
- Organizing your AWS environment using multiple accounts (whitepaper)
- AWS Organizations quotas (policy sizes and attachments)
- How AWS Transit Gateway works
- AWS Network Firewall pricing and AWS Pricing Calculator
Universal Configuration details (accounts, policies, CIDRs, firewall rules, endpoints, backup plans) were read directly from the v1.4.0 configuration files and documentation.