Listen "#17 AWS Account Structure"
Episode Synopsis
Using multiple AWS accounts to isolate workloads has been a best practice, not only since AWS introduced consolidated billing in 2010. AWS made a huge step by introducing AWS Organizations in 2017 and has added more and more features on top of the formerly boundary of an AWS account. In my opinion, we have passed the sweet spot between centralism and isolated accounts. The possibilities powered by AWS Organizations ruin the concept of isolated accounts with limited blast radius.
I recommend, to manage no more than 50 AWS accounts per AWS organization. Use multiple AWS organizations instead. Also, think twice before using SCP or Trusted Organization Access, both features make centralism permanent. I haven't seen a thriving, innovative, and centralized IT organization so far. Correct me if I'm wrong.
I recommend, to manage no more than 50 AWS accounts per AWS organization. Use multiple AWS organizations instead. Also, think twice before using SCP or Trusted Organization Access, both features make centralism permanent. I haven't seen a thriving, innovative, and centralized IT organization so far. Correct me if I'm wrong.
More episodes of the podcast cloudonaut
#095 AWS costs are like fingernails ...
25/08/2025
#092 The Cloud Control API came a long way
11/10/2024
#091 Cloudflare R2 Same Same But Different
25/07/2024
#090 AWS Testing Awesomeness
13/06/2024
#089 Copying 5 TB in 15 minutes
18/04/2024
#088 AWS networking without burning money?
15/03/2024
#087 Automate all the release processes!
29/02/2024
#086 Overwhelmed by Security Hub
13/02/2024
ZARZA We are Zarza, the prestigious firm behind major projects in information technology.