WHY MY FILES NEVER TOUCH MY SERVER ?? 🤔

When I first started building cloud projects, I assumed file uploads worked like this:

📂 User Uploads File
⬇️
🖥️ Server Stores File on Its Disk

Simple, right?

But while building RIA Vault, a cloud document management dashboard, I learned that modern cloud applications often work very differently.

Instead of storing files on the server itself, my architecture looks like this:

📂 User
⬇️
🌐 Frontend (Vercel)
⬇️
⚙️ Flask Backend (Render)
⬇️
☁️ AWS S3

So where does the file actually live?

👉 Not on my server.

👉 Not on Render.

👉 Inside Amazon S3.

What happens when a user uploads a file?

1️⃣ The user selects a file from the dashboard.

2️⃣ The frontend sends the file to my Flask backend using the Fetch API.

3️⃣ The backend receives the file and uses AWS Boto3 SDK.

4️⃣ Boto3 calls Amazon S3's upload service.

5️⃣ S3 stores the file and returns a success response.

6️⃣ The dashboard instantly updates to show the uploaded file.

Why not store files on the server?

Imagine 10,000 users uploading documents.

If everything is stored directly on the server:

❌ Storage fills up quickly
❌ Scaling becomes difficult
❌ Server crashes can affect files
❌ Managing backups becomes a headache

Using Amazon S3 solves many of these problems:

✅ Highly scalable storage
✅ Designed for massive amounts of data
✅ Better reliability and durability
✅ Pay only for what you use

AWS Services I Used

🔹 Amazon S3 – Cloud object storage

🔹 AWS Boto3 SDK – Python SDK to interact with AWS services

Key methods used:

s3_client.upload_fileobj()
s3_client.list_objects_v2()
s3_client.delete_object()

These three methods powered the core functionality of my project:

📤 Upload Files

📋 View Files

🗑️ Delete Files

My Biggest Learning

Before this project, I thought cloud storage was just "a folder on the internet."

After building with AWS S3, I realized modern applications separate:

🖥️ Compute Layer → Handles requests

☁️ Storage Layer → Stores files

This separation makes applications easier to scale, maintain, and deploy.

Building projects teaches concepts that documentation alone cannot.

What's one AWS service that completely changed how you think about cloud architecture?