Project: Host a Static Website on S3

As with Module 3's project, you can follow this directly in a real AWS account or read through it without creating anything. If you do create a real bucket, check your AWS account's current Free Tier eligibility and the current S3 pricing page first — don't assume a small training bucket is automatically free, and remember Lesson 3's point that storage classes, and Versioning if you enable it, each carry their own cost characteristics.

1. Create or select a bucket — using the quarrydev-training-UNIQUE_SUFFIX naming pattern from Lesson 1, with your own unique, non-sensitive suffix.
2. Upload a small static site — at minimum an index.html file, and optionally an error page.
3. Inspect the uploaded object — confirm its key, size, and that it uploaded successfully.
4. Reason about access — this bucket is a website, so enabling public read access to its content is the deliberate, narrow exception Lesson 4 discussed — not a default applied to every bucket.
5. Optionally enable Versioning — upload a second version of index.html and observe that both versions now exist, per Lesson 3.
6. Configure static website hosting — set the index document (and error document, if you added one).
7. Test — request the site's website endpoint in a browser and confirm your page loads.

If you have the AWS CLI configured, the same steps can be done from a terminal instead of the Console — entirely optional, and not required to complete this project:

aws s3 ls

aws s3 cp example.txt s3://YOUR_BUCKET_NAME/example.txt

The first command lists your buckets, confirming your CLI is authenticated and working. The second uploads a local file (example.txt) to a specific bucket and key — replace YOUR_BUCKET_NAME with your own real bucket name (following Lesson 1's naming pattern), and never paste real AWS credentials into a command or commit them anywhere.

This project creates real, potentially billable resources if followed in a real account. Once you've confirmed the site works and you're done experimenting, work through this checklist — don't assume any single step handles everything:

1. Review the objects in the training bucket.
2. Review object versions, if you enabled Versioning in step 5 — per Lesson 3, a version can remain stored even after the "current" object appears deleted.
3. Review delete markers, if any objects were deleted while Versioning was enabled.
4. Delete training objects and versions you no longer need — all of them, not just the visible current version.
5. Remove any lifecycle configuration you added, if it's no longer needed.
6. Delete the training bucket itself once it's empty and you're finished with it.
7. Confirm the bucket no longer exists by checking your account's S3 dashboard directly — the same "verify, don't assume" discipline Module 3 taught for EC2.

Lists the S3 buckets visible to your currently configured AWS CLI credentials. A quick way to confirm the CLI is authenticated and working before trying anything else — entirely optional if you're following along in the Console instead.

Uploads a local file (example.txt) to the given bucket at the key example.txt. Replace YOUR_BUCKET_NAME with your own real, unique bucket name — never a shared or guessable one — and never include real credentials in the command itself; the AWS CLI reads those from your existing configuration.