Once I had a rough mental model of how the cloud fits together, the next wall was the names. AWS has hundreds of services and a lot of them sound interchangeable until they aren’t. These are the ones I kept mixing up, and the plain-language version that finally made each one stick.
EC2 vs Lambda — “a computer I rent” vs “code that just runs”
EC2 is a server you rent. It’s a computer in the cloud that’s yours to set up, keep running, and pay for whether or not anyone’s using it. Lambda flips that: you hand over a piece of code, and it runs only when something triggers it, then disappears. No server to babysit, and you pay per run.
The way I hold it: EC2 is renting a shop and keeping the lights on. Lambda is paying someone only for the minutes they actually work.
S3 vs a database — “files” vs “queryable data”
I kept treating S3 as a catch-all place to put things, including things that belong in a database. S3 is object storage: it’s brilliant for files. Images, backups, the static files behind a website. You put a thing in and get it back by its name.
A database (like DynamoDB or RDS) is for data you need to ask questions of. “All messages from last week.” “This user’s orders.” S3 can hold a file; a database can answer a query. Different jobs.
Region vs Availability Zone — “city” vs “buildings in that city”
A Region is a geographic location, like Mumbai or Frankfurt. An Availability Zone is one of several isolated data centers inside that region. You spread across zones so that if one building has a bad day, your thing stays up. Region is the city; AZs are separate buildings in it, on different power and networks.
IAM — “who’s allowed to do what”
IAM is how AWS decides who can do which actions on which resources. It’s big enough that it gets its own post down the line, but the one idea that stuck early was this: nothing is allowed until you explicitly allow it. Silence means no. That single rule explains most of the “access denied” messages a beginner runs into.
CloudFront vs Route 53 — “the fast copy nearby” vs “the phone book”
Route 53 is DNS: it turns a domain name into the address of where your thing actually lives. The phone book. CloudFront is a content network that keeps copies of your content close to users around the world, so the page loads from nearby instead of crossing the planet. One finds the place; the other makes getting there fast.
A quick reference, for future me
| Service | What it actually is | Plain version |
|---|---|---|
| EC2 | Virtual server you manage | A computer you rent |
| Lambda | Code that runs on a trigger | Pay-per-run, no server |
| S3 | Object storage | A place for files |
| DynamoDB / RDS | Databases (NoSQL / relational) | Data you can query |
| Region / AZ | Geography / data centers | City / buildings in it |
| IAM | Permissions system | Who can do what |
| Route 53 | DNS | The phone book |
| CloudFront | Content delivery network | Fast copies nearby |
None of this makes me an engineer. I haven’t wired these together with my own hands yet. But I can read an architecture diagram now and actually follow the story it’s telling, and a year ago I couldn’t. For where I’m headed, that feels like the right first thing to own.