Buckets in S3 🪣

So, you’ve met S3 – the big cloud hard drive. But here’s the twist:
You don’t just throw files into the sky like confetti 🎉.
AWS makes you put them inside buckets. Yep, buckets. 🪣

What is a Bucket? 🤔

• A bucket is basically a container (or folder) in S3.
• Every file (aka object) you upload must live inside a bucket.
• Think of it as a digital backpack 🎒 for your files.

No bucket = no storage. AWS is strict like that.

Why Buckets? 🤷‍♂️

• Buckets help you organize your stuff (cat pics in one, project files in another).
• They give your data a unique address on the internet.
• AWS uses bucket names to make your files globally unique.

Example:

• Bucket: kahnu-memes
• Object: funnycat.png
• URL: https://kahnu-memes.s3.amazonaws.com/funnycat.png

Rules of Bucket Naming 📝

AWS is picky about bucket names. Follow these rules:

1. Bucket names must be globally unique (no two buckets can have the same name).
2. Lowercase only → mybucket ✅, MyBucket ❌
3. No spaces or special characters → kahnu-bucket ✅, kahnu_bucket!! ❌
4. Length: 3 to 63 characters.
5. Can’t be just an IP address (192.168.0.1 🚫).

Buckets & Regions 🌍

• Every bucket lives in a specific AWS region (like us-east-1, ap-south-1).
• Files in that bucket physically live in that region’s data centers.
• Choose a region close to your users → faster access, lower costs.

Buckets vs. Folders 🗂️

• Buckets are like drives.
• Folders (inside buckets) are just a visual trick AWS gives you.
• Technically, S3 doesn’t have folders → it just pretends with naming (catpics/cute.png).

So don’t get confused — folders = fake magic, buckets = real deal.

Kahnu’s Pro Tip 💡

Treat buckets like kingdoms 👑.
Each kingdom has its own rules (naming, region, access).
Inside the kingdom, you can create villages (folders) and store treasure (files).