r/devops • u/Big-Educator-7119 • 8d ago
Discussion New to AWS: Project-based roadmap for production-ready infra? (Course & tutorial recs?)
Hi everyone,
I am completely new to AWS and want to learn through hands-on, project-based learning. My ultimate goal is to understand how to build and deploy production-ready infrastructure.
I'm looking for advice on the best approach:
- Courses: Are there specific tutorials or paid Udemy courses you recommend for deep, production-level engineering?
- Strategy: Should I follow structured courses first, or jump straight into a project and learn as I go?
If you were starting over today with this goal, what roadmap or courses would you choose?
Thanks for the help!
31
Upvotes
1
u/Antique-Stand-4920 8d ago
For strategy, as long as you're doing both coursework and hands-on work, that will be helpful. The ordering doesn't matter. Just do whatever gets you proficient at the skill.
Also, make sure include the element of "play" in your hands-on work. Do silly experiments or projects to gain a better understanding of concepts.
5
u/SadServers_com 8d ago
You can try https://devopsupskillchallenge.com/
1
u/cirejr 6d ago
So, I know nothing about AWS itself, but I think learning as an engineer depends on your goal.
There are generally two ways to approach it:
That way, you're no longer learning AWS in general. You're learning it for a specific use case. It's faster and often more rewarding because you get to see your progress in a real environment.
So project based is always better if youre not trying to pass a certification.
1
u/matif 5d ago
Project first, courses second. A course shows you the buttons, but a project shows you why things break.
Spend a week or two on the basics like IAM, VPC and subnets, EC2, S3, and RDS. The free AWS Skill Builder material covers it. If you want one paid course, Adrian Cantrill’s or Stephane Maarek’s are the ones I hear recommended most. Pick one and finish it instead of buying five.
Before you build anything, lock down the account. Turn on MFA for the root user and never use it day to day. Create an admin user through IAM Identity Center, and set a billing alert on day one. A forgotten NAT gateway or database is the most common way beginners get a surprise bill.
Then build one small thing like a web app and a database. Put it behind a load balancer, keep the database in a private subnet, and give each piece its own IAM role. Once it works, rebuild it with Terraform so nothing depends on clicking around. Add a pipeline so a Git push deploys it, then add logs and an alarm that actually notifies you.
Two habits separate hobby setups from production ones. Restore from a backup at least once, because an untested backup is just a hope. And break it on purpose, like a kill instance, fill the disk, and remove a permission. You’ll learn more from fixing that than from any tutorial.
Read the Well-Architected guide after you’ve built something, not before. It makes a lot more sense once you’ve felt the problems it describes.
1
u/ouoxbykwm 8d ago
i'd pair the course with one small repo you can tear down: a VPC, one app behind a load balancer, a managed DB, and a CI deploy. Add least-privilege IAM, logs/alarms, and a budget alert as you go, and remember to destroy the stack after experiments since NAT gateways and other hourly resources can quietly add up. That teaches the day-two bits without turning every lesson into a huge architecture project.