AWS Builder Center

From Zero to Building: How I Got Familiar with AWS in 3 Months

Discover how to master the basics of Amazon Web Services in 90 days through hands-on practice. Learn which core services to focus on first and the biggest beginner mistakes to avoid.

Three months ago, opening the AWS Management Console felt like looking at the control panel of a spaceship. Every service had an intimidating acronym—S3, EC2, IAM, VPC—and I was terrified of clicking the wrong button and accidentally getting a surprise bill.
Today? I can comfortably launch servers, manage cloud storage, and build basic automated workflows.
Getting comfortable with AWS didn't take years, and I didn't need a computer science degree. It just took 90 days of consistent, hands-on practice. If you are feeling overwhelmed by the cloud, here is how my 3-month journey unfolded step-by-step—including the mistakes I made along the way.



My 3-Month Learning Roadmap

Month 1: Demystifying the Jargon

Instead of trying to learn all 200+ AWS services at once, I focused exclusively on the "Big Three" core concepts:
  • IAM (Security): Learning how to create users and set up basic permissions so I wasn't using my root account for everyday tasks.
  • S3 (Storage): Learning how cloud storage works by creating "buckets" to upload images and static files.
  • EC2 (Compute): Launching my very first virtual server running Linux in the cloud.

Month 2: Moving from Theory to Hands-On Projects

In the second month, I stopped just watching video tutorials and started actually building small, bite-sized projects using the AWS Free Tier:
  • Hosted a Static Web Page: Uploaded HTML and CSS files to an Amazon S3 bucket and configured it as a live website.
  • Deployed a Web Server: Logged into a virtual server on EC2 and hosted a basic application.
  • Connected Storage & Compute: Built a simple workflow that saved files uploaded from an EC2 instance directly into S3.

Month 3: Connecting the Dots & Going Serverless

By the third month, the pieces began coming together into a full ecosystem:
  • Dived into Serverless: Wrote my first AWS Lambda function to run code automatically without managing a server.
  • Earned Skill Badges: Completed learning paths on AWS Skill Builder to test my understanding and collect credentials for my resume.
  • Understood Architecture: Learned how to draw simple diagrams showing how databases, servers, and storage connect.



The Biggest Mistakes I Made (And What They Taught Me)

Learning AWS wasn't smooth sailing. I hit several roadblocks, but each mistake turned out to be the best lesson:

1. Mistake: Leaving an EC2 Instance Running 24/7

  • What Happened: I launched a virtual server for a project and forgot to stop or terminate it when I finished working for the week.
  • What I Learned: Always turn off or terminate active resources when you aren't using them. Most importantly, set up an AWS Budget Alert on Day 1 so you get an email notification if your estimated spending exceeds $1.

2. Mistake: Using the Root Account for Everything

  • What Happened: For the first few weeks, I logged into AWS using my main email and root password for every minor task.
  • What I Learned: The root account has unlimited power and can be a security risk if compromised. I learned the principle of Least Privilege: create an IAM user with only the specific permissions you need for daily work.

3. Mistake: Getting Stuck in "Tutorial Hell"

  • What Happened: I spent two weeks watching long video courses without actually opening the AWS console to follow along. I felt like I understood everything until I tried doing it on my own.
  • What I Learned: Watching someone else build in AWS gives a false sense of mastery. Real learning happens when you click the buttons yourself, run into error messages, and figure out how to fix them.

4. Mistake: Misconfiguring Security Groups

  • What Happened: I spent hours trying to access a web server I created, only to keep getting "Connection Timed Out" errors.
  • What I Learned: Security groups act as virtual firewalls. If you don't explicitly open ports (like Port 80 for HTTP or Port 22 for SSH), AWS will block all incoming traffic by default. Troubleshooting this taught me how cloud network security actually works.



My Key Takeaways for Beginners

  1. Set Up Budget Alerts First: Knowing you are protected from surprise bills gives you the confidence to experiment freely.
  1. Embrace the Errors: Don't get discouraged when something breaks. Fixing a broken configuration or error code is where you learn the most.
  1. You Don't Need to Know Everything: Nobody knows all of AWS. Even experienced cloud engineers look up documentation daily. Focus on understanding how core services interact.
If you are just starting out, take a deep breath. Start small, make mistakes, learn from them, and keep building!
Any opinions in this article are those of the individual author and may not reflect the opinions of AWS.
Enjoyed reading this content? Let the author know!

Your likes, comments, shares, and saves help creators reach more builders.

Loading recommendations

Loading article