Study guide

1.2 AWS Organizations, SCPs, and Multi-Account Strategy

AWS Solutions Architect Associate SAA-C03

Track your progress as you read

Finished sections get a check mark.

1 Introduction

About the AWS Solutions Architect Associate (SAA-C03) Exam Study Strategies and Exam Tips for SAA-C03 The AWS Well-Architected Framework

2 Domain 1: Design Secure Architectures (30%)

1.1 IAM Fundamentals — Users, Groups, Roles, and Policies 1.2 AWS Organizations, SCPs, and Multi-Account Strategy 1.3 VPC Security — Security Groups, NACLs, and VPC Endpoints 1.4 Encryption, KMS, and Secrets Management 1.5 AWS WAF, Shield, and Network Firewall 1.6 GuardDuty, Inspector, Macie, and Security Hub 1.7 The Shared Responsibility Model for Solutions Architects 1.8 Data Protection, Compliance, and Audit Services

3 Domain 2: Design Resilient Architectures (26%)

2.1 Elastic Load Balancing (ELB) — ALB, NLB, and GWLB 2.2 EC2 Auto Scaling — Dynamic, Predictive, and Scheduled 2.3 Multi-AZ and Multi-Region Architectures 2.4 Disaster Recovery Strategies — RTO and RPO 2.5 Decoupling with SQS, SNS, and EventBridge 2.6 AWS Step Functions and Workflow Orchestration

4 Domain 3: Design High-Performing Architectures (24%)

3.1 EC2 Instance Types, Purchasing Options, and Placement Groups 3.2 Lambda, Serverless Compute, and Container Services 3.3 Amazon S3 - Storage Classes, Lifecycle, and Performance 3.4 Block and File Storage - EBS, EFS, and FSx 3.5 Database Services - RDS, Aurora, DynamoDB, and More 3.6 CloudFront, Route 53, and Global Accelerator 3.7 Data Ingestion and Transformation - Kinesis, Glue, and EMR

5 Domain 4: Design Cost-Optimized Architectures (20%)

4.1 Compute Cost Optimization — Right-Sizing, RIs, Savings Plans, and Spot 4.2 Storage Cost Optimization — S3 Tiers, EBS, and Data Transfer 4.3 Database Cost Optimization 4.4 AWS Cost Management and Monitoring Tools

6 VPC and Networking Deep Dive

5.1 VPC Architecture — Subnets, Route Tables, and Gateways 5.2 VPC Connectivity — Peering, Transit Gateway, and Direct Connect 5.3 Amazon API Gateway 5.4 CloudFormation and Infrastructure as Code 5.5 AWS PrivateLink and Endpoint Services

7 Migration, Transfer, and Hybrid Services

6.1 The 7 Rs of Cloud Migration 6.2 AWS Snow Family — Snowball Edge Devices 6.3 CloudWatch, CloudTrail, and AWS Config 6.4 Amazon Cognito and Identity Federation 6.5 AWS DataSync and Transfer Family

8 Serverless Architecture and Application Services

7.1 Serverless Architecture Patterns 7.2 Advanced SQS Patterns — DLQ, Backpressure, and FIFO 7.3 Analytics Services — Athena, OpenSearch, and QuickSight 7.4 Container Orchestration — ECS, EKS, and ECR

9 Advanced Topics and Exam Scenarios

8.1 Advanced IAM — Permission Boundaries, Federation, and Cross-Account 8.2 Caching Strategies and ElastiCache Patterns 8.3 Hybrid Architecture — DNS, Storage, and Compute 8.4 SAA-C03 Scenario Practice — Putting It All Together

1.2 AWS Organizations, SCPs, and Multi-Account Strategy

Key Takeaways Explain This Topic AI

AWS Organizations consolidates multiple accounts into a hierarchy of Organizational Units (OUs) with consolidated billing.

Service Control Policies (SCPs) set maximum-permission guardrails at the OU or account level — they restrict, never grant.

SCPs never affect the management (payer) account — only member accounts are subject to them.

AWS Control Tower automates landing zones, guardrails, and account vending on top of Organizations.

A multi-account strategy delivers blast-radius isolation, security boundaries, and clean cost attribution.

Last updated: October 2026

Quick Answer: AWS Organizations governs many accounts from one management account. Service Control Policies (SCPs) set the maximum permission ceiling for member accounts — they only restrict, never grant, and they never touch the management account. AWS Control Tower automates the whole landing zone. Use a multi-account design to isolate blast radius and simplify billing.

AWS Organizations

AWS Organizations is a free governance service that groups accounts into an organization rooted at a single management (payer) account . Accounts are arranged in Organizational Units (OUs) — a tree up to five levels deep below the root.

Feature What It Delivers

Consolidated billing One invoice; volume tiers and Reserved Instance / Savings Plan discounts shared across accounts

  • Organizational Units Hierarchical grouping (Prod OU, Dev OU, Security OU)
  • Service Control Policies Permission guardrails attached to root, OUs, or accounts
  • Programmatic accounts CreateAccount API and Account Factory provisioning
  • Resource sharing Cross-account sharing via AWS Resource Access Manager (RAM) Root (Management Account)
  • ├── Security OU
  • │ ├── Log Archive Account
  • │ └── Security Tooling Account
  • ├── Production OU
  • │ ├── Prod-App-A └── Prod-App-B
  • ├── Development OU
  • │ └── Dev-Sandbox
  • └── Suspended OU (quarantine)

A recommended pattern keeps a dedicated Log Archive and Security Tooling account in a Security OU so audit logs are isolated from workload accounts.

Service Control Policies (SCPs)

SCPs define the maximum set of permissions for principals in member accounts. They are a ceiling, not a grant — an action still needs an IAM Allow to actually run.

SCP Rules to Memorize

  • Rule Why It Matters on the Exam
  • SCPs restrict , never grant A user with an SCP-only setup can do nothing
  • Management account is immune SCPs apply to member accounts only — never the payer
  • Apply to all member-account principals Includes each member account's root user, but not service-linked roles
  • Deny beats any IAM Allow The standard explicit-deny precedence
  • FullAWSAccess is attached by default Remove or replace it to start denying

SCPs come in two strategies: deny lists (allow everything, then explicitly deny — the default starting point) and allow lists (deny everything, then explicitly allow only approved services).

  • Region-Restriction SCP (classic question) {
  • "Version": "2012-10-17",
  • "Statement": [{
  • "Sid": "DenyNonApprovedRegions",
  • "Effect": "Deny",
  • "Action": "*",
  • "Resource": "*",
  • "Condition": { "StringNotEquals": {
  • "aws:RequestedRegion": ["us-east-1", "us-west-2", "eu-west-1"]
  • }}
  • }]
  • }

On the Exam: "Prevent member accounts from launching resources outside approved Regions" or "block any instance type larger than t3.large " → an SCP on the relevant OU. AWS Config rules are detective (they flag drift after the fact); SCPs are preventive .

AWS Control Tower

AWS Control Tower sits on top of Organizations and automates a best-practice landing zone .

  • Capability Detail
  • Landing zone Preconfigured multi-account baseline (management, log archive, audit)

Guardrails / Controls Preventive (SCPs) and detective (AWS Config rules); also proactive (CloudFormation hooks)

  • Account Factory Self-service, policy-compliant account vending
  • Dashboard Org-wide compliance and drift visibility

Use Organizations alone when you need only basic consolidated billing and a few SCPs; choose Control Tower when you want an automated, audited landing zone with account vending.

Multi-Account Strategy Benefits

  • Benefit Explanation
  • Security isolation A compromised account cannot reach the others
  • Blast-radius reduction A bad deploy is contained to one account
  • Cost attribution Per-team / per-project spend is unambiguous
  • Independent quotas Each account has its own service limits
  • Compliance segmentation PCI workloads sit in their own controlled account

Common trap: SCPs do not replace IAM. A new account with a restrictive SCP and no IAM policies still cannot do anything — both layers must allow.

SCP Inheritance and Evaluation

SCPs are inherited down the OU tree, and the effective permission set at any account is the intersection of every SCP from the root down to that account, then intersected with IAM. Picture an account three levels deep: if the root SCP allows services A, B, and C, the parent OU's SCP allows only A and B, and the account-level SCP allows only A, then the account can use only service A — and even then only where IAM also allows it. This is why an over-tight SCP high in the tree can silently break every account beneath it, a frequent troubleshooting scenario ("users suddenly lost access in all accounts after an SCP change at the root").

A second subtlety: SCPs limit only the IAM users and roles in the organization's member accounts. They don't restrict users or roles from accounts outside the organization, even when a resource-based policy (such as a bucket policy) in a member account grants them access, and they don't apply to service-linked roles. They also never restrict the management account, which is the deliberate escape hatch that keeps you from locking yourself out of the entire organization.

Cross-Account Access Patterns

Multi-account designs need controlled cross-account access. The two exam-favored mechanisms are IAM roles assumed via sts:AssumeRole (a workload in account A assumes a role in account B) and AWS Resource Access Manager (RAM) for sharing actual resources such as subnets, Transit Gateways, and License Manager configurations. A shared-services account commonly hosts central networking and shares its VPC subnets to workload accounts through RAM, avoiding duplicate VPCs.

Tagging, Cost, and Governance Glue

A mature organization layers complementary services on top of the account structure:

  • Service Role in a Multi-Account Org
  • Consolidated billing One payer; shared volume and commitment discounts
  • AWS Config aggregator Org-wide configuration and drift visibility
  • CloudTrail organization trail Single immutable audit trail across all accounts
  • Tag policies Enforce consistent cost-allocation tags
  • Backup policies Centrally mandate AWS Backup plans

Exam framing: When a prompt mixes "central governance," "consistent guardrails," and "automated new-account provisioning," the layered answer is Organizations (structure) + SCPs (guardrails) + Control Tower (automation) — not a single service doing everything.