.AWS Landing Zone versus AWS Control Tower

AWS Landing Zone and AWS Control Tower help set up and govern a new, secure, multi-account AWS environment based on AWS best practices. Both consist of core accounts and resources which will implement a initial security baseline.
The following table compares the managed service (AWS Control Tower) with the solution (AWS Landing Zone).

Update:

🚨 AWS Control Tower allows existing organizations to set up a landing zone.

References

AWS Landing Zone

• 📚 Implementation Guide
• 📚 Developers Guide
• 📚 User Guide
• 📚 Upgrade Guide
• 📺 Videos
• 🧰 Solutions
  • 🔧 Account Vending Machine
  • 🔧 Security Hub Multiaccount Scripts

AWS Control Tower

• 📚 User Guide
• 📚 Pricing
• 🎓 Labs
• 📺 Videos
• 🧰 Solutions
  • 🔧 Customizations for AWS Control Tower
  • 🔧 Enabling guardrails in new AWS Regions the AWS Control Tower supports

Which one should I choose?

❓Are you new two AWS?
❗️Use AWS Control Tower

❓Do you need a configurable landing zone with full customization and control over every part?
❗️Use AWS Landing Zone

1. ↩

Member accounts could be provisioned in every region no matter where the Account Vending Machine is deployed.
⚠️You just need to take care that your CloudFormation templates & Lambdas are available in the requested region.

1. ↩

AWS Control Tower could provision new Accounts (Network baseline) into the following regions: North-Virginia (us-east-1), Ohio (us-east-2), Oregon (us-west-2), Irland (eu-west-1) and Sydney (ap-southeast-2).