Container behind a load balancer architecture
The smallest thing that serves real traffic: a public load balancer in two availability zones and one Fargate container. About four minutes to create and roughly 4¢ an hour, so it is the cheapest way to find out whether a deploy works end to end.
Every resource, and what it costs.
Projections from August 2026 list prices for always-on resources. Connect an account and these become the figures your provider actually bills.
| Node | Type | What it is | Projected |
|---|---|---|---|
| Edge | Network | 1 ALB + light LCU usage | $23/mo |
| Web | Compute | 0.25 vCPU · 0.5 GB | $9.01/mo |
Every figure is a projection from AWS list prices, before anything is built.
Similar templates.
Three-tier web application
The default shape: load balancer, containerised app tier, managed Postgres, cache and asset storage.
Serverless API
HTTP API with function compute and a key-value store. Scales to zero; the floor is the gateway.
Static site on CDN
Marketing site or SPA served from object storage behind a CDN, with DNS and a WAF in front.
Open Container behind a load balancer on the canvas.
It loads as an editable graph. Ask Archie to change it, then approve the plan and it is built in your own AWS account.