AWS Builder Center

Amazon S3 for Beginners: What I’ve Learned So Far

A CS student’s plain-language notes on Amazon S3: buckets, objects, keys, security basics, and the questions I still have as a beginner.

I’m a CS student learning AWS step by step. These are my notes on Amazon S3, the first storage service most beginners meet, in plain words, plus the questions I still have.
When I started learning AWS, one service kept showing up everywhere: in tutorials, in architecture diagrams, in other people’s projects. It was Amazon S3. So before moving on to anything fancier, I decided to understand it properly. Here’s what I’ve learned so far.

What is S3?

S3 stands for Simple Storage Service. It stores files on AWS: images, documents, backups, website files, datasets, and more. The easiest way I found to picture it is as an online hard drive with no practical size limit.

Three words that explain everything

Think of S3 as a huge storage building:
Term
Meaning
Analogy
Bucket
The container that holds your files. Its name must be unique across all of AWS.
A storage unit with your name on it
Object
A file stored in a bucket, plus its details (metadata). A single object can be up to 5 TB.
One box inside the unit
Key
The object’s name or path in the bucket, like  photos/cat.jpg .
The label on the box
One thing that surprised me: S3 doesn’t have real folders. The  /  in a key just makes the console display them like folders.

Why it’s worth learning first

S3 is designed for very high durability, meaning AWS aims to keep your data safe even if hardware fails. That’s why so many other services use it as their storage layer. Learning S3 early makes later topics easier to follow.

What can you use it for?

  • Storing files for an app, such as user uploads and images
  • Backups and archives
  • Hosting a simple static website (HTML, CSS, JavaScript)
  • Keeping datasets for data and machine learning projects

The security lesson every beginner should know

New buckets are private by default, and AWS has a setting called Block Public Access that helps prevent accidental exposure. Before making any bucket public, it’s worth asking why. Many data leaks in the news came from buckets that were opened by mistake, so this is the setting I plan to understand before touching anything else.

Storage classes

S3 offers different storage classes: standard ones for files you use often and cheaper ones for files you rarely need. I’m still learning the details, so I’ll read the official documentation before choosing one for a project.

My next step

The project I see recommended most for beginners is to host a one-page website on S3. It touches buckets, objects, permissions, and static hosting in one small task, so that’s what I want to try next.

Questions I still have

  1. When is it right to make a bucket public, and what’s the safest way to do it?
  1. How do I choose a storage class for a small project?
  1. What’s the best way to let an app access a bucket without sharing access keys?
If you know the answers or have good resources, please share them in the comments. I’d love to learn from you.
Any opinions in this article are those of the individual author and may not reflect the opinions of AWS.
Enjoyed reading this content? Let the author know!

Your likes, comments, shares, and saves help creators reach more builders.

Loading recommendations

Loading article