The 5 AWS Services Every Beginner Actually Needs to Know
AWS has over 200 services. Two hundred. When I first opened the AWS console, the wall of names — half of them sounding like rejected sci-fi spaceships — nearly made me close the tab.
Here's the good news I wish someone had told me on day one: you don't need 200 services. You need about 5. Almost every app you'll ever deploy leans on the same small handful, and once these click, the other 195 are just variations and add-ons.
So let's meet the five that matter. No jargon, just plain English and an analogy for each.
1. EC2 — your rented computer in the cloud
Think of it as renting an apartment instead of buying a house.
EC2 (Elastic Compute Cloud) gives you a virtual computer that lives in AWS's data center and runs 24/7. You don't own the physical machine — you rent a slice of one — but inside it, you have the keys. You can install software, run your app, configure it however you like.
Want a bigger place? Resize to a more powerful machine. Done with it? Hand back the keys and stop paying. That flexibility — rent what you need, scale up or down, never deal with the building's plumbing — is the whole point of "Elastic."
When you'll use it: running an app, a backend server, basically any time you need a full computer that's always on.
2. S3 — your infinite storage closet
Think of it as a magic storage unit that never runs out of space.
S3 (Simple Storage Service) is where you put files: images, videos, backups, the HTML/CSS/JS of a website, anything. You drop files into "buckets" (just named containers), and AWS stores them durably across multiple locations so they don't get lost.
The magic part: it's practically infinite and you pay only for what you actually store. No buying a hard drive that's too big or too small — the closet grows to fit your stuff.
When you'll use it: hosting a static website, storing user uploads, keeping backups, serving images and downloads.
3. VPC — your private, fenced-off neighborhood
Think of it as a gated community for your servers.
A VPC (Virtual Private Cloud) is your own private network inside AWS. Your EC2 machines live inside it, and the VPC controls who and what can come in and out — like a gated neighborhood with a security guard at the entrance.
Inside, security groups act as the guards, enforcing rules like "allow web visitors in on the front gate (port 443), but block everyone else." This is how you keep your database hidden from the public internet while still letting your website face the world.
When you'll use it: always, quietly, in the background. Every serious deploy runs inside a VPC, even if AWS sets a default one up for you.
4. Route 53 — the cloud's phone book
Think of it as the contacts app for the internet.
Computers find each other using IP addresses — strings of numbers no human wants to memorize. Route 53 is AWS's DNS service: it translates a friendly name like cloudcompass.dev into the actual numeric address of your server, the same way your phone's contacts turn "Mom" into her phone number.
So when someone types your domain, Route 53 is what quietly points them to the right machine. (The odd name? Port 53 is the traditional port DNS runs on.)
When you'll use it: whenever you connect a custom domain to your app.
5. CloudWatch — the dashboard and smoke detector
Think of it as the dashboard in your car plus a smoke alarm in the house.
Once your app is live, you need to know how it's doing. CloudWatch collects logs (what your app is saying) and metrics (how much traffic, how fast, how many errors). It's your speedometer and fuel gauge.
And like a smoke detector, it can alert you — "CPU is maxed out," "error rate just spiked" — so you find out something's wrong before your users do.
When you'll use it: the moment anything is running in production and you care whether it stays healthy.
How they fit together
Picture deploying a simple web app, and watch the five play their parts:
Your app runs on EC2 (the rented computer), serving files stored in S3 (the storage closet), all inside a VPC (the gated neighborhood) that keeps it secure. Route 53 (the phone book) points your domain at it, and CloudWatch (the dashboard + smoke alarm) watches over the whole thing.
That's a real, working architecture — and it's just five services.
The takeaway
When AWS's 200+ services make you feel like you're drowning, come back to these five. They cover the four questions every deploy answers: what runs my code (EC2), where do my files live (S3), how do I stay secure and reachable (VPC + Route 53), and how do I know it's healthy (CloudWatch)?
Learn these cold, and the rest of AWS stops being a wall of scary names — it becomes a toolbox where you already know the essentials, and everything else is a specialized tool you reach for only when you need it.
This is part of My Cloud Journey, where I document what I'm learning on the way to becoming a cloud architect — plain English, one concept at a time. CLCD: Continuous Learning, Continuous Deployment. Next up, I'm untangling one of the most confusing beginner topics: IaaS vs PaaS vs SaaS. See you there.
