Skip to main content
Five Steps for Cloud Compliance Readiness·A practical playbook for security teamsDownload
CIS Amazon Web Services Foundations v7.0.0 · 2.1.3

The AWS Organizations management account should not run workloads

  • Level 2

This check looks at whether the account that manages your AWS Organization also hosts application resources such as servers, databases or storage. The safe setting is to keep the management account for organization administration only and run workloads in separate member accounts.

Why it matters

The management account has powers that member accounts do not: it creates and closes accounts, and it manages the organization's policies and consolidated billing. Service control policies do not restrict it. Any workload placed there widens the group of people and software with a foothold in the most privileged account you have, and a mistake in that workload can affect the whole organization.

Keeping the account empty also makes it easier to protect: you can limit sign-in to a handful of named administrators, require strong authentication for each of them, and watch its activity closely because almost everything that happens there should be rare and deliberate.

AWS recommends this separation in Best practices for the management account.

How to check it yourself

Console path: AWS Organizations, AWS accounts, note which account is marked as the management account. Then sign in to that account and look for resources in Amazon EC2, Amazon RDS, Amazon S3 and similar services, in every Region you use.

Read-only AWS CLI commands, run with credentials of the management account:

aws organizations describe-organization --query "Organization.ManagementAccountId"
aws resourcegroupstaggingapi get-resources --query "ResourceTagMappingList[].ResourceARN" --region eu-west-1
aws ec2 describe-instances --query "Reservations[].Instances[].InstanceId" --region eu-west-1

Repeat the last two for each Region. They only list resources. A short list limited to organization or billing items is the expected result.

How to fix it

Console steps: create or pick a member account for the workload (AWS Organizations, AWS accounts, Add an AWS account), rebuild or migrate the resources there, confirm everything works, then delete the originals from the management account.

Script to create a member account for the workload (replace the placeholders):

aws organizations create-account --email "<unique-mailbox>" --account-name "workloads-prod"
aws organizations list-accounts --query "Accounts[].{id:Id,name:Name,status:Status}" -o table

Moving the actual resources depends on the service, for example copying S3 objects or restoring snapshots into the new account. ConfigCobra itself only reads your AWS accounts and suggests the fix; it never changes them.

What changes when you fix it

Teams that owned the moved workloads get a new account to sign in to, new IAM roles and, in many cases, new resource identifiers and endpoints, so DNS records, connection strings and cross-account permissions need updating. Costs stay on the same consolidated bill but appear under a different account, which can change how chargeback reports read. Plan a maintenance window for databases and stateful services, and keep the old resources until the new ones are verified. Once the move is finished, the management account has far fewer users and roles, which makes its access easier to review.

ConfigCobra's remediation impact analysis lists the affected resources and identities before you apply a fix.

Included in

BenchmarkCIS IDProfile
CIS Amazon Web Services Foundations v7.0.02.1.3Level 2

Check this on your AWS

ConfigCobra runs this check with every other control of the CIS Amazon Web Services Benchmarks, read-only.

Get in touch

Let's talk.

Whether you're evaluating ConfigCobra, running an audit, or managing a client fleet — we respond within one business day.

Free trial