So far I have secured root, set a budget, turned on CloudTrail and CloudWatch, and added tags. All of that sits in one account. The next step is the structure around it: AWS Organizations .
Why more than one account
An AWS account is a strong boundary for security, cost and blast radius .
A mistake in a sandbox account cannot touch production.
Each account has its own root user, IAM and limits, so teams can work separately.
The building blocks
Term What it is Notes
Organization The group of accounts you manage together Created from one account
Management account The account that creates the organization and pays the bill SCPs do not apply to it
Member accounts Every other account in the organization One per workload or team
OU An organizational unit that groups accounts Policies on an OU apply to its accounts
SCP A service control policy Sets the maximum permissions, never grants them
Consolidated billing
All member accounts roll up to one bill on the management account.
Usage across accounts…