AWS · Editable reference architecture
AWS multi account architecture
An editable aws multi account architecture reference showing Organization → Management account → Account provisioning. Keep management access separate from workload execution.
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.

6 components · 5 connections · Open the editor to zoom, move nodes and edit source.
Architectural overview
AWS multi account architecture addresses the responsibilities and boundaries shown in this reference rather than prescribing an entire production deployment. The primary flow starts at Organization and reaches Account provisioning through Management account. Use this view to explain which component initiates work, which component owns a decision, and where a dependency can affect the caller. Keep management access separate from workload execution.
The diagram contains 6 distinct components and 5 directed relationships. A separate path connects Account provisioning → Production account. A separate path connects Account provisioning → Development account. A separate path connects Production account → Central log archive. 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 Organization a bounded dependency timeout and a documented failure response. For Central log archive, 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 multi account architecture with explicit ownership and dependency paths. Keep management access separate from workload execution.
Data flow
Connections from this diagram. Branches and control signals are not a single chronological sequence.
- Organization → Management account. Define the interaction contract and trace the resulting response or state change.
- Management account → Account provisioning. Define the interaction contract and trace the resulting response or state change.
- Account provisioning → Production account. Define the interaction contract and trace the resulting response or state change.
- Account provisioning → Development account. Define the interaction contract and trace the resulting response or state change.
- Production account → Central log archive. Define the interaction contract and trace the resulting response or state change.
Security boundaries
- Authenticate callers at the boundary before Management account accepts protected work; authorize the specific operation rather than trusting network placement.
- Use separate service identities and least-privilege permissions for Management account, Account provisioning, Production account. Encrypt sensitive traffic, protect credentials and avoid placing confidential payloads in logs.
- Restrict and audit access to Central log archive; define retention and deletion requirements for the actual data.
Failure handling
Organization 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 Organization in an isolated test and measure errors, recovery and any repeated side effects.
Central log archive 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 Management account
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 Organization and verify rejection, observability and unchanged valid state.
Trade-offs and alternatives
Keep management access separate from workload execution.
- Benefit
- Makes the ownership and interaction boundaries visible for a focused design review.
- Cost
- The 6 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 multi account architecture
- Benefit
- Keeps the responsibilities of Organization, Management account, Account provisioning 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 multi account architecture to engineers or stakeholders using a concrete visual flow.
- Review this decision before deployment: Keep management access separate from workload execution.
- Adapt a starting diagram for your own requirements, then record and validate every changed boundary.
Key components
- Organization
- Organization participates in aws multi account architecture. Organization → Management account. Define its contract, owner and access permissions in your implementation.
- Management account
- Management account participates in aws multi account architecture. Organization → Management account; Management account → Account provisioning. Define its contract, owner and access permissions in your implementation.
- Account provisioning
- Account provisioning participates in aws multi account architecture. Management account → Account provisioning; Account provisioning → Production account; Account provisioning → Development account. Define its contract, owner and access permissions in your implementation.
- Production account
- Production account participates in aws multi account architecture. Account provisioning → Production account; Production account → Central log archive. Define its contract, owner and access permissions in your implementation.
- Development account
- Development account participates in aws multi account architecture. Account provisioning → Development account. Define its contract, owner and access permissions in your implementation.
- Central log archive
- Central log archive participates in aws multi account architecture. Production account → Central log archive. Define its contract, owner and access permissions in your implementation.
Questions about this template
What does this aws multi account architecture diagram show?
It shows 6 components with the core flow Organization → Management account → Account provisioning. Keep management access separate from workload execution.
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.