Organizational units should be structured by environment and sensitivity
This check looks at how accounts are grouped into organizational units (OUs) in AWS Organizations. The safe setting is an OU layout that separates environments and workloads of different sensitivity, so that guardrails can be applied to each group as a whole.
Why it matters
In AWS Organizations, policies such as service control policies attach to the root, to an OU or to a single account, and apply to everything beneath. AWS's guidance on organizing your environment recommends grouping accounts by function and by the controls they need rather than mirroring your reporting chart.
If production and experimental accounts share an OU, any restriction strict enough for production blocks the experiments, and one loose enough for the experiments weakens production.
Source: AWS documentation, Organizing Your AWS Environment Using Multiple Accounts and Managing organizational units.
How to check it yourself
Sign in to the management account and open AWS Organizations > AWS accounts. Expand the OU tree and see whether accounts sit in OUs that reflect environment or sensitivity, or whether most sit directly under the root.
A read-only listing with the AWS CLI:
ROOT=$(aws organizations list-roots --query 'Roots[0].Id' --output text)
aws organizations list-organizational-units-for-parent --parent-id "$ROOT"
aws organizations list-accounts-for-parent --parent-id "$ROOT"Accounts returned for the root itself are not in any OU.
How to fix it
Plan the layout, then move accounts one group at a time:
- In AWS Organizations choose Actions > Create new under the root to add OUs such as production, non-production and sensitive workloads.
- Select an account and choose Move to place it in the right OU.
- Attach policies to OUs rather than to individual accounts.
The same with the CLI, using placeholder IDs:
aws organizations create-organizational-unit --parent-id r-examplerootid --name Production
aws organizations move-account --account-id 111122223333 --source-parent-id r-examplerootid --destination-parent-id ou-examplerootid-exampleouidConfigCobra never makes these changes for you: it reports the finding and suggests the steps.
What changes when you fix it
An account that moves immediately inherits the policies of its new OU and stops inheriting those of the old one. A service control policy on the destination can block actions the account's roles used to perform, and a policy it no longer inherits can open actions that were blocked.
Review the policies attached to the destination OU before each move, and move low-risk accounts first. Account owners and the teams that run workloads in them are the people affected, so tell them before a move and keep a note of the old parent in case you need to move the account back.
Included in
| Benchmark | CIS ID | Profile |
|---|---|---|
| CIS Amazon Web Services Foundations v7.0.0 | 2.1.4 | Level 2 |
Check this on your AWS
ConfigCobra runs this check with every other control of the CIS Amazon Web Services Benchmarks, read-only.