AWS Builder Center
Starting My AWS Journey: 7 Lessons I’ve Learned as a Beginner

Starting My AWS Journey: 7 Lessons I’ve Learned as a Beginner

A few weeks ago, I started my journey into AWS and cloud computing. At first, seeing the huge number of AWS services, concepts, and new terms was a little overwhelming. But as I started studying the fundamentals and putting some of them into practice, things gradually became clearer. I’m still at the beginning of this journey, so I’m definitely not an AWS expert. These are simply 7 lessons that have helped me learn more effectively so far.

software engineer

1. You don't need to learn everything at once

One of the first things I realized is that AWS is huge.
There are hundreds of services, and trying to understand all of them from the beginning would probably make learning much harder.
Instead, I’m focusing on the fundamentals first and gradually expanding my knowledge as I understand what each service is actually used for.
One step at a time.

2. Understand the problem before memorizing the service

Something that has helped me a lot is changing the way I study.
Instead of asking:
"What does this AWS service do?"
I try to ask:
"What problem does this service solve?"
For example:
  • EC2 → Virtual servers in the cloud
  • S3 → Object storage
  • RDS → Managed relational databases
  • Lambda → Run code without managing servers
  • SQS → Decouple applications using message queues
Once I understand the problem a service solves, remembering the service becomes much easier.

3. Regions and Availability Zones matter

At first, Regions and Availability Zones were concepts I had to revisit a few times.
A Region is a geographic area where AWS has infrastructure, while Availability Zones are isolated locations within a Region.
Understanding this helped me see how applications can be designed for higher availability, resilience, and fault tolerance.
It's much easier to understand these concepts when you stop looking at them as definitions and start thinking about how they affect a real application.

4. Cloud security is a shared responsibility

The AWS Shared Responsibility Model was another important concept for me.
AWS is responsible for security of the cloud, while customers are responsible for security in the cloud, depending on the services they use.
This made me realize that moving an application to the cloud doesn't mean security becomes someone else's problem.
Understanding IAM, permissions, encryption, networking, and access control is an important part of becoming a good cloud professional.

5. Hands-on practice changes everything

Reading documentation and watching courses is useful, but actually using a service is a completely different experience.
Even a small experiment can make a concept much easier to understand.
For example, creating an S3 bucket, deploying a Lambda function, or connecting an application to a database can turn something theoretical into something concrete.

6. Getting confused is part of learning

There have already been concepts that I had to study more than once.
And that's okay.
Cloud computing has a lot of interconnected concepts, so sometimes something only makes sense after learning another topic first.
I've learned that instead of getting frustrated when something doesn't make sense immediately, it's better to:
Study → Practice → Get confused → Research → Try again → Understand
That's part of the process.

7. The community makes the journey better

One of the things I'm enjoying most about starting with AWS is seeing what other people are building and learning.
Different people explain the same concept in completely different ways, and sometimes a simple explanation from another builder can make something finally click.
That's one of the reasons I decided to start sharing my own learning journey here in the AWS Builder Center.
I'm hoping to learn from other builders while also documenting what I'm learning along the way.

What's next?

My current goal is to build a strong foundation in AWS and prepare for the AWS Certified Cloud Practitioner (CLF-C02) certification.
But I don't want the certification to be the final destination.
I want to take what I learn and turn it into real projects and hands-on experience, especially around Cloud, Software Development, and Generative AI.
There is still a lot ahead, but I'm excited to keep learning and building.
Let's see where this journey takes me.



What about you?

If you're also starting with AWS:
What was the first AWS concept that really confused you?
And if you've been working with AWS for a while:
What is one piece of advice you would give to someone just starting out?
I'd love to learn from the community.
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