Skip to content

AWS · Editable reference architecture

AWS public and private subnet architecture

An editable aws public and private subnet architecture reference showing Internet → Public subnet load balancer → Private subnet application and downstream dependencies. Private placement still requires routes and permission rules.

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.

LinkedInTelegramReddit

AWS public and private subnet architecture diagram: Internet, Public subnet load balancer, Private subnet application, Isolated database subnet and their connections
AWS public and private subnet architecture — follow the component relationships, then open the editor to adapt the design. View diagram image.

6 components · 5 connections · Open the editor to zoom, move nodes and edit source.

Architectural overview

AWS public and private subnet architecture addresses the responsibilities and boundaries shown in this reference rather than prescribing an entire production deployment. The primary flow starts at Internet and reaches Isolated database subnet through Public subnet load balancer, Private subnet application. Use this view to explain which component initiates work, which component owns a decision, and where a dependency can affect the caller. Private placement still requires routes and permission rules.

The diagram contains 6 distinct components and 5 directed relationships. A separate path connects Private subnet application → VPC endpoint → S3. 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 Internet a bounded dependency timeout and a documented failure response. For Isolated database subnet, 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 public and private subnet architecture with explicit ownership and dependency paths. Private placement still requires routes and permission rules.

Data flow

Connections from this diagram. Branches and control signals are not a single chronological sequence.

  • Internet → Public subnet load balancer. Define the interaction contract and trace the resulting response or state change.
  • Public subnet load balancer → Private subnet application. Define the interaction contract and trace the resulting response or state change.
  • Private subnet application → Isolated database subnet. Define the interaction contract and trace the resulting response or state change.
  • Private subnet application → VPC endpoint. Define the interaction contract and trace the resulting response or state change.
  • VPC endpoint → S3. Define the interaction contract and trace the resulting response or state change.

Security boundaries

  • Authenticate callers at the boundary before Public subnet load balancer accepts protected work; authorize the specific operation rather than trusting network placement.
  • Use separate service identities and least-privilege permissions for Public subnet load balancer, Private subnet application, Isolated database subnet. Encrypt sensitive traffic, protect credentials and avoid placing confidential payloads in logs.
  • Restrict and audit access to Isolated database subnet; define retention and deletion requirements for the actual data.

Failure handling

Internet 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 Internet in an isolated test and measure errors, recovery and any repeated side effects.

Isolated database subnet 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 Public subnet load balancer

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 Internet and verify rejection, observability and unchanged valid state.

Trade-offs and alternatives

Private placement still requires routes and permission rules.

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 public and private subnet architecture

Benefit
Keeps the responsibilities of Internet, Public subnet load balancer, Private subnet application 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 public and private subnet architecture to engineers or stakeholders using a concrete visual flow.
  • Review this decision before deployment: Private placement still requires routes and permission rules.
  • Adapt a starting diagram for your own requirements, then record and validate every changed boundary.

Key components

Internet
Internet participates in aws public and private subnet architecture. Internet → Public subnet load balancer. Define its contract, owner and access permissions in your implementation.
Public subnet load balancer
Public subnet load balancer participates in aws public and private subnet architecture. Internet → Public subnet load balancer; Public subnet load balancer → Private subnet application. Define its contract, owner and access permissions in your implementation.
Private subnet application
Private subnet application participates in aws public and private subnet architecture. Public subnet load balancer → Private subnet application; Private subnet application → Isolated database subnet; Private subnet application → VPC endpoint. Define its contract, owner and access permissions in your implementation.
Isolated database subnet
Isolated database subnet participates in aws public and private subnet architecture. Private subnet application → Isolated database subnet. Define its contract, owner and access permissions in your implementation.
VPC endpoint
VPC endpoint participates in aws public and private subnet architecture. Private subnet application → VPC endpoint; VPC endpoint → S3. Define its contract, owner and access permissions in your implementation.
S3
S3 participates in aws public and private subnet architecture. VPC endpoint → S3. Define its contract, owner and access permissions in your implementation.

Questions about this template

What does this aws public and private subnet architecture diagram show?

It shows 6 components with the core flow Internet → Public subnet load balancer → Private subnet application → Isolated database subnet. Private placement still requires routes and permission rules.

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.