Organization Structure
A well-designed organizational unit (OU) hierarchy enables you to apply policies at the right level of granularity.Recommended OU Structure
Design Principles
- Separate security from workloads: Security accounts (audit, log archive) should be in their own OU with strict SCPs.
- Environment isolation: Production, staging, and development workloads in separate OUs allow different policy sets.
- Sandbox for experimentation: Give developers a safe space with spend limits but relaxed controls.
- Suspended OU: Move accounts here before deletion to ensure all SCPs deny actions while you audit.
Enabling Organization Features
Ensure your organization has all features enabled (not just consolidated billing):"FeatureSet": "ALL". If you see "CONSOLIDATED_BILLING", enable all features:
Service Control Policies (SCPs)
SCPs are the primary governance mechanism. They define the maximum permissions available to accounts within an OU.Common SCPs
SCP Best Practices
- Start with a deny-list approach: allow everything by default, explicitly deny what’s not permitted.
- Test SCPs in the Sandbox OU before rolling to production.
- Never attach restrictive SCPs directly to the root — use OUs for granularity.
- Keep the management account free of restrictive SCPs (it is always exempt from SCPs by design, but avoid confusion).
Delegated Administrators
Delegate service administration to member accounts so the management account remains minimal:Tag Policies
Enforce consistent tagging across all accounts:Trusted Access
Enable trusted access for AWS services that need organization-wide visibility:- AWS CloudFormation StackSets
- AWS Config
- AWS CloudTrail (organization trail)
- AWS Backup
- AWS RAM (Resource Access Manager)
Consolidated Billing & Cost Allocation
- Enable Cost Allocation Tags in the management account billing console.
- Use AWS Cost Explorer for cross-account cost visibility.
- Set up AWS Budgets at both the organization and individual account levels.

