I’m sharing the three-step blueprint that I would follow to learn AWS if I could start all over again. I’m also giving away loads of free resources that you probably didn’t even know existed so you can get started for free today even if you have zero experience. All you need is a laptop, one or 2 hours per day, and start with step zero.
Step Zero: Developing the Right Mindset
That’s right, you are not ready for step number one yet. When I was starting out, I didn’t even know that this stage existed. I jumped straight into playing around with AWS Services thinking the sooner that I build, the better. I was so wrong because here’s the thing: a great Cloud engineer doesn’t just dive headfirst and learn random tools they’ve never heard of. You have to build a strong foundation before you can build the house.
Back in my old 9-5 job as a cloud engineer, we were assigned a data migration project. Basically, we had to move a bunch of files from our on-prem servers into AWS. Pretty straightforward, right? But what if I told you that we almost ran into serious trouble because we skipped one crucial step?
One of my teammates was so pumped about a brand new AWS tool for transferring data. He had read an article about it, so he was quick to set it up. Within days, we had a demo with files flowing straight into Amazon S3. It looked great, but then we noticed a few big red flags when we started to run some tests. Basically, this new service wasn’t a one-size-fits-all, but we didn’t realize that until after we started building, so we were scrambling around for a better solution.
That’s where the mindset shift comes in. Instead of jumping at the opportunity to learn the newest AWS feature (which we call “shiny object syndrome”), I took a step back and approached the problem with first principles thinking. I asked three simple questions:
- What do we really need this migration to achieve?
- What do we have to do to secure our data?
- How can we verify every file is transferred correctly?
As soon as I mapped out these requirements, it became very clear the new AWS service didn’t meet all our needs. That’s the difference between a good and a great AWS Cloud engineer. A good Cloud engineer would jump on the latest AWS service and put together a quick demo that looks perfect on paper. A great Cloud engineer takes more time in the planning phase to ask the right questions.
This method based on first principle engineering is exactly how students inside of my Academy like John, Mac, or Jay are going from zero to hired by AWS in just a few months.
A great first-principle Cloud engineer asks: How does the solution we’re building scale if our data or user base increases tenfold? What happens in 6 weeks’ time when things break? Do we even have Disaster Recovery in place?
This will make learning AWS so much easier for you because you start to think critically from day one. That’s why if I could start over, the very first thing I would do is make this mindset shift to think from first principles and question every single assumption. Anyone can spin up a service for a quick fix; a great Cloud engineer focuses on the why and the how, ensuring the long-term success of a project.
Step One: Learn Cloud and IT Fundamentals
Now that you have the right mindset, you are ready for step number one. Here’s where most people slip up—they dive straight into building AWS projects. If you want to avoid frustration, you have to build a strong base in cloud and IT fundamentals.
First, start with a clear understanding of what cloud providers like AWS actually do and why companies choose to move from on-prem to the cloud. I recommend checking out AWS Cloud Essentials guide—it’s a great introduction. AWS also has a video that breaks down what AWS does and how it fits into the broader technology ecosystem.
At this stage, don’t worry if you feel overwhelmed at first. There are a lot of new terms that you’ll come across, but the key here is to absorb. This isn’t a time to launch a big project; focus on getting a strong foundational understanding.
Next, you want to learn Linux. Why Linux? Because most, if not all, servers in the cloud are running on Linux distributions. Head over to LinuxJourney.com—it’s a free interactive resource that walks you through Linux commands, file systems, and all that great stuff. FreeCodeCamp also offers a Linux Basics course on YouTube that I recommend.
The third piece of the puzzle in this foundation phase is networking. Cloud computing is fundamentally about connecting resources over networks, so if you don’t understand networking, you’ll get lost very quickly. FreeCodeCamp has a networking tutorial on YouTube, so you should start there.
Next, spend some time understanding operating systems in general—what they do, how processes are managed, and how file systems are structured. Whether you use macOS, Windows, or Linux, this will help you debug problems and assess tradeoffs in architectural decisions when actually working as an AWS Cloud engineer.
Step Two: Build Your Skills in AWS
If I could start over again, I wouldn’t try to learn all 200 AWS services at once. It’s a rookie mistake and a waste of time. To keep things simple, I would focus on four core AWS Services:
- EC2 (Elastic Compute Cloud)
- S3 (Simple Storage Service)
- VPC (Virtual Private Cloud)
- IAM (Identity and Access Management)
I actually have an in-depth AWS course for beginners on my channel—it’s completely free and cuts out all of the noise so you can focus on what actually matters.
Here’s a trap that roughly 96% of beginners make: Everyone knows they have to build projects, but most watch tutorial after tutorial building the same static website on S3 or spinning up a simple database. The problem is that everyone is doing that, so you will never stand out. Plus, you won’t even remember half the steps once you’re done because you’re just following instructions, not solving real problems.
To avoid tutorial hell:
- Don’t just follow tutorials on YouTube. It’s good for the first time to learn how to use AWS services, but after that, think about small real-world problems you can solve.
- Apply the first principles thinking mindset that you’ve just learned. Maybe you want to track your workouts or calories. If it’s something that interests you, you’re way more likely to retain the knowledge.
- Build projects that solve your problems because you’re more likely to finish them.
If you need guidance on where to build these projects, AWS has a hidden gem called AWS Workshops—a site filled with free tutorials to build hands-on projects. I’ve also released a video on AWS cloud projects that will give you an unfair advantage—these are the same projects my students inside my Academy are leveraging to land six-figure roles in the cloud.
Before we jump into step three, there’s one key thing we haven’t covered yet. If you really want to learn AWS and actually get hired, you’ll need to have some coding and automation skills. And if you’re thinking, “I’m not a software engineer, do I really need to learn this?” stick with me.
When you’re building projects for the first time, you can definitely go through the AWS console and manually click through—that’s fine for learning how AWS works. But once you get comfortable, you want to switch to automated, repeatable processes. This is where having basic coding knowledge with Python will make all the difference. It’s not only the most popular language to learn but also the easiest because it reads like plain English.
To learn Python, check out “Bro Code” on YouTube. Being comfortable with Python allows you to handle cloud tasks effortlessly and integrate with two specific tools:
- Terraform: In the real world, companies want to version-control their infrastructure. Instead of clicking buttons in the console, you write code that says, “give me two EC2 instances, one load balancer, a VPC with this IP range,” and Terraform builds it all automatically. To get started with Terraform, go to HashiCorp tutorials—there’s a dedicated section on Terraform with AWS, completely free.
- CI/CD Pipelines: This is about automating the process of testing, building, and deploying your applications to the cloud. When you push a change to your Terraform code, your CI/CD pipeline can automatically test it and apply those infrastructure changes. To get started for free, check out GitHub docs for GitHub Actions.
Step Three: Long-Term Growth
If you’re worried that you’re not technical enough and there’s a lot to take in, don’t worry. The secret to longevity in tech is having the right system that propels you.
If there’s one piece of advice I would give myself when starting over, it’s this: Never stop learning. The cloud evolves daily—new services, best practices, security threats. While it’s exciting, it can also be overwhelming, especially when your day job or personal life gets in the way. That’s why you need to build a system that sets you up for success.
Here’s my personal framework:
- Schedule: Dedicate at least 1-2 hours every day to learn something new on AWS.
- Mentors and Communities: Join communities and go to Cloud meetups. Having mentors to bounce ideas off accelerates your growth, keeps you motivated, and helps you find a job because you’re building a network.
- Project-based Learning: Instead of random tutorials, structure your learning around building real-life projects. That way, you’ll stay focused and have actual results to put in your portfolio.
With this system, you’ll retain what you learn and won’t feel like you’re going too deep into topics you don’t understand yet.
It’s not enough to just learn and build projects in your own corner of the internet—you have to showcase what you’re doing. Why? Because 90% of recruiters will check your LinkedIn before they talk to you. I’ve been in this game for a decade, and being visible online has consistently led to new opportunities, job offers, clients, and partnerships.
It’s not about who you know; it’s about who knows you. If you have the skills but nobody knows about them, it’s as if you don’t exist. So put yourself out there. You don’t need a fancy setup with expensive cameras—just fix your LinkedIn profile because LinkedIn is your new resume in 2025. Make sure your picture looks professional and post 3-4 times a week. Share your progress, talk about what you’re building and learning, and the challenges you’re facing. That way, when you apply for jobs and the hiring manager searches for you on LinkedIn, they’re more likely to give you a chance.
As for certifications, they are important because they give you credibility, and many companies look for them when hiring. But they act as a barrier for more than 93% of beginners because people think they need certifications before they can even learn AWS and build projects, so they never get started building anything—and ironically, they don’t get certified either. That’s why if I could start over again, I would use certifications as a supplement to learning AWS, not as a core focus.
Source: https://www.youtube.com/watch?v=gB00e15sUqc
Comments