Implement Multi-Account and Organizational Unit (OU) Structure
Specification & Description
Establish a standardized multi-account and Organizational Unit (OU) hierarchy in AWS Organizations (with All Features enabled) to isolate security, infrastructure, and application workloads and scope SCP, RCP, and Tag Policy inheritance.
Technical Specifications
AWS Organizations requires FeatureSet ALL before you can attach Service Control Policies (SCPs), Resource Control Policies (RCPs), or Tag Policies. OUs can nest up to five levels deep under Root, each member account resides in one parent OU, and the Management account always remains directly under Root. Separating concerns across dedicated accounts and functional OUs aligns your landing zone with the AWS Security Reference Architecture (SRA):
- Management Account (Root): Organization control plane and consolidated billing only, with zero application workloads.
- Log Archive Account (Security OU): Centralized, immutable storage for organization audit and network logs.
- Security Tooling Account (Security OU): Delegated administrator for GuardDuty, Security Hub, AWS Config, and IAM Access Analyzer.
- Network Account (Infrastructure OU): Centralized Transit Gateway, Network Firewall, Route 53 Resolver, and VPC IPAM.
- Shared Services Account (Infrastructure OU): Shared CI/CD runners, golden AMIs, and directory services.
- Workload Accounts (Workloads OU split into Production and Non-Production, plus Sandbox, PolicyStaging, and Suspended OUs): Isolated per-team or per-application accounts.
Security Rationale
An AWS account is the strongest native isolation boundary for IAM permissions, service quotas, and billing, while policy inheritance follows the OU tree. Grouping dedicated platform and workload accounts into functional OUs limits incident blast radius, supports delegated administration, and prevents over-permissive production or over-restrictive sandbox guardrails.
Business & Security Impact
Running shared tooling, logging, and workloads in a small set of flat accounts or leaving member accounts directly under Root blurs administrative boundaries, increases lateral movement risk during a compromise, and forces frequent per-account policy exceptions.
Operational & Implementation Notes
Keep the OU hierarchy shallow (two to three levels) aligned to policy boundaries rather than transient org charts. Including RESOURCE_CONTROL_POLICY in enabled_policy_types on aws_organizations_organization requires Terraform AWS Provider 5.76.0 or later.
Related Controls & Guardrails (7)
Compliance Framework Mappings (5)
Regulatory baselines and industry standards mapped to this control specification.
| Framework / Standard | Mapped Requirements & Controls | Controls |
|---|---|---|
NIST 800-53 Rev 5NIST 800-53 | AC-2AC-3AC-4CM-2SC-7 | 5 |
ISO 27001:2022ISO 27001 | A.5.15A.8.9A.8.22 | 3 |
PCI DSS v4.0PCI DSS | 2.2.17.2.1 | 2 |
SOC 2SOC 2 | CC6.1CC6.3CC6.6 | 3 |
AWS Foundational Security Best PracticesAWS FSBP | Account.2 | 1 |
* Compliance framework mappings are provided for informational architectural reference. Always verify control alignment against your organization's formal audit requirements.
Automated Detection & Rule Logic
Detection Engine: aws-api • Automated: Yes
Query describe-organization to confirm FeatureSet is ALL, list OUs under Root, inspect accounts directly under Root and across OUs via list-accounts-for-parent and list-accounts to verify member accounts sit in designated OUs rather than Root, and confirm delegated administrators are registered for security and infrastructure services. Required IAM permissions: organizations:DescribeOrganization, organizations:ListRoots, organizations:ListOrganizationalUnitsForParent, organizations:ListAccounts, organizations:ListAccountsForParent, and organizations:ListDelegatedAdministrators.
Remediation Guide & Automation
Enable AWS Organizations with FeatureSet ALL, create foundational (Security, Infrastructure), workload (Production, Non-Production), Sandbox, PolicyStaging, and Suspended OUs, provision dedicated core accounts, move all member accounts out of Root into their target OUs, and register delegated administrators. Required IAM permissions: organizations:CreateOrganization, organizations:DescribeOrganization, organizations:EnableAllFeatures, organizations:ListRoots, organizations:ListOrganizationalUnitsForParent, organizations:CreateOrganizationalUnit, organizations:CreateAccount, organizations:ListAccountsForParent, organizations:MoveAccount, and organizations:RegisterDelegatedAdministrator.
Step-by-Step Instructions
- Confirm AWS Organizations runs with FeatureSet ALL so SCPs, RCPs, and Tag Policies are supported.
- Create the Security OU and provision dedicated Log Archive and Security Tooling accounts.
- Create the Infrastructure OU and provision dedicated Network and Shared Services accounts.
- Create the Workloads OU (with nested Production and Non-Production OUs) alongside Sandbox, PolicyStaging, and Suspended OUs.
- Move all member accounts out of Root into their designated OUs, register Security Tooling and Network delegated administrators, and attach baseline policies per OU.