AWS Builder Center
Things I got completely wrong while learning AWS

Things I got completely wrong while learning AWS

Starting my AWS journey made me realize that some of the things I thought I understood about cloud were completely different from how they actually work. Here are five misconceptions I had, and the ideas that finally made them click.

I'm still learning AWS, and one thing I've realized is that the hardest part isn't always learning the services.
Sometimes it's about realizing that what you thought you understood wasn't quite right.
When I first started learning cloud, I had quite a few assumptions that sounded reasonable in my head. Then when I started learning how things actually work, some of those assumptions slowly fell apart.
Here are a few things I got wrong:
  1. "The cloud is just someone else's computer."
Okay, this one isn't completely wrong.
But thinking of cloud as simply "a computer somewhere else" made it difficult for me to understand why things like Regions, Availability Zones, networking, IAM, scalability, and managed services matter so much.
There is a lot more going on than simply renting a computer.
  1. "EC2 is basically just a normal computer."
At first, I thought:
My laptop = computer EC2 = another computer
So I assumed that once I launched an EC2 instance, I basically had a ready-to-use server and could treat it just like my own computer.
But then I started learning what actually goes into an EC2 environment.
An EC2 instance is a virtual server, but I still have to think about things like the operating system, CPU and memory, storage, networking, security groups, access, and what software I want to install and run on it.
And that's when it clicked for me:
EC2 gives me the computing infrastructure, but I am still responsible for managing much of what happens inside and around that server.
It's not simply "AWS gives me a computer."
It's more like:
  • AWS provides the virtual infrastructure
  • I configure and manage the server according to what my application needs.
That distinction helped me understand why cloud isn't just about getting a server. It's also about understanding the infrastructure surrounding that server.
  1. "Serverless means there are no servers."
This one confused me for a while.
Obviously, something has to run the code somewhere.
What started making sense to me about serverless is I don't have to manage the underlying servers myself.
That small distinction completely changed how I understood services such as Lambda.
  1. "Networking is something I'll learn later."
Probably my biggest mistake.
When I first saw things like VPCs, subnets, route tables, internet gateways, NAT gateways, and security groups, I thought:
"I'll understand these once I get deeper into AWS."
Then I realized that understanding networking actually makes AWS much easier to understand.
A lot of the AWS services I was learning started making more sense once I understood the networking underneath them.
  1. "I need to memorize AWS services."
AWS has a lot of services.
At first, I felt like learning AWS meant remembering what every service does.
Now I'm starting to think differently.
Instead of asking:
"How many AWS services do I know?"
I'm trying to ask:
"What problem am I trying to solve, and which service is designed for that problem?"
That shift has made learning feel much less overwhelming.
What I'm learning from all of this?
  • I'm realizing that learning cloud isn't really about memorizing a giant list of services.
  • It's about building a mental model of how everything fits together.
  • And honestly, I'm still figuring it out.
  • That's what makes learning AWS interesting for me right now. Every new concept seems to connect to something I learned before.
So I'm curious:
What AWS or cloud concept did you completely misunderstand when you first started?
I'd love to hear them, especially the ones that only "clicked" after you had already been learning for a while.
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