AWS Builder Center
Amazon S3 Explained: The Storage Service Every Cloud Student Needs to Understand

Amazon S3 Explained: The Storage Service Every Cloud Student Needs to Understand

A practical, security-aware guide to Amazon S3 for students entering cloud and cybersecuritycovering buckets, access control, bucket policies, encryption, storage classes, and static website hosting.

The Moment S3 Stopped Being Abstract
When I started studying cloud computing, I kept running into Amazon S3. Every tutorial referenced it. Every architecture diagram had that green bucket icon somewhere. Yet nobody seemed to explain why it mattered — they just assumed you'd figure it out.
My real understanding of S3 didn't come from a course. It came from a mistake.
I was experimenting with a small project — storing some log files from an EC2 instance — and I accidentally left an S3 bucket publicly accessible. Nothing sensitive was in it, thankfully. But the moment I realized anyone on the internet could have listed and downloaded those files, something clicked. S3 isn't just a place to dump files. It's infrastructure. And like all infrastructure, if you don't understand it, it will surprise you.
This article is what I wish I had read before that moment.



What Is Amazon S3?

Amazon Simple Storage Service (S3) is AWS's object storage service. It lets you store and retrieve any amount of data — files, images, backups, logs, datasets, static websites — from anywhere on the internet.
Unlike a traditional file system (with folders and paths), S3 is object-based. Every file you upload is an object, and objects live inside buckets.
Here's the core vocabulary you need:
Term
What It Means
Bucket
A container for your objects. Like a top-level folder, but globally unique across all of AWS
Object
Any file you store in S3 (a photo, a script, a CSV, a zip archive)
Key
The full "path" of an object within a bucket — e.g., logs/2026/august/server.log
Region
The AWS data center location where your bucket lives
Storage Class
Controls how frequently data is accessed and how much it costs
One thing that surprises most beginners: S3 is not a file system. There are no real folders. The  /  in a key like  logs/august/server.log  is just part of the name — S3 uses it to simulate folder structure in the console, but underneath, it's all flat.



Why Should Students in Cloud and Security Care About S3?

S3 is everywhere. Once you start working with AWS seriously, you will touch S3 constantly — whether you intend to or not:
  • Cybersecurity: S3 misconfiguration is one of the most common causes of cloud data breaches. Understanding how S3 access works is fundamental to cloud security assessments.
  • Development: Applications store user uploads, logs, and configuration files in S3.
  • DevOps: CI/CD pipelines use S3 to store build artifacts. Terraform state files live in S3.
  • Data & ML: Datasets for machine learning models are staged in S3 before processing.
  • Static Hosting: Entire websites can be served directly from an S3 bucket.
If you're transitioning into cloud or security, S3 is not optional knowledge. It's foundational.



Creating Your First Bucket

Creating an S3 bucket takes about 60 seconds in the AWS console. But the decisions you make at creation time matter.

Step 1 — Name Your Bucket

Bucket names must be globally unique across all AWS accounts worldwide. If someone else already has  my-bucket , you can't use it — even in a different account or region.
Good naming practice:  your-name-project-purpose  — e.g.,  ulindu-lab-logs-2026 

Step 2 — Choose a Region

Pick the region closest to where your application or users are. For Sri Lanka,  ap-southeast-1  (Singapore) or  ap-south-1  (Mumbai) are the nearest options with low latency.
Data stored in a region stays in that region unless you explicitly replicate it. This matters for compliance — some industries require data to remain in specific geographic jurisdictions.

Step 3 — Block Public Access

By default, AWS now blocks all public access to new buckets. Leave this setting on unless you have a specific reason to expose objects publicly (like hosting a static website).
This is the setting I ignored the first time. Don't make the same mistake.



Uploading and Accessing Objects

Once your bucket exists, you can upload files through the console, the AWS CLI, or programmatically via SDKs.

Using the AWS CLI

# Upload a single file
aws s3 cp myfile.txt s3://your-bucket-name/myfile.txt

# Upload an entire folder
aws s3 cp ./logs/ s3://your-bucket-name/logs/ --recursive

# Download a file
aws s3 cp s3://your-bucket-name/myfile.txt ./myfile.txt

# List objects in a bucket
aws s3 ls s3://your-bucket-name/


Pre-Signed URLs

Want to share a private file with someone temporarily without making the whole bucket public? Use a pre-signed URL. It generates a time-limited link that grants access to a specific object.
aws s3 presign s3://your-bucket-name/report.pdf --expires-in 3600

This creates a URL that expires in 3600 seconds (1 hour). After that, the link stops working. This is exactly how services like Google Drive or WeTransfer handle temporary file sharing — and now you know how to build the same thing yourself.



S3 Security: The Part That Actually Matters

This is where most beginners — and unfortunately, many professionals — go wrong. S3 security has multiple layers, and they interact in ways that aren't always obvious.

Layer 1 — Block Public Access Settings

This is the master switch. Even if a bucket policy or object ACL says "public," Block Public Access overrides it. Always leave this on unless you're deliberately hosting public content.

Layer 2 — Bucket Policies

A bucket policy is a JSON document that defines who can do what with your bucket. It's powerful but easy to misconfigure.
Here's what an overly permissive bucket policy looks like — this is what you never want in production:
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Principal": "*",
"Action": "s3:GetObject",
"Resource": "arn:aws:s3:::your-bucket-name/*"
}
]
}

The  "Principal": "*"  means anyone in the world. This is the pattern behind thousands of real data breaches. If you see this in a bucket policy, it's a red flag.
A safer pattern — restricting access to a specific IAM role:
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Principal": {
"AWS": "arn:aws:iam::123456789012:role/MyAppRole"
},
"Action": ["s3:GetObject", "s3:PutObject"],
"Resource": "arn:aws:s3:::your-bucket-name/*"
}
]
}


Layer 3 — IAM Policies

IAM policies on users, groups, or roles also control S3 access. The effective permission is the intersection of what the bucket policy allows and what the IAM policy allows. Both have to permit the action for it to succeed.

Layer 4 — Encryption

S3 now enables server-side encryption by default on all new objects (SSE-S3). Your data is encrypted at rest automatically. For higher control, you can use SSE-KMS to manage your own encryption keys through AWS Key Management Service.
As someone studying cybersecurity: S3 misconfiguration auditing is a real skill in cloud penetration testing and GRC assessments. Tools like  aws s3 ls  without credentials, or public bucket enumeration, are standard reconnaissance techniques. Understanding S3 from the defender's side makes you better on both sides of an assessment.



S3 Storage Classes — Choosing the Right One

Not all data is accessed equally. S3 lets you choose how your data is stored based on how often you need it:
Storage Class
Best For
Retrieval
S3 Standard
Frequently accessed data
Milliseconds
S3 Intelligent-Tiering
Unknown or changing access patterns
Milliseconds
S3 Standard-IA
Infrequently accessed, but needs fast retrieval
Milliseconds
S3 Glacier Instant Retrieval
Archives accessed occasionally
Milliseconds
S3 Glacier Flexible Retrieval
Long-term backups
Minutes to hours
S3 Glacier Deep Archive
Compliance archives, rarely accessed
Up to 12 hours
For learning and lab work, S3 Standard is fine. When you move into real projects, choosing the right storage class can dramatically reduce costs.



A Practical Use Case: Hosting a Static Website on S3

One of the most satisfying things you can do with S3 as a student is host a website for free. Any site that's purely HTML, CSS, and JavaScript — no backend server required — can live in an S3 bucket.
Here's the setup in four steps:
  1. Create a bucket with the same name as your domain (e.g.,  ulindu.dev ) if you have one, or any name for testing
  1. Upload your HTML files — make sure  index.html  is at the root
  1. Enable Static Website Hosting under the bucket's Properties tab
  1. Update the bucket policy to allow public read access to objects (this is one of the rare legitimate cases for a public bucket)
Your site will be available at a URL like:  http://your-bucket-name.s3-website-ap-southeast-1.amazonaws.com 
Pair it with Amazon CloudFront (AWS's CDN) and Route 53 (DNS) for a custom domain with HTTPS. That's a real production-grade setup.



What I'd Tell My Past Self

Before I understood S3 properly, I thought of it as "just file storage" — something boring and obvious. I was wrong.
S3 is a lens through which you can see almost everything important in cloud: IAM and access control, encryption at rest, cost optimization, event-driven architecture (S3 can trigger Lambda functions), compliance, logging, and incident response.
When a real-world cloud breach happens, there's a good chance S3 is involved somewhere — either as the exposed asset or as the evidence trail in access logs. Understanding it deeply, not just as a place to upload files, is what separates a surface-level cloud user from someone who can design and defend cloud systems.
That's worth learning properly.



Key Takeaways

  • S3 stores objects in buckets — it's not a traditional file system
  • Block Public Access should almost always be on — it's your safety net
  • Bucket policies define access;  "Principal": "*"  in a policy is a red flag to know and recognize
  • Pre-signed URLs let you share private files temporarily without changing permissions
  • S3 connects to nearly every other AWS service — it's infrastructure, not just storage
  • S3 misconfigurations are a major real-world security risk — understanding it makes you a better defender and a more capable assessor



What's Next?

If this article clicked for you, here's where to go deeper:
  • AWS Skill Builder — Introduction to Amazon S3 (free, hands-on lab)
  • S3 + Lambda — trigger a function every time a file is uploaded
  • S3 Access Analyzer — AWS's built-in tool that flags publicly accessible buckets
  • CloudTrail + S3 — log every API call made to your bucket for forensic visibility
  • Boto3 (Python SDK) — interact with S3 programmatically in your own scripts
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