AWS › AWS Organizations & Multi Account Strategy

Why do organizations commonly adopt a multi account strategy instead of running all workloads within a single AWS account?

Beginner

Answer

A multi account strategy provides strong isolation between different environments or teams, limiting the blast radius of any security incident or misconfiguration to a single account rather than potentially affecting an entire organization's resources, simplifies cost tracking and allocation per team or project, and allows different accounts to have completely independent security policies and resource limits appropriate for their specific purpose, such as a more restrictive policy for a production account compared to a development sandbox account.
aws organizations create-account --email dev-team@example.com --account-name 'Development Account'
Real-world example A company separates its production workloads into their own dedicated AWS account, ensuring that a misconfiguration or security incident in a developer's sandbox account can never directly impact the production environment serving real customers.

Common follow-ups: How many separate accounts does a typical mature organization usually end up managing?;What is the tradeoff between having very granular accounts versus fewer, broader accounts?