AWS Builder Center

From Learning AWS to Actually Using It: What Changed for Me

Learning AWS through courses is one thing. Understanding why those services matter when you're actually building something is completely different. Here’s what changed for me when I moved from theory to practical exposure.

For a long time, I thought learning cloud meant understanding services, remembering their definitions, and completing courses.
Then I started working on real projects.
That's when I realized that knowing what EC2, S3, RDS, IAM, VPC, Lambda, and other AWS services are is only the beginning.
The real learning starts when you have to figure out why you need a particular service and how everything fits together.

Theory Gives You the Foundation

Courses like AWS Cloud Practitioner Essentials helped me understand the fundamentals of cloud computing and the AWS ecosystem.
I learned about:
  • Compute
  • Storage
  • Databases
  • Networking
  • Security
  • Pricing and billing
  • AWS's shared responsibility model
All of this is important.
But there's a difference between knowing that a service exists and knowing when you should actually use it.
For example, knowing that S3 provides object storage is easy.
Understanding why an application should store uploaded files in S3 instead of directly on a server requires a completely different kind of thinking.

Real Projects Change the Way You Learn

When you're working on an actual application, you don't get a perfectly structured question saying:
"Which AWS service should you use here?"
Instead, you get a problem.
You have to investigate it, understand the requirements, look at the available options, and decide what makes sense.
Sometimes you don't even know the answer initially.
And that's actually where the learning happens.
I have found that when I encounter something I don't understand and have to solve it within a short timeframe, I learn much faster than when I'm simply studying it because it's part of a course.

The Shift From "What Is It?" to "Why Use It?"

This has probably been the biggest change in my learning.
Instead of asking:
"What is AWS Lambda?"
I find myself asking:
"Would Lambda actually make sense for this particular problem?"
Instead of:
"What is an RDS database?"
It's:
"Do I need a managed relational database here, or would another approach make more sense?"
That shift seems small, but it changes how you approach technology.
You stop learning services individually and start thinking about systems.

AWS Is a Huge Ecosystem

One thing I have realized while learning AWS is just how large the ecosystem is.
There are services for almost every part of a modern application.
That can be exciting, but it can also be overwhelming when you're starting out.
You don't need to know every AWS service.
At least, I don't think that's the right goal.
A better goal is to understand the fundamentals well enough that when you encounter a new problem, you know how to investigate it and where to start looking.

What I'm Focusing on Now

Rather than trying to memorize the AWS service catalog, I'm focusing on three things:

1. Understanding the fundamentals

I want to build a strong understanding of networking, compute, storage, databases, security, and cloud architecture.

2. Building things

The best way I've found to understand a technology is to actually use it.
Even small projects can reveal things that a course doesn't necessarily teach you.

3. Learning when things break

Debugging has probably taught me more than simply getting something to work.
When something doesn't behave as expected, you are forced to understand what is happening underneath.

My Biggest Takeaway

The biggest thing I've learned so far is that practical exposure changes how you learn technology.
Courses give you direction.
Documentation gives you knowledge.
But actually building and solving problems forces you to connect everything together.
I'm still very much in the learning phase with AWS, but that's what makes it interesting.
There is always another service to explore, another architecture to understand, and another problem to solve.
And honestly, that's the part I'm enjoying the most.

What's Next?

I'm planning to continue learning AWS by building more, experimenting with different services, and gradually moving from understanding individual services to designing complete cloud-based systems.
The goal isn't to know everything.
It's to become comfortable enough with the cloud that when a new problem comes up, I can figure it out.
That's the skill I'm hoping to build.
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