Topic lessonTopic: Multi-account guardrails and deployment checks
AWS Organizations design: accounts, OUs and administrative boundaries
Use OUs to group accounts that should follow the same rules. Separate production, development and audit responsibilities in a fictional organization.
Separate production, development and audit responsibilities in a fictional organization.
This is a design exercise with no live account enrollment.
Choose resource boundaries and administrative groups separately
An AWS organization has a root, organizational units and accounts. Accounts are boundaries for resources and access. OUs group accounts for administration.
- Requirements → Organization rootSet boundaries
- Organization root → OUGroup accounts
- OU → AccountPlace each workload
- Requirements
- Separate production and testing
- Organization root
- Top administrative level
- OU
- Group accounts with shared rules
- Account
- Resource and ownership boundary
Place workloads, audit and organization administration
| Responsibility | Placement | Reason |
|---|---|---|
| Production orders API | Workload account in production OU | Limit production operations and permissions |
| Development testing | Development account in test OU | Exercise different rules |
| Audit log storage | Audit-side account | Separate storage from workload ownership |
| Organization settings | Management account | Reserve for organization administration |
Organization policy scope varies by policy type. Before moving an account, check the policies that will apply in the destination hierarchy.
Check responsibilities and policies before a move
Group by purpose. Document resources, owners, costs and rules for production, testing and audit.
Compare inheritance. Read the policy types and scopes along the current and proposed paths through the root, OUs and account.
Choose representative operations. Identify workflows that must survive the move, and define recovery criteria and decision owners.
Check the worked example
Choose an option to see the result and explanation.
Check, then explain in your own words
- Define the boundaries.
- Group accounts by common policies.
- Compare operation requirements before and after a move.
Check your understanding: Can you deploy workloads directly into an OU?
Deploy into accounts, then organize accounts in OUs.
An administrative group is distinct from a resource boundary.
Sources and conditions checked
The official references used in this lesson are collected here with their scope, conditions and corresponding sections. Independent expert review and live AWS comparison have not been performed.
Scope and conditionsOrganization, root, OUs, and management and member accounts.
Used in this lessonChoose resource boundaries and administrative groups separately Place workloads, audit and organization administration Check responsibilities and policies before a move