What I Learned While Using AWS for the First Time

Introduction

When I started using AWS, I thought it would be straightforward. I assumed I would follow a few steps, deploy my application, and everything would just work.

That did not happen.

This article is about my first real experience with AWS, what confused me, what went wrong, and what I learned along the way. I am not an expert, but if you are a beginner starting with AWS, this might save you some time and frustration.

Why I Started Using AWS

I was working on a small personal project and wanted to move it from my local machine to the cloud. Running everything on my laptop felt limiting, and I wanted to understand how real applications are deployed in the real world.

AWS seemed like the right choice because:

• It is widely used in industry
• It has many services for different needs
• Most cloud learning resources are based on AWS

My First Confusion with AWS

The first thing that confused me was how many services AWS has.

I kept asking myself:

• Do I need EC2 or ECS?
• What is the difference between IAM roles and users?
• Why do I need a VPC?
• Why is nothing accessible even though my app is running?

At first, AWS felt overwhelming because everything depends on something else. Nothing works in isolation.

What I Tried First

I decided to start simple.

I launched an EC2 instance and tried to deploy my backend application on it. I connected using SSH, installed dependencies, and ran my app.

The application started successfully, but I could not access it from the browser.

What Went Wrong (And Took Me Time to Understand)

The problem was security groups.

Even though my application was running, AWS was blocking traffic by default. I learned that:

• AWS does not expose anything unless you explicitly allow it
• Security groups act like a firewall
• You must open the correct port (for example, port 80 or 8000)

Once I fixed the security group rules, my app became accessible.

This small issue taught me a big lesson: In AWS, security comes first, even if it makes things harder for beginners.

IAM Was the Hardest Part for Me

IAM was the most confusing AWS service for me.

I struggled to understand:

• Users vs roles
• Policies and permissions
• Why something fails with “Access Denied”

Over time, I learned an important rule:

If something works locally but fails on AWS, it is often an IAM permission issue.

Instead of guessing, I started reading error messages carefully and checking policies line by line.

What I Learned Overall

Here are the most important lessons from my first AWS experience:

• AWS is powerful, but it expects you to be explicit
• Nothing is open or accessible by default
• Security and permissions are core concepts, not optional
• Small misconfigurations can block everything
• Reading error messages carefully saves a lot of time

Most importantly, I learned that struggling is part of learning AWS.

Many Resources Can Help You Learn AWS

One thing I truly appreciate about AWS is the amount of learning resources available.

There are countless blogs, tutorials, videos, documentation pages, and community posts that explain how different AWS services work. Whenever I felt stuck or confused, chances were that someone else had already faced the same issue and shared their solution online.

I especially want to say thank you to the creators and community members who take the time to write articles, record videos, and answer questions. Their content helped me a lot during long debugging sessions when things were not working as expected.

A Note on AI Tools and Creativity

Today, we also have powerful AI tools that can help with learning, debugging, and even coding. These tools are great for speeding things up and exploring ideas faster.

However, I believe the real value comes from starting with your own idea first.

Build something based on your own curiosity. Struggle a little. Make mistakes.

Then use AI as an enhancement, not a replacement.

Your creativity, your decisions, and your learning process are what truly add value. AI can support that journey, but it should not replace the joy of building something from scratch.

Who This Article Is For

This article is for:

• Beginners starting AWS for the first time
• Students deploying their first cloud project
• Anyone who feels overwhelmed by AWS services

If AWS feels confusing right now, that is normal. It slowly makes sense with practice.

Thanks for reading

If this helped you, feel free to share it with someone else who is starting their AWS journey.