5 Mistakes I Made When Starting My AWS Journey
5 Mistakes I Made When Starting My AWS Journey
5 Mistakes I Made When Starting My AWS Journey
When I first started learning AWS, I made a simple mistake: I tried to learn everything at once.
There are hundreds of AWS services, countless tutorials, and a huge amount of information available online. At first, it felt like I needed to understand all of it before building anything.
I quickly realized that this was the wrong approach.
Here are five mistakes I made while starting my AWS journey — and what I learned from them.
1. Trying to Learn Too Many Services at Once
When you discover AWS, it is easy to jump from EC2 to Lambda, then S3, RDS, DynamoDB, ECS, CloudFormation, and many other services.
The problem is that you can spend hours studying services without actually building anything.
What I learned: start with a small project and learn only the services that you actually need.
You don't need to know all of AWS to start building with AWS.
2. Ignoring Costs
One of the first things I realized is that cloud computing is not simply about creating resources and forgetting about them.
Some resources can generate costs depending on how they are configured and used.
For a beginner, understanding the AWS Free Tier, checking billing information, and deleting resources that are no longer needed should become a habit.
What I learned: always know what resources you created and why they exist.
3. Underestimating IAM
At first, IAM can look complicated.
Users, groups, roles, policies, permissions... it is a lot to understand when you're just starting.
But security cannot be something we postpone until later.
What I learned: permissions should be intentional. Give identities only the access they actually need instead of giving broad permissions just because they make things easier.
4. Forgetting About Logs
When something doesn't work, my first instinct used to be changing code or configuration immediately.
Sometimes, the answer was already there — in the logs.
Logs are one of the most useful tools when troubleshooting cloud applications.
What I learned: before randomly changing things, check the logs and try to understand what actually happened.
This simple habit can save a lot of time.
5. Thinking I Needed to Be "Ready" Before Building
This was probably my biggest mistake.
I thought I needed to understand AWS first and build projects later.
In reality, I learned much faster when I started building.
You encounter a problem.
You research it.
You try a solution.
It doesn't work.
You investigate.
Eventually, it works — and now you actually understand why.
What I learned: building is part of learning.
You don't need to know everything before starting your first cloud project.
What I Would Do Differently Today
If I could start my AWS journey again, I would keep it simple:
- Pick one small project.
- Identify the AWS services required.
- Learn those services while building.
- Monitor costs and resources.
- Read logs whenever something goes wrong.
- Focus on understanding concepts instead of memorizing services.
AWS can feel overwhelming at first, but it becomes much easier when you stop trying to learn the entire platform at once.
The goal isn't to know every AWS service.
The goal is to know how to solve problems with the services you need.
If you're also starting your AWS journey, what's one thing you wish you had known earlier?
Enjoyed reading this content? Let the author know!
Your likes, comments, shares, and saves help creators reach more builders.
Loading recommendations
Loading article