Most teams start on AWS with one account that holds production, test servers, audit logs and the billing owner. Then a test server is compromised, or a cleanup script hits the wrong environment, and nothing stands between the mistake and production.
An AWS account is a hard isolation boundary. Roles, policies and resources in one account cannot touch another unless you grant cross-account access. If you come from Azure, an account is closest to a subscription, and AWS Organizations groups them, bills them together and applies policy from the top.
AWS does not charge for accounts or for Organizations. You pay only for what runs inside them.
This is the smallest layout worth having, even if all you do is call Amazon Bedrock:
Organization root├── Management Organizations and billing. No workloads├── OU: Security│ └── Log/Security Audit logs, security tooling, delegated admin└── OU: Workloads├── OU: Prod│ └── Prod Production└── OU: NonProd└── NonProd Development, testing, experiments
Figure: Four accounts, with production and non-production in separate OUs
Northwind has one AWS account. It holds the production app, the test servers and the CloudTrail bucket, and every developer is an administrator.
❌ Figure: Bad example - Bad example - Whoever compromises a test server can reach production and delete the audit logs
Northwind has Management, Log/Security, Prod and NonProd accounts. Developers are administrators in NonProd and read-only in Prod. The CloudTrail bucket lives in Log/Security, where no workload admin has access.
✅ Figure: Good example - Good example - A compromised test server stays in NonProd, and the logs that record it are out of reach
A managed service with no servers makes a second account feel like overhead. It still pays for itself:
Give each new workload its own account, for example the public website or shared DNS. Splitting a workload out of a shared account later is a migration. Larger environments add OUs such as Infrastructure, Sandbox and Suspended. See Recommended OUs and accounts.
AWS Control Tower sets up a landing zone on top of Organizations, with logging and security accounts and baseline controls. For a handful of accounts, plain Organizations plus infrastructure as code is less to learn and keeps every setting in your repository.
Figure: Control Tower is optional for a small organization