Serve static work at the edge
Let CloudFront answer cacheable requests close to the visitor while the private S3 origin remains inaccessible from the public internet.
AWS infrastructure reference
Zero-idle serverless, made legible.
An interactive architecture brief for static edge delivery, on-demand compute, durable asynchronous work, and controlled failure paths.
Interactive request model
Follow the work, not the service list.
Select a scenario to see which parts of the system participate and what the operating model must account for.
Request scenarioChoose a path to inspect
request-path.mmd illustrative model
Rendering architecture diagram…
edge cache hitResponse served at edge
Architecture decisions
The structure follows the workload.
Each service earns its place by changing delivery, isolation, durability, or operating responsibility.
Invoke compute only for work
Use event-driven functions for dynamic behavior instead of maintaining an application server that waits for traffic.
Externalize durable state
Keep functions replaceable. Durable state belongs in services designed for persistence, concurrency, backup, and recovery.
Design the failure path
Bound retries, isolate exhausted work, expose useful operating signals, and give callers a controlled result when dependencies fail.
Cost boundary
Zero idle compute is not zero cost.
The architecture avoids a permanently running application server. It still consumes managed services whose pricing, quotas, and abuse exposure need review against the actual workload.
Design rule
Estimate with named traffic assumptions, then verify against current AWS pricing before deployment.
| Area | Cost behavior | Boundary |
|---|---|---|
| DNS | Hosted-zone baseline plus queries | Route 53 is not scale-to-zero. |
| Static delivery | Storage, requests, and transfer | CloudFront and S3 usage remains billable. |
| Dynamic path | Requests, duration, and capacity consumed | API Gateway, Lambda, DynamoDB, and SQS charge by their own units. |
| Operations | Logs, metrics, alarms, and optional controls | Retention and services such as WAF must be chosen deliberately. |
Delivery model
Infrastructure is reviewed before it becomes infrastructure.
The public reference repository treats deployment code, operating checks, and rollback notes as one deliverable.
- 01
Validate
Lint, type-check, test constructs, and synthesize the infrastructure template.
- 02
Plan
Review the generated change set, IAM changes, replacement risk, and estimated service footprint.
- 03
Deploy
Assume a scoped CI role through OIDC and apply the reviewed infrastructure change.
- 04
Verify
Run smoke checks, inspect alarms and logs, then record the deployed version and rollback point.
Need a decision, not another service diagram?
Request an architecture assessment