Study guide
5.1 AWS Organizations Hierarchy, OUs & Account Provisioning
AWS Certified DevOps Engineer – Professional Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: CI/CD Pipeline Architecture & Source Integration
1.1 Multi-Stage & Multi-Account CodePipeline Design 1.2 CodeBuild Projects, Build Environments & Pipeline Secrets 1.3 Source Control Workflows, Webhooks & Branching Models
2 Chapter 2: Automated Testing, Test Gates & Quality Verification
2.1 Automated Unit, Integration & Acceptance Testing in Pipelines 2.2 Load Testing, Performance Benchmarking & Synthetic Canaries 2.3 Security Scanning, SAST/DAST & Approval Gates
3 Chapter 3: Artifact Management & Multi-Platform Deployment Strategies
3.1 Artifact Lifecycle Management with CodeArtifact, ECR & S3 3.2 Automated Image Baking with EC2 Image Builder 3.3 In-Place, Rolling & Immutable Deployments on EC2 3.4 Blue/Green & Canary Deployments for ECS, EKS & Lambda
4 Chapter 4: CloudFormation, CDK & Reusable IaC Components
4.1 Advanced CloudFormation: Nested Stacks, Change Sets & Custom Resources 4.2 Cross-Account & Multi-Region StackSets & Drift Detection 4.3 Modern IaC: AWS CDK, SAM & Service Catalog Governance
5 Chapter 5: Multi-Account Architecture, Organizations & Control Tower
5.1 AWS Organizations Hierarchy, OUs & Account Provisioning 5.2 Service Control Policies (SCPs) & Multi-Account Guardrails 5.3 AWS Control Tower, Account Factory & Landing Zone Automation
6 Chapter 6: Systems Manager & Large-Scale Fleet Configuration
6.1 SSM Agent, Hybrid Activation & Session Manager 6.2 Systems Manager Run Command, State Manager & Associations 6.3 Patch Manager, Parameter Store vs Secrets Manager & AppConfig
7 Chapter 7: High Availability & Multi-Region Resiliency
7.1 Designing Resilient Multi-AZ & Multi-Region Architectures 7.2 Route 53 Traffic Flow, Health Checks & DNS Failover 7.3 Data Replication: Aurora Global DB, DynamoDB Global Tables & S3 CRR
8 Chapter 8: Scalability, Auto Scaling & Disaster Recovery Automation
8.1 EC2 Auto Scaling Policies, Lifecycle Hooks & Warm Pools 8.2 Container & Serverless Scalability: ECS Capacity Providers, EKS & API Gateway 8.3 Disaster Recovery Strategies: RTO, RPO & Architecture Tiers 8.4 Automated Backup & Recovery with AWS Backup & Elastic Disaster Recovery
9 Chapter 9: CloudWatch Metrics, Agent Collection & Log Aggregation
9.1 CloudWatch Metrics, Dimensions, Metric Math & High Resolution 9.2 Unified CloudWatch Agent & Custom Metric Collection 9.3 Centralized Log Aggregation, Retention & Cross-Account Subscriptions
10 Chapter 10: Log Analysis, Dashboards & Distributed Tracing with X-Ray
10.1 CloudWatch Logs Insights, Filter Syntax & Query Optimization 10.2 CloudWatch Dashboards, Composite Alarms & Anomaly Detection 10.3 Distributed Tracing with AWS X-Ray & Service Maps
11 Chapter 11: Automated Observability & Event-Driven Monitoring
11.1 Application & Infrastructure Health Checks with Route 53 & ALB 11.2 Centralized Observability with Amazon OpenSearch & Athena 11.3 Synthetic Monitoring with CloudWatch Synthetics Canaries
12 Chapter 12: Event-Driven Incident Detection & Notification Pipelines
12.1 AWS Health, CloudTrail Events & Operational Notification 12.2 EventBridge Event Routing, Patterns & Multi-Account Buses 12.3 Asynchronous Event Processing: SNS, SQS Queues & Dead-Letter Handling
13 Chapter 13: Automated Remediation & Deployment Troubleshooting
13.1 AWS Config Managed Rules & Automated Remediation with SSM 13.2 Event-Driven Infrastructure Self-Healing with Lambda & Step Functions 13.3 Troubleshooting CI/CD Pipeline & Deployment Failures 13.4 Root Cause Analysis for Auto Scaling & Container Failures
14 Chapter 14: Identity, Access Management & Secrets at Scale
14.1 IAM Policy Evaluation Logic, NotAction & Explicit Denies 14.2 IAM Permissions Boundaries & Delegated Administration 14.3 IAM Identity Center, Cross-Account Roles & STS Session Policies 14.4 Automated Secrets Management & Secret Rotation with Secrets Manager
15 Chapter 15: Security Automation, Data Protection & Compliance Auditing
15.1 Network Security Automation: Security Groups, NACLs, Network Firewall & WAF 15.2 Cryptographic Controls & Key Management with AWS KMS & ACM 15.3 Automated Threat Detection: GuardDuty, Inspector & Security Hub 15.4 Continuous Compliance Auditing & Log Integrity with CloudTrail & Config
5.1 AWS Organizations Hierarchy, OUs & Account Provisioning
Key Takeaways Explain This Topic AI
AWS Organizations establishes a hierarchical tree of Organizational Units (OUs) rooted under a single Management account, enforcing structural blast radius isolation across security, infrastructure, and workload domains.
Production-grade AWS landing zones decouple critical operational capabilities into dedicated accounts: Log Archive (immutable centralized storage) and Security Tooling (delegated administrator for GuardDuty, Security Hub, and Macie).
Automated account creation leverages the asynchronous CreateAccount API, tracking execution state via EventBridge events or Step Functions to orchestrate immediate OU assignment and baseline resource deployment.
When an account is created natively via Organizations, AWS automatically provisions the OrganizationAccountAccessRole with AdministratorAccess; invited existing accounts do not automatically inherit this role.
Beyond authorization guardrails, AWS Organizations centrally governs environments using Tag Policies for resource taxonomy, Backup Policies for centralized AWS Backup orchestration, and AI Service Opt-Out Policies for enterprise data privacy.
Last updated: September 2026
Enterprise Multi-Account Architecture Principles
In modern cloud engineering, managing an enterprise footprint within a single AWS account is considered an anti-pattern. As organizations scale, a single account inevitably encounters hard AWS service quotas (such as API rate limits, VPC limits, and IAM policy size constraints), monolithic blast radiuses where a security compromise affects all environments, and complex, error-prone IAM permission boundaries.
AWS Organizations solves these structural challenges by consolidating multiple AWS accounts into an administratively unified tree structure governed by programmatic policies and centralized billing.
The Need for Multi-Account Isolation
Blast Radius Containment: A security compromise, credential leak, or catastrophic operational misconfiguration (such as a destructive deployment script) in a development account remains physically isolated from production workloads and sensitive corporate data.
Granular Security and Compliance Boundaries: Highly regulated environments (such as PCI-DSS cardholder data environments or HIPAA health records) can be segregated into dedicated accounts subject to strict audit trails, dedicated encryption keys, and immutable logging.
Independent Service Quotas: AWS API rate limits (such as CloudFormation deploy calls, EC2 instance launch limits, and Route 53 queries) apply per account per region. Multi-account partitioning prevents noisy neighbor workloads in development or testing from starving production pipelines.
Precise Cost Allocation: While bills are aggregated centrally for volume discounts, individual member accounts provide definitive attribution of infrastructure expenditure to distinct cost centers, business units, or engineering squads without complex tagging heuristics.
Recommended AWS Organizations Hierarchy
AWS Well-Architected multi-account guidance recommends organizing accounts into functional Organizational Units (OUs) rather than mirroring corporate reporting structures. The hierarchy branches beneath a single Root container. [ Organizations Root ]
- │
- ┌───────────────────┬────────────────┴────────────────┬───────────────────┐
- ▼ ▼ ▼ ▼
- [ Security OU ] [ Infrastructure OU ] [ Workloads OU ] [ Sandbox OU ]
- ├─ Log Archive ├─ Network Account ├─ Dev Accounts └─ Isolated R&D
- └─ Security Tool └─ Shared Services / Tools ├─ Test Accounts
- └─ Prod Accounts
- Core Organizational Units and Account Roles
Organizational Unit (OU) Dedicated Account Core Responsibilities & Delegated Administration
Management Account (Root) Organization Root Account creation, billing consolidation, payment methods, organization-wide policy attachment (SCPs, Tag Policies). Exam Rule: Never run application workloads or development tasks in the Management account.
Security OU Log Archive Account Ingests and stores centralized, immutable copies of all AWS CloudTrail organization trails, Amazon VPC Flow Logs, AWS Config logs, and Route 53 resolver query logs. Protected by S3 Object Lock and strict bucket policies prohibiting deletion even by administrators.
Security OU Security Tooling (Audit) Acts as the Delegated Administrator for centralized security services: AWS Security Hub, Amazon GuardDuty, AWS IAM Identity Center, AWS CloudTrail, Amazon Macie, and Amazon Inspector. Dedicated incident responders conduct forensic investigations here without accessing workload accounts directly.
Infrastructure OU Network Account Manages external and cross-account connectivity: AWS Transit Gateway, AWS Network Firewall, Route 53 private hosted zones and inbound/outbound resolvers, AWS Direct Connect gateways, and centralized NAT Gateways.
Infrastructure OU Shared Services / Tools Hosts centralized CI/CD pipelines (AWS CodePipeline, Jenkins), shared container image registries (Amazon ECR), internal artifact repositories (AWS CodeArtifact), and central identity directory connectors.
Workloads OU Dev / Test / Prod Accounts Dedicated accounts hosting operational microservices, applications, and databases. Nested child OUs (or separated peer OUs) isolate lifecycle environments to prevent pre-production changes from impacting live traffic.
Sandbox OU R&D / Experimentation Ephemeral, detached accounts granted to developers for prototyping. Detached from corporate VPCs and internal networks, governed by rigid spend limits, and subjected to automated nightly resource teardown routines.
Automated Account Provisioning and Onboarding
Manually clicking through the AWS Management Console to provision accounts does not scale and introduces human configuration errors. Enterprise DevOps requires continuous, programmatic account provisioning.
The CreateAccount API Mechanics
The AWS Organizations CreateAccount API creates a new member account that automatically joins the organization:
Asynchronous Execution: Calling aws organizations create-account --email dev-team@corp.internal --account-name "Mobile-App-Dev" initiates an asynchronous workflow and immediately returns a CreateAccountStatus object containing a unique Id (e.g., car-1234567890abcdef0 ).
Status Tracking: The status transitions through IN_PROGRESS to either SUCCEEDED or FAILED . The provisioning orchestration must poll DescribeCreateAccountStatus using the request Id , or reactively listen for state changes.
Default IAM Role: By default, AWS Organizations automatically creates an IAM role named OrganizationAccountAccessRole inside the new member account. This role grants AdministratorAccess and establishes an IAM trust relationship allowing principals in the Management account to assume it via AWS STS.
Important
DOP-C02 Exam Trap — Created vs. Invited Accounts: When an account is created using CreateAccount , AWS automatically deploys the OrganizationAccountAccessRole . However, when an existing standalone AWS account is brought into the organization via InviteAccountToOrganization , AWS does not create this role! Administrators must manually create an IAM cross-account role with trust back to the Management account, or deploy it using an onboarding script before centralized automation can manage the invited account.
Event-Driven Account Provisioning Pipeline
To enforce security baselines on newly created accounts before releasing them to engineering teams, DevOps teams construct event-driven onboarding pipelines combining Amazon EventBridge, AWS Step Functions, and AWS CloudFormation StackSets: [ Organizations: CreateAccount API ]
- │
- ▼
- [ Account Provisioned (SUCCEEDED) ]
- │
- ▼ (Emits AWS API Call via CloudTrail)
- [ Amazon EventBridge ]
- │
- ▼ (Triggers)
- [ AWS Step Functions ]
- │
- ├─ 1. MoveAccount: Relocate from Root to target Workload OU
- ├─ 2. TagResource: Apply mandatory CostCenter, Owner, and Env tags
- ├─ 3. CloudFormation StackSets: Deploy baseline VPC, IAM roles, and KMS keys
- ├─ 4. AWS Config & GuardDuty: Verify member enablement
- └─ 5. Notify Team: Send provisioning success notification via Amazon SNS
Event Capture: CloudTrail captures the completion of CreateAccount and forwards the CreateAccountResult event to Amazon EventBridge in the Management account.
State Machine Execution: An EventBridge rule detects the successful account creation and invokes an AWS Step Functions state machine.
OU Relocation: Step Functions executes an AWS Lambda task that invokes organizations:MoveAccount , specifying the AccountId , the SourceParentId (initially the Organization Root), and the DestinationParentId (e.g., the Dev-Workloads-OU ). Moving the account causes it to immediately inherit all Service Control Policies (SCPs) attached to the target OU.
Baseline StackSet Deployment: CloudFormation StackSets with automatic deployment enabled ( AutoDeployment: Enabled: true, RetainStacksOnAccountRemoval: false ) automatically detect the new account in the target OU. StackSets immediately provisions baseline infrastructure: local security groups, VPCs, IAM roles for CI/CD runners, and default Amazon EBS volume encryption ( ec2:EnableEbsEncryptionByDefault ).
Identity & Access Integration: The state machine registers the new account with AWS IAM Identity Center (AWS SSO) and assigns preconfigured permission sets to designated Active Directory / Okta groups.
Governance Beyond SCPs: Organizations Management Policies
While Service Control Policies (SCPs) restrict authorization (detailed in Section 5.2), AWS Organizations supports specialized declarative management policies to maintain corporate compliance across all member accounts.
1. Tag Policies
Tag Policies define standardized tagging rules across an organization. They enforce key-value pair conventions for metadata such as CostCenter , Environment , and ProjectOwner :
Schema Enforcement: Specifies the exact case-sensitive key name (e.g., Environment rather than environment or env ) and an allowed list of valid values (e.g., ['development', 'staging', 'production'] ).
Non-Compliance Auditing: Automatically evaluates resources across member accounts and generates non-compliance reports in the AWS Organizations console.
Preventive Enforcement: When tag enforcement is enabled for supported resource types, AWS denies any API call that attempts to create a resource or modify tags with non-compliant keys or values. {
- "tags": {
- "CostCenter": {
- "tag_key": {
- "@@assign": "CostCenter"
- },
- "tag_value": {
- "@@assign": [
- "Finance-101",
- "Engineering-202",
- "Security-303"
- ]
- },
- "enforced_for": {
- "@@assign": [
- "ec2:instance",
- "s3:bucket"
- ]
- }
- }
- }
- }
- 2. Backup Policies
Backup Policies define organization-wide AWS Backup plans deployed automatically to member accounts. Instead of each engineering team writing independent backup scripts, a centralized backup policy configures:
Resource assignment rules based on resource tags (e.g., resources tagged BackupPlan: Gold ).
Backup frequency (e.g., daily snapshots retained for 35 days).
Cross-Region and cross-account backup copies (e.g., copying snapshots to a dedicated, locked backup vault in the Log Archive or Security Tooling account for ransomware protection).
3. AI Service Opt-Out Policies
Enterprise compliance frameworks frequently prohibit cloud vendors from utilizing proprietary customer data to train artificial intelligence models. AI Service Opt-Out Policies allow organizations to opt out of having content stored or processed by AWS AI services (such as Amazon Rekognition, Amazon Transcribe, Amazon Comprehend, and Amazon Bedrock) utilized for AWS model training and quality improvement.
Consolidated Billing and Cost Governance
AWS Organizations consolidates the payment method for all member accounts into the single Management account:
Volume Tiering: Usage across all member accounts is aggregated for pricing tiers. For instance, data transferred out of Amazon S3 or EC2 across 50 member accounts is pooled, qualifying the company for higher-volume, lower-per-gigabyte pricing tiers much faster.
Savings Plans and Reserved Instance (RI) Sharing: By default, unused Reserved Instance hours and Savings Plans commitments purchased in one account apply across all eligible usage within the organization. If a business unit requires strict budget boundaries without cross-subsidization, RI discount sharing can be selectively disabled for specific member accounts.
Cost Allocation Tags: User-defined cost allocation tags activated in the Management account propagate to billing reports (AWS Cost and Usage Report - CUR) across all member accounts, providing unified spend visibility in AWS Cost Explorer.