Real-world scenario
A startup needs a data lake for analytics CSVs. The bucket must be private, encrypted, and only a designated IAM user may upload.
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.
Create an S3 bucket named "data-lake-bleepx" in us-east-1.
Set default encryption to SSE-S3 on "data-lake-bleepx".
Enable S3 Block Public Access on "data-lake-bleepx".
Create an IAM user named "lake-uploader".
Create an IAM policy named "LakePutOnly" and attach it to "lake-uploader" allowing s3:PutObject on arn:aws:s3:::data-lake-bleepx/*.
Bleepx skills build on each other. Continue your learning path across Query, Lab, and Cloud.