Why I Started Learning AWS
As a full-stack developer, I have worked on applications involving frontend, backend, databases, and APIs. But building an application is only one part of the journey. Understanding how applications are deployed, scaled, secured, and monitored in the cloud is equally important.
That is why I decided to start learning AWS.
Where I'm Starting
AWS has many services, and trying to learn everything at once can be overwhelming. Instead, I plan to begin with a few fundamental services and understand what problem each one solves.
Amazon EC2
Amazon EC2 provides virtual computing resources in the cloud. I want to understand how applications can be deployed and run on EC2 instead of only running them locally.
Amazon S3
Amazon S3 provides object storage. I plan to explore how applications can use S3 for storing files, images, backups, and static content.
AWS Lambda
AWS Lambda introduces serverless computing, where code can run without managing the underlying servers. I am particularly interested in understanding where Lambda is a better choice than running a traditional backend server.
Amazon RDS
Since databases are an important part of most full-stack applications, I also want to explore how AWS manages relational databases through Amazon RDS.
AWS IAM
Before building larger projects, I want to understand IAM and how AWS manages users, roles, permissions, and secure access to resources.
My Learning Approach
Instead of learning AWS only through theory, my goal is to follow a simple cycle:
Learn → Build → Understand → Document
For every important service, I want to understand the basic concept and then use it in a small hands-on project.
For example, I can start by hosting static content using S3, deploy an application using EC2, and later experiment with serverless applications using Lambda.
What I Want to Build
As I progress, I would like to explore projects where multiple AWS services work together.
One of my goals is to take a full-stack application that currently runs locally and understand how its frontend, backend, database, storage, security, and monitoring can be designed using AWS services.
This should help me move from simply knowing individual AWS services to understanding cloud architecture.
What's Next?
This is only the beginning of my AWS journey.
I'll continue documenting what I learn, including the mistakes I make, concepts that initially confuse me, and small projects I build along the way.
If you're also beginning your AWS journey, I'd love to know which AWS service you're learning first.
Loading article