Getting Comfortable with AWS: A Beginner’s Simplified Starting Point
Starting AWS can feel overwhelming when you don't know where to begin or what comes before what. As a beginner learning AWS myself, I wanted to simplify that starting point for others. In this article, I cover: * AWS fundamentals and learning order * IAM, networking, EC2, Security Groups & S3 * Learning concepts before implementation * Hands-on practice and AWS costs * Beginner do's, don'ts, and common mistakes * Staying consistent without getting overwhelmed
When I first started learning AWS, I honestly didn't know where to begin.
There are so many services, so many terms, and so many different learning paths that it can be difficult to even figure out what you should learn first.
EC2? IAM? S3? VPC? Regions? Security Groups? Availability Zones?
And then you start wondering:
"Do I need to learn all of this before I can actually use AWS?"
After spending some time learning the basics and doing a few hands-on things myself, I realised something:
You don't need to know a lot of AWS to start using AWS.
You just need to understand a few important concepts first.
I'm still learning AWS myself, so this isn't an expert road map or an official AWS learning path. It's simply my attempt to take what I've learned so far and simplify the starting point for someone who is completely new to AWS.
If you're at that stage where AWS looks complicated and you don't know what comes before what, hopefully this helps.
Start With the Basics — Seriously
When you first start learning AWS, it can be tempting to immediately jump into services.
I did that too.
But I think the most important part of starting AWS is understanding the basic concepts behind cloud computing.
Before worrying about dozens of AWS services, get comfortable with questions like:
- What is cloud computing?
- What is AWS?
- What is a Region?
- What is an Availability Zone?
- What is a server in the cloud?
- What does it mean to store something in the cloud?
- How does AWS charge for resources?
- What is the Shared Responsibility Model?
You don't need to become an expert in any of these.
You just need to reach the point where the terminology doesn't feel completely unfamiliar anymore.
That's the first milestone:
AWS should start feeling familiar instead of intimidating.
Then Learn IAM
One of the first AWS services/concepts I would recommend getting comfortable with is IAM — Identity and Access Management.
At its simplest, IAM is about controlling access to AWS resources.
Start by understanding:
- Users
- Groups
- Roles
- Policies
- Permissions
- MFA
- Least privilege
At first, IAM can feel confusing because there are quite a few new terms.
Don't worry about mastering every detail.
Just understand the basic idea:
Someone needs permission to do something in AWS. IAM controls that access.
Once that basic idea clicks, the terminology starts becoming easier.
And because permissions are involved in almost everything you do in AWS, understanding IAM early is useful.
Learn the Basic AWS Environment
Before getting too deep into individual services, it's helpful to understand where your resources actually exist.
This is where concepts such as:
- Regions
- Availability Zones
- VPCs
- Subnets
start becoming relevant.
Again, don't try to master networking at this point.
Just understand the basic picture.
For example:
AWS Region → Availability Zones → Your resources
And when you start learning about VPCs:
VPC → Subnets → Resources
You don't need to know every networking detail yet.
The goal is simply to stop thinking of AWS as one giant place where you randomly create things.
Your resources exist somewhere, inside a particular environment, with particular networking settings.
That basic understanding becomes much more useful later.
Then Get Your Hands Dirty With EC2
This was one of the points where AWS started feeling more real to me.
EC2 lets you create a virtual server in AWS.
And instead of only reading about it, actually try it.
Launch an instance.
Look at the options.
Connect to it.
Run a few commands.
Stop it.
Start it again.
Look at its settings.
And eventually, terminate it when you're finished.
While doing this, you'll come across things like:
- AMIs
- Instance types
- Key pairs
- EBS
- Public IP addresses
- Security Groups
Don't worry if all of these don't make sense immediately.
That's actually part of the learning process.
You might see something and think:
"What the hell is this?"
That's fine.
Look it up.
Understand the basic idea.
Try it.
Then move on.
You don't have to completely master one concept before you're allowed to learn the next one.
Understand Security Groups
While working with EC2, you'll probably come across Security Groups.
This is another concept worth understanding early.
At a basic level, Security Groups control what traffic is allowed to reach your resources.
For example, you might allow:
- SSH traffic
- HTTP traffic
- HTTPS traffic
The important thing isn't memorising which ports exist.
It's understanding the idea:
Your cloud resources shouldn't simply be accessible to everyone.
This is also where AWS starts connecting with cyber security.
Even basic AWS usage involves thinking about access, permissions, networking and exposure.
Learn S3
Once you're getting comfortable with basic compute, another important AWS service to explore is Amazon S3.
S3 is used for storing objects such as files and data.
Start with the simple concepts:
- Buckets
- Objects
- Uploading and downloading files
- Permissions
- Basic security
- Versioning
Don't worry about learning every S3 feature.
Just get comfortable creating a bucket, putting something inside it, retrieving it, and understanding who can access it.
The more you actually use these services, the less abstract they become.
Learn to Watch What You're Doing
This is something I think beginners should get used to early.
When you create AWS resources, don't just create them and forget about them.
Get familiar with the basics of:
- Billing
- Costs
- Resource usage
- CloudWatch
- AWS Free Tier / available credits
You don't need to become a cost-optimization expert.
Just develop the habit of knowing:
What did I create?
Is it still running?
Is it costing me anything?
Do I still need it?
And when you're finished experimenting:
Clean it up.
This is especially important when you're learning through hands-on experimentation.
So What Should You Actually Learn First?
If I had to simplify everything I've learned so far into a very basic starting path, I would put it like this:
1. Cloud & AWS Fundamentals
Understand what AWS is and learn the basic terminology.
↓
2. IAM
Understand users, permissions, policies, roles and basic account security.
↓
3. AWS Regions & Basic Networking
Understand where your resources exist and the basic idea of VPCs and subnets.
↓
4. EC2
Create and use your first virtual server.
↓
5. Security Groups
Understand the basic idea of controlling network access.
↓
6. S3
Learn the basics of storing files and objects in AWS.
↓
7. Billing & Monitoring
Understand what you're running and keep an eye on your usage.
↓
8. Start Building Small Things
Combine the concepts you've learned instead of immediately jumping to dozens of new services.
That's it.
That's the starting point.
You don't need to put Lambda, Kubernetes, Terraform, RDS, CloudFormation, load balancers and every other AWS service on your first-week checklist.
There will be plenty of time for those later.
First, become comfortable with the environment you're working in.
Don't Let the Amount of AWS Scare You
One of the biggest things I've realised while learning AWS is that the number of services can make it feel much harder than it actually is.
You'll learn one thing and discover three more things that you don't understand.
Then you'll search for those three things and discover five more.
It can become a never-ending cycle.
Don't let that stop you.
You are not supposed to understand AWS completely when you start.
You're supposed to understand one more thing than you understood yesterday.
If you don't understand something, slow down and learn the basic idea.
You don't have to memorise everything.
You don't have to understand every configuration option.
And you definitely don't have to become an AWS expert before you start using AWS.
Learn the Concept First, Then Try It
Something else I've found useful is not treating hands-on labs as a sequence of buttons to click.
Before creating something, try to understand what you're creating.
For example, don't just create an EC2 instance because a tutorial says:
"Click Launch Instance."
First understand:
What is an EC2 instance?
Then launch one.
Don't just open a port because a tutorial tells you to.
Ask:
Why am I opening this port?
Don't just create an S3 bucket.
Ask:
What am I actually storing here?
You don't need deep knowledge before experimenting.
Even a basic understanding is enough to start.
Learn a little → try it → get confused → investigate → try again.
That's a much better learning cycle than simply copying a tutorial.
A Few Beginner Do's and Don'ts
Do:
- Learn the fundamentals before chasing advanced services.
- Try things yourself instead of only watching videos.
- Ask "why?" when you see a configuration.
- Make small experiments.
- Take notes in your own words.
- Get comfortable with the AWS Console.
- Clean up resources after experimenting.
- Keep track of your AWS usage and costs.
- Accept that confusion is part of learning.
Don't:
- Try to learn every AWS service at once.
- Memorise definitions without understanding them.
- Copy tutorials blindly.
- Assume you need to know everything before building something.
- Ignore permissions and security.
- Leave resources running when you don't need them.
- Get discouraged because other people seem much further ahead.
My Biggest Takeaway So Far
I'm still very much in the process of learning AWS.
I haven't explored everything AWS has to offer, and I don't think a beginner needs to.
But after getting through the initial stage of learning the basics, I've started to feel much more comfortable navigating AWS and experimenting with its services.
And I think that's an important milestone that beginners sometimes overlook.
You don't have to be advanced to make progress.
Being able to open the AWS Console and understand what you're looking at is progress.
Being able to launch an EC2 instance and understand the basic options is progress.
Being able to understand why IAM permissions matter is progress.
Being able to create an S3 bucket and understand what it's used for is progress.
These small pieces eventually start connecting.
And once they do, AWS becomes much less intimidating.
If You're Starting AWS, Start Small
If I could go back to the beginning, I wouldn't try to learn AWS as a giant collection of hundreds of services.
I'd focus on understanding the basic building blocks first.
Learn what AWS is.
Understand the basic environment.
Learn IAM.
Understand basic networking.
Launch an EC2 instance.
Play around with it.
Learn S3.
Understand basic security.
Keep an eye on your costs.
And most importantly:
Use what you learn.
You don't need a complicated project.
You don't need an impressive architecture.
You don't need to know advanced AWS services.
You just need to start.
Because once you get comfortable with the basics, learning the next thing becomes much easier.
Start with the basics.
Understand what you're doing.
Try it yourself.
Get confused.
Figure it out.
And keep going.
Understand what you're doing.
Try it yourself.
Get confused.
Figure it out.
And keep going.
That's the approach I'm taking with AWS, and this is the simplified starting road map I would share with anyone beginning their own AWS journey.
Enjoyed reading this content? Let the author know!
Your likes, comments, shares, and saves help creators reach more builders.
Loading recommendations
Loading article