- Learn AWS
- Architecture
- Static site
Architecture pattern
AWS Static site architecture
when the front end is files, not a server
A single-page app is a bundle of files. Nothing has to run to serve them, so nothing should. S3 holds the objects, CloudFront copies them to edge locations near each viewer, and there is no instance to patch or scale.
What it runs through
In the order a request or a record moves through it. Each one links to the page that explains it.
- Web clientBrowser / web client
- CloudFrontAmazon CloudFront
- S3Amazon S3
Signals in a brief that point here
Phrases that, when you meet them in a scenario, mean this shape rather than another. They are the tell, and they are what an exam question is built around.
- “static single-page application”
- “no server-rendered HTML”
- “users all over the world”
- “minimal operations”
What it costs you
Anything that has to be computed per request needs a second path — usually an API alongside, not instead.
Every shape has one. A design decision with no stated downside is usually a decision nobody has finished making.
Learn the services in it
- AWS CloudFrontA content delivery network: copies of your files are cached at edge locations near viewers, and requests that miss go back to your origin over the AWS network.
- AWS S3Object storage for any amount of data: files kept as objects in buckets, designed for eleven nines of durability, and private until you grant access.
Shapes it is easily confused with
These run through some of the same services, which is exactly why a brief that fits one can look like it fits another.
Now build it from a brief
Reading a shape and producing one from a scenario that never names a service are different skills, and the exam asks for the second. The scenarios give you the brief; you draw the architecture and it is scored against what the brief requires.