Hands-on emulator lab · 6–10 min
Bring a website closer — CloudFront and S3
Describe a website distribution and inspect where it gets its files.
These actions use an isolated AWS Emulator. It stores API state locally; it does not create paid cloud resources or run the full hosted AWS service.
Your goal
Describe a website distribution and inspect where it gets its files.
Why this matters
A distribution needs to know where the original files live and which page opens first. You will configure an S3 origin and a default page. The emulator stores that setup without creating worldwide edge servers.
Words you will use
A cache keeps a reusable copy. An edge location serves nearby visitors. The origin is the place holding the original file.
How to proceed
Start a fresh emulator, read each numbered step, and enter the practice settings shown. Run the action, inspect its API receipt, then continue. Finish lab checks the emulator state again before saving your progress.
1. Create an origin bucket
Create a practice bucket. An origin is the place CloudFront asks for the original file. The bucket remains local to your emulator.
2. Save a distribution configuration
Point a distribution at your bucket’s origin name and set index.html as the default page. The emulator stores this configuration. It does not create worldwide edge servers or make your bucket public.
3. Inspect the origin and default page
Get the distribution record. Find your origin and the index.html setting. A stored distribution is different from measuring a real cache hit or a visitor’s download speed.
Practice, then check your understanding
Perform the actions yourself and inspect the returned state. Errors keep your settings so you can retry. Starting another lab clears the previous live environment. Earned XP is kept, and signed-in achievements sync to your account. Replay does not award duplicate XP.
Read the official AWS documentation for service behavior and production details.