AWS Learning Journey

One AWS Account for Everything? Here's Why That Eventually Breaks

How real teams structure AWS accounts — and why the root user is the most dangerous login you own.

9 min read · 1718 words
AWSCloud SecurityCloud GovernanceDevOpsCloud Computing
One AWS Account for Everything? Here's Why That Eventually Breaks cover image

AWS from Zero to Production — Phase 1, Part 3 of 5 · See the full series roadmap


It’s 4:55 p.m. on a Friday.

A developer runs a cleanup script against what they think is the test environment. It’s the same AWS account as production. The script doesn’t know the difference.

You can guess the rest.

This kind of mistake rarely comes from bad engineers. It comes from bad boundaries. When development, testing, and production all share one AWS account, one wrong command, one leaked key, or one overly generous permission can reach everything.

The fix isn’t more caution. It’s better structure. And AWS gives you the tools to build it.

What you’ll walk away with


What is an AWS account?

An AWS account is a container for AWS resources, with its own:

Each account has a 12-digit account ID. Treat it as an identifier, not a secret — but avoid publishing it unnecessarily.


Creating and securing an AWS account

When you sign up, AWS creates the account and its root user, identified by the email address you used.

What makes the root user special

The root user has complete, unrestricted access to the account. IAM policies inside the account can’t limit it. A small set of tasks can only be done by the root user, including:

AWS keeps the full list in the IAM documentation, and it changes over time.

Root user best practices

  1. Use a strong, unique password, ideally from a password manager.
  2. Enable MFA immediately. A hardware security key or authenticator app protects against password theft.
  3. Don’t create root access keys. If any exist, delete them.
  4. Use a shared, monitored email address for business accounts — such as a distribution list — not one person’s inbox.
  5. Don’t use the root user for daily work. Create a separate identity with appropriate permissions.
  6. Set alternate contacts for billing, operations, and security so AWS can reach the right people.

Engineer’s note: In an AWS Organization, the management account can centrally manage root access for member accounts, including removing their root credentials. That turns “protect 50 root passwords” into a much smaller problem. Check the current Organizations documentation for availability and setup.


Why multiple accounts?

As soon as more than one person or environment is involved, a single account gets risky.

Accounts are a coarse but very strong boundary. IAM permissions inside an account are fine-grained but easier to get wrong.


AWS Organizations

AWS Organizations lets you create and manage many AWS accounts centrally.

Key building blocks

An example structure

Root
├── Security OU
│   ├── Log Archive account
│   └── Security Tooling account
├── Infrastructure OU
│   └── Shared Networking account
├── Workloads OU
│   ├── NonProd OU
│   │   ├── Dev account
│   │   └── Staging account
│   └── Prod OU
│       └── Prod account
└── Sandbox OU
    └── Individual experiment accounts

Engineer’s note: Keep the management account almost empty. It can’t be restricted by SCPs, so anything running there is harder to govern. Use it for organization administration and billing only.


Service Control Policies (SCPs)

Service Control Policies set the maximum permissions available to accounts in an OU or organization.

What SCPs do — and don’t do

Think of it as two gates: an action must be allowed by both the SCPs and the identity’s IAM permissions.

Common SCP use cases

Example: restrict Regions

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "DenyOutsideApprovedRegions",
      "Effect": "Deny",
      "NotAction": [
        "iam:*",
        "organizations:*",
        "route53:*",
        "cloudfront:*",
        "support:*",
        "sts:*",
        "budgets:*",
        "ce:*",
        "health:*"
      ],
      "Resource": "*",
      "Condition": {
        "StringNotEquals": {
          "aws:RequestedRegion": ["eu-west-1", "eu-central-1"]
        }
      }
    }
  ]
}

The NotAction list exempts global services and billing tools such as Budgets and Cost Explorer, which run from us-east-1 and would otherwise break — including the budget alerts you’ll set up in Part 5. This is a simplified example. AWS publishes a more complete version in the Organizations documentation; start from that before using one in a real organization.

Warning: A badly written SCP can lock every account in an OU out of critical actions. Test SCPs on a sandbox OU first.

Other organization policy types

SCPs are the best known, but Organizations supports other policy types too. Two worth knowing early:


Consolidated billing

Every organization uses consolidated billing:


AWS Control Tower and landing zones

A landing zone is a pre-configured, secure, multi-account environment that follows best practices — the “ground” new workloads land on.

You could build one manually with Organizations, IAM Identity Center, CloudTrail, and AWS Config. AWS Control Tower automates it.

What Control Tower sets up

Should you use Control Tower?


A practical environment layout

For a team building the platform in this series:

Engineer’s note: Not every organization needs separate Test and Staging accounts. The principle matters more than the exact count: production must be isolated, and changes to it should flow through automation.


Common mistakes


Key takeaways


Quick self-check

Test yourself before moving on:

  1. Can a Service Control Policy grant permissions?
  2. Does an SCP restrict users and roles in the management account?
  3. Name two tasks that require the root user.
  4. Why should the management account stay almost empty?

Answers

  1. No. SCPs only set the maximum permissions. An identity still needs an IAM policy that allows the action.
  2. No. SCPs apply only to member accounts.
  3. Any two of: changing the root email address or password of a standalone account, closing a standalone account, restoring IAM permissions after the only admin is locked out, or enabling MFA delete on an S3 bucket.
  4. Because SCPs can’t restrict it, anything running there is harder to govern — and the account controls your entire organization.

What’s next

In Part 4, we tackle the topic that worries most new AWS users: cost. We’ll cover pricing models, the Free Tier, the tools that keep your bill predictable, and AWS Support plans.

Do you use one AWS account or many? What made you switch? Tell me in the comments.


Share this article

LinkedIn post draft