Real-world scenario
A fintech startup rushes to launch. They leave an S3 website public, an EC2 security group open to 0.0.0.0/0 on SSH, and a PowerUserAccess policy on a human user. You audit and remediate.
By the end you can:
Follow the request/data flow through the architecture.
Work through each concept and mark it understood. This unlocks the knowledge check.
Object storage with 11 nines of durability and effectively unlimited capacity.
Why it matters
The backbone of data lakes, static sites, backups and pipelines.
When to use it
Use for objects/blobs. Use EBS for block (a disk for one instance) and EFS for shared file systems.
Example
aws s3 cp ./report.pdf s3://my-bucket/reports/ \ --storage-class INTELLIGENT_TIERING --sse aws:kms
Gotcha (exam trap)
S3 is private by default — public exposure is almost always a misconfigured policy or disabled Block Public Access, not an S3 flaw.
Finish the walkthrough above to unlock the check.
Use the simulated AWS console below to complete each mission step. No real AWS account is required.
In the S3 tab, enable S3 Block Public Access on the "bleepx-bank-website" bucket.
Replace the SSH (port 22) rule on the web-sg security group so it only allows 203.0.113.0/24.
Create a new scoped policy named "WebAdminReadOnly" and attach it to web-admin, replacing the PowerUserAccess wildcard.
Open the Terraform tab and click "Generate & Save Terraform" to export the remediated infrastructure as IaC.
Bleepx skills build on each other. Continue your learning path across Query, Lab, and Cloud.