Managing a cloud infrastructure consisting of multiple AWS accounts is one of the most important but also complex topics for Well-Architected AWS environments. superwerker helps to establish the baseline for your AWS landscape.
Most organizations start small on AWS. Usually, there is a bit of prototyping or a single application needs to be migrated. There are not many moving parts involved and it seems suitable to deploy everything into one single AWS account.
Based on these basic scenarios, many people question the need of superwerker and a structured approach to a multi-account AWS environment when getting started with AWS. Based on the experiences with complex architectures on AWS, it’s guaranteed that previous small project will get more complex as they evolve. Therefore, ensuring best-practices for AWS from the outset is highly recommended.
Multi-account environments enable improved security and cost outcomes. They contribute to key metrics like development and deployment velocity by retaining the technological freedom for small and independent workload teams.
There are many good reasons to have a multi-account environment with AWS:
Using AWS Organizations, AWS Control Tower, and custom Organization Units, you can group and organize your AWS accounts. Per default, Control Tower configures a core
Organization Unit for the log and audit AWS accounts.