INFRASTRUCTURE LEARNINGINFRASTRUCTURE LEARNING
インフラ大全インフラ大全IT INFRASTRUCTURE / LEARNING
Infrastructure learning guide
Find a lesson or lab/

Esc to close · Search terms stay on your device

LEARNING日本語

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.

What you will learn

Separate production, development and audit responsibilities in a fictional organization.

Prerequisite

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.

Choose where each responsibility belongs
Choose where each responsibility belongs1: Requirements — Set boundaries — Organization root. 2: Organization root — Group accounts — OU. 3: OU — Place each workload — Account123RequirementsOrganization rootOUAccountChoose where each responsibility belongs1: Requirements — Set boundaries — Organization root. 2: Organization root — Group accounts — OU. 3: OU — Place each workload — Account123RequirementsOrganizationrootOUAccount
  1. Requirements → Organization rootSet boundaries
  2. Organization root → OUGroup accounts
  3. 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

A fictional delivery business separates development testing from production.
ResponsibilityPlacementReason
Production orders APIWorkload account in production OULimit production operations and permissions
Development testingDevelopment account in test OUExercise different rules
Audit log storageAudit-side accountSeparate storage from workload ownership
Organization settingsManagement accountReserve 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.

Which boundary separates resources and permissions for production and testing?
Read the answer and reason

Answer: An AWS account · Use different accounts for the workload boundaries.

What should be checked before moving an account from testing to production?
Read the answer and reason

Answer: Destination policies and representative operations · Moving can change the applicable rules.

What is the organization root?
Read the answer and reason

Answer: The administrative parent of OUs and accounts · It is the top administrative container.

Check, then explain in your own words

  1. Define the boundaries.
  2. Group accounts by common policies.
  3. 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.