Object storage, not a filesystem — buckets, objects, and why S3 needs no server to manage.
Amazon S3 is object storage — not a filesystem, not a database. Every file you store (an object) lives inside a container called a bucket, alongside the metadata S3 keeps about it: size, content type, when it was last modified.
A traditional website needs a running server to answer every request. S3 has no server to manage — you upload objects, and S3 handles storage, retrieval, and durability (99.999999999%, eleven nines) automatically, at whatever traffic volume shows up. That's the pitch for this module: a neighborhood farmers market's schedule page gets almost no visitors Monday through Friday and a sharp spike every Saturday morning — a server sized for the spike sits idle all week, one sized for the average buckles on market day. Static hosting sidesteps the whole problem.
Over the next couple of lessons you'll provision a bucket in CDK, configure
it to serve a website, and grant it public read access — the real page a
small market would actually use, built entirely in code. No // TODO in
this lesson — just read, then continue.