
5 Things I Wish Someone Told Me Before I Started Learning AWS
A no-nonsense beginner's guide to AWS — free tier landmines, why you don't need to learn all 200 services, and the habits that actually stick.
5 Things I Wish Someone Told Me Before I Started Learning AWS
A no-fluff, beginner-friendly guide to starting AWS the smart way—from someone who made every mistake in it first.
If you've just opened the AWS Management Console for the first time and felt a small wave of panic looking at 200+ services with names like "Lambda," "Fargate," and "Step Functions"—congratulations, you're normal. Everyone who's ever learned AWS has had that exact moment.
I started the same way: a cloud computing course, a lot of confusion, and way too many tabs open trying to figure out what I actually needed to learn versus what I could ignore for now. A few months and a couple of real projects later — including an EC2-based internship and a fully serverless build with Lambda, Cognito, and API Gateway — here's what I wish someone had told me on day one.
Quick take, if you're short on time:* Set a billing alarm before you touch anything* Don't try to learn all 200+ services — pick a path* Learn IAM early, even though it's boring
- Build something small and real instead of only watching tutorials
- Use the community around you instead of learning alone
1. The Free Tier is generous, but it has landmines
AWS's Free Tier is genuinely one of the best ways to learn cloud for free — but "free" doesn't mean "unlimited," and it doesn't mean "forever." Some services are free for 12 months, some are "always free" but only up to a usage cap, and it is entirely possible to leave something running by accident and get a bill you weren't expecting.
Do this: Before you touch anything, set up a Billing Alarm in CloudWatch for a small amount (like $1). It costs nothing to set up and will save you from a nasty surprise. Also, get in the habit of shutting down or deleting resources — EC2 instances, RDS databases — the moment you're done experimenting with them.
2. You do not need to learn all 200+ services
This was the biggest mental shift for me. Beginners often think "learning AWS" means working through every service alphabetically. It doesn't, and trying to do that is a fast way to burn out before you build anything real.
Do this instead: Pick a path. If you're aiming for a certification, the AWS Certified Cloud Practitioner path forces you to learn a sensible, curated slice of AWS — enough to be dangerous, not enough to overwhelm you. Once you have that foundation, specialize based on what you actually want to build (serverless, data, security, ML) instead of trying to be equally deep in everything.
3. Learn IAM early, even though it's boring
Nobody gets excited about identity and access management. It's not flashy, there's no "wow" demo moment, and it's tempting to skip past it to get to the services that actually do things. Don't.
Every real mistake I made early on traced back to permissions—either giving something too much access out of laziness ("I'll just attach AdministratorAccess and move on") or too little and spending an hour debugging an "Access Denied" error that had nothing to do with my code.
Do this: When you create your first IAM role for a project, force yourself to write the exact permissions it needs instead of reaching for a broad managed policy. It's slower up front. It will save you real pain later, and it's a habit that separates "can use AWS" from "can be trusted with AWS" in a job setting.
4. Watching tutorials is not the same as building
This one is uncomfortable to admit, but I'll say it: you can watch a hundred "Build a Serverless App in 10 Minutes" videos and still freeze up the first time you try to do it yourself without the video paused next to you. Watching teaches you vocabulary. Building teaches you the platform.
Do this: As early as possible, pick one small, real project — not a tutorial clone, something with your own twist — and build it end to end, even badly. My first real project was a serverless attendance system using Lambda, Cognito, and API Gateway. It broke constantly. Every single break taught me more than the tutorials that came before it.
5. Certifications and community help — but only once you're building
Certifications are useful. They're structured, they're recognized by recruiters, and studying for one gives you a curated syllabus instead of an overwhelming ocean of docs. But a certification alone, without anything built, is a weaker signal than a working (even small) project plus a certification.
This is also where the AWS community side genuinely pays off—and it's a little meta that I'm writing this on it. Places like AWS Builder Center let you read real build stories from other beginners and experienced builders alike, ask questions, and even pick up free training credits and certification vouchers as you engage with the platform.
Try this: Don't just lurk. Comment on something, publish your own first article about whatever small thing you built this week, however unpolished it feels. The "unpolished beginner build" post is usually more useful to the next beginner than a perfectly polished one.
The Short Version
If you're just starting out, here's the whole guide in one line: set a billing alarm, pick a path instead of trying to learn everything, take IAM seriously even when it's boring, build something small and real instead of only watching tutorials, and use the community around you instead of learning in isolation.
You don't need to have it figured out. Nobody did on day one — including everyone who now looks like they did.
Enjoyed reading this content? Let the author know!
Your likes, comments, shares, and saves help creators reach more builders.
Loading recommendations
Loading article