The Beginner’s Guide to Learning AWS (What I Wish I Had 3 Years Ago)
AWS for Beginners: The Guide I Wish I Had When Starting My Cloud Journey
When I started my cloud engineering journey with AltSchool Africa in 2022, I knew absolutely nothing about AWS. AltSchool did their best to simplify the cloud for me, but deep inside, I still felt lost. So I did what most beginners do, I ran to YouTube, blogs, documentation, the AWS website and ended up even more overwhelmed.
Too many services. Too many concepts. Too many details. Not enough clarity.
Today, even with better content online, beginners still feel the same confusion:
What exactly do I need to know first?
What should I ignore for now?
How do I avoid getting lost?
That’s why I decided to create the guide I wish someone had handed me when I first touched the cloud 3 years ago
In this article, I will walk you through:
The essential prerequisites before touching AWS
The core AWS concepts every beginner must understand
The main services you should learn first
A framework for building real, hands-on AWS skills
Extra tips and resources to speed up your learning
Let’s start from the beginning.
1. Essential Prerequisites Before Learning AWS
Before diving into AWS itself, there are a few foundational skills that will save you from being confused or overwhelmed later.
1. Basic Networking Fundamentals
You don’t need to be a networking expert.
But you should understand:
How the internet works
What an IP address is
What happens when you type a URL into your browser
Think of it as learning the road system before driving a car.
2. Linux & Virtual Machines
In the cloud world, Linux is king.
Most AWS services, servers, and tools interact with Linux in some way.
You should understand:
How a virtual machine works
Basic Linux navigation
How to install or update software on Linux
Nothing advanced just basics.
3. Command Line Basics (Very Important)
You don’t need to be a CLI ninja.
Just learn how to:
Navigate directories
Create / delete files
View and edit simple text
SSH into a server
This will keep you from getting stuck when AWS requires you to connect to a machine.
4. A Programming Language (Highly Recommended)
You can work with some areas of AWS without programming.
But knowing one language will take you much further.
Python is my top recommendation:
Easy to learn
Beginner-friendly
Used everywhere (automation, backend, data engineering, ML)
Works perfectly with AWS SDKs and services
If you already know another language, you’re fine.
But if you’re choosing your first start with Python.
5. Secure Your AWS Account (People Skip This!)
This is where people get into trouble.
A misconfigured account can lead to:
Security breaches
Surprise bills
Losing access to your own environment
Before doing anything, learn how to:
Set up MFA
Create IAM users instead of using the root account
Set billing alerts
Understand the Free Tier limits
It will save you pain later.
2. Core AWS Concepts You Must Understand
Once your foundations are set, it’s time to learn the “shape” of AWS.
1. Global Infrastructure: Regions & Availability Zones
AWS is built around:
Regions
Geographical areas (e.g., us-east-1, eu-west-1).
You choose where your infrastructure physically lives.
Availability Zones (AZs)
Independent data centers within a region.
Best practice: deploy across multiple AZs so your app stays up even if one AZ fails.
Understanding this helps you design reliable, resilient cloud systems.
3. The AWS Services Every Beginner Should Learn
AWS has over 250 services, and no one knows all of them.
But there’s a core set that almost every engineer uses.
These are the ones you should learn first.
Networking
VPC (Virtual Private Cloud)
This is your private section of AWS where your resources live.
Learn:
What a VPC is
What subnets are
What security groups are
The basics of how traffic flows
Security groups especially confuse beginners learn them early.
Compute
EC2 (Elastic Compute Cloud)
AWS’s virtual servers.
You don’t need to master every EC2 feature.
Just learn how to:
Launch a small instance
SSH into it
Install basic packages
Stop and terminate it
That’s enough for getting comfortable.
Storage
S3 (Simple Storage Service)
Arguably the most used AWS service.
It’s a highly scalable file storage system.
Know how to:
Create a bucket
Upload and download files
Understand bucket permissions
You will use S3 everywhere including serverless apps, data lakes, backups, websites, logging, and more.
Databases
Two main ones to learn:
1. RDS (Relational Database Service)
Runs traditional SQL databases like:
PostgreSQL
MySQL
SQL Server
Aurora (Amazon-founded version)
Good for structured, relational data.
2. DynamoDB
A NoSQL, key-value document store.
Massively scalable. Used heavily within Amazon and AWS services.
You don’t need to master DynamoDB now just understand what it is and where it’s useful.
Security
IAM (Identity and Access Management)
One of the most important services to learn.
IAM controls:
Who can access what
Which services can talk to which
Keys and credentials
Users, groups, and roles
AWS is permission-driven.
If you don’t understand IAM, you will regularly get stuck.
4. Should You Start With AWS Certifications?
Many beginners ask this question “Should I take AWS certifications to learn?”
Certifications can help build structure and give you motivation.
But they are not a replacement for hands-on practice.
A better approach is:
Learn the fundamentals above
Build small hands-on projects
Then take a certification when you can connect theory + experience
Think of certification as a confirmation of your skills not the source of them.
5. The Best Way to Actually Learn AWS (Hands-on Framework)
Reading, watching videos, and studying diagrams is great but none of it builds confidence.
To truly learn AWS, use this approach:
1. Pick a small project
Examples:
A static website hosted on S3
An EC2 server running a basic app
A Lambda function triggered by an S3 upload
A simple API using API Gateway + Lambda
2. Build it
Break it
Fix it
This is how you internalize AWS.
5. Repeat with slightly harder challenges
Each project should add one new complexity:
Add a database
Add a load balancer
Add IAM roles
Add monitoring (CloudWatch)
Progressive building is the fastest way to grow.
If I Were Starting AWS From Scratch Today
If I had to restart my AWS journey today, I would:
Learn basic networking + Linux
Get comfortable with the terminal
Understand AWS regions + AZs
Learn the core services (VPC, EC2, S3, RDS, DynamoDB, IAM)
Build small hands-on projects
Only then pursue certifications
AWS can feel overwhelming but if you focus on the essentials, it becomes incredibly powerful and exciting.
You don’t need to know all 250 services.
Just start with the ones that matter.
And remember:
Real skills come from building, not just watching.