AWS · Editable reference architecture
AWS landing zone architecture
An editable aws landing zone architecture reference showing Identity center → Account factory → Workload accounts. Govern identity, logging and connectivity across account boundaries.
Open & Edit in DrawArc (Free, No Login Required)Your changes stay in a separate draft on this browser. Download an editable project to keep a portable copy.

7 components · 5 connections · Open the editor to zoom, move nodes and edit source.
Architectural overview
AWS landing zone architecture addresses the responsibilities and boundaries shown in this reference rather than prescribing an entire production deployment. The primary flow starts at Identity center and reaches Workload accounts through Account factory. Use this view to explain which component initiates work, which component owns a decision, and where a dependency can affect the caller. Govern identity, logging and connectivity across account boundaries.
The diagram contains 7 distinct components and 5 directed relationships. A separate path connects Workload accounts → Log archive account. A separate path connects Security account → Workload accounts. A separate path connects Network account → Transit Gateway. These arrows describe logical interactions; they do not establish authentication, network access, atomic transactions or delivery guarantees. Label the actual protocol, payload contract and owner when adapting the drawing to your system. Keep synchronous and asynchronous boundaries explicit so that a reviewer can identify where a request ends and a later operation begins.
Before implementing this architecture, define expected load, data classification, latency budgets and recovery objectives. Give Account factory a bounded dependency timeout and a documented failure response. For Log archive account, specify ownership, retention, access control and a tested recovery procedure. Validate the decision above against your workload instead of treating the presence of a component as proof of reliability. Open the editable canvas, replace generic labels with real deployment units, and document the decisions that differ from this reference.
The real-world problem
Design or explain aws landing zone architecture with explicit ownership and dependency paths. Govern identity, logging and connectivity across account boundaries.
Data flow
Connections from this diagram. Branches and control signals are not a single chronological sequence.
- Identity center → Account factory. Define the interaction contract and trace the resulting response or state change.
- Account factory → Workload accounts. Define the interaction contract and trace the resulting response or state change.
- Workload accounts → Log archive account. Define the interaction contract and trace the resulting response or state change.
- Security account → Workload accounts. Define the interaction contract and trace the resulting response or state change.
- Network account → Transit Gateway. Define the interaction contract and trace the resulting response or state change.
Security boundaries
- Authenticate callers at the boundary before Account factory accepts protected work; authorize the specific operation rather than trusting network placement.
- Use separate service identities and least-privilege permissions for Account factory, Workload accounts, Log archive account. Encrypt sensitive traffic, protect credentials and avoid placing confidential payloads in logs.
- Restrict and audit access to Log archive account; define retention and deletion requirements for the actual data.
Failure handling
Account factory is unavailable or slow
Response: Apply bounded timeouts and controlled backoff only where retrying is safe. Return an explicit failure or durable acceptance; do not report success before required work is committed.
Verify: Interrupt Account factory in an isolated test and measure errors, recovery and any repeated side effects.
Log archive account loses or returns stale state
Response: Use workload-specific durability, reconciliation and tested recovery. Specify how stale reads or a failed write affect callers.
Verify: Exercise the failure path with representative records and verify both the visible response and the resulting state.
An invalid or incompatible input reaches Account factory
Response: Validate the input contract before effects are committed. Preserve rejected input identifiers without exposing secrets, and document a safe replay or correction procedure.
Verify: Send malformed and older-version inputs through Identity center and verify rejection, observability and unchanged valid state.
Trade-offs and alternatives
Govern identity, logging and connectivity across account boundaries.
- Benefit
- Makes the ownership and interaction boundaries visible for a focused design review.
- Cost
- The 7 illustrated components still require contracts, monitoring and operational ownership; extra boundaries can add latency and failure modes.
- Alternative
- Use a simpler deployment when it meets the same requirements, or split a boundary only after measuring a specific need.
Logical boundaries versus deployment units in AWS landing zone architecture
- Benefit
- Keeps the responsibilities of Identity center, Account factory, Workload accounts visible without requiring a separate server for each box.
- Cost
- A logical view does not establish isolation, independent scaling or high availability; those require a separate deployment design and operational tests.
- Alternative
- Co-locate components in a simpler deployment first when ownership and workload requirements permit it.
When to use this architecture
- Explain aws landing zone architecture to engineers or stakeholders using a concrete visual flow.
- Review this decision before deployment: Govern identity, logging and connectivity across account boundaries.
- Adapt a starting diagram for your own requirements, then record and validate every changed boundary.
Key components
- Identity center
- Identity center participates in aws landing zone architecture. Identity center → Account factory. Define its contract, owner and access permissions in your implementation.
- Account factory
- Account factory participates in aws landing zone architecture. Identity center → Account factory; Account factory → Workload accounts. Define its contract, owner and access permissions in your implementation.
- Workload accounts
- Workload accounts participates in aws landing zone architecture. Account factory → Workload accounts; Workload accounts → Log archive account; Security account → Workload accounts. Define its contract, owner and access permissions in your implementation.
- Log archive account
- Log archive account participates in aws landing zone architecture. Workload accounts → Log archive account. Define its contract, owner and access permissions in your implementation.
- Security account
- Security account participates in aws landing zone architecture. Security account → Workload accounts. Define its contract, owner and access permissions in your implementation.
- Network account
- Network account participates in aws landing zone architecture. Network account → Transit Gateway. Define its contract, owner and access permissions in your implementation.
- Transit Gateway
- Transit Gateway participates in aws landing zone architecture. Network account → Transit Gateway. Define its contract, owner and access permissions in your implementation.
Questions about this template
What does this aws landing zone architecture diagram show?
It shows 7 components with the core flow Identity center → Account factory → Workload accounts. Govern identity, logging and connectivity across account boundaries.
Can I edit this diagram without signing in?
Yes. Open the template in the browser-local canvas to change nodes, connections and source. AI generation and cloud account storage require sign-in.
Is this a complete production implementation?
No. It is an editable reference. Validate the security controls, dependency behavior, capacity and recovery plan against your own requirements before implementation.
Validate your implementation
Use the relevant platform documentation to verify service limits, supported features and configuration. This diagram is an original reference rather than a reproduction of a provider deployment.