
AWS Has 200+ Services — Which Ones Should You Actually Learn?
AWS has hundreds of services, and knowing where to start can be overwhelming. Here’s the roadmap I’m using to understand the core AWS services and how they fit together in real-world cloud architectures.
Where Should You Start?
When I started exploring AWS, I quickly realized something:
There are a LOT of services.
EC2, S3, Lambda, VPC, RDS, DynamoDB, CloudFront, IAM, ECS, EKS, SQS, SNS...
And the list keeps growing.
As I'm building my foundation in AWS, I found myself asking:
“Which services should I actually learn first?”
There are so many learning resources available, but sometimes the hardest part isn't learning a service—it's knowing where it fits and why it matters.
So I started putting together a simple roadmap for myself.
And I thought, why not share it with other people who are also starting their cloud journey?
You don't need to memorize hundreds of AWS services.
You need to understand the core building blocks of the cloud and, more importantly, understand how they work together.
Here are the services I believe every cloud learner should have on their radar.
1. IAM — Who can access what?
If you're learning AWS, start with IAM.
IAM (Identity and Access Management) controls who can access AWS resources and what they are allowed to do.
You should understand:
- Users
- Groups
- Roles
- Policies
- Permissions
- Least privilege
One thing I found important while learning IAM is that giving someone access and giving them the right access are two different things.
IAM may not be the most exciting service to start with, but it's one of the most important foundations of AWS.
2. EC2 — Your server in the cloud
Think of EC2 as a virtual computer that you can create in AWS.
You can choose the machine, configure it, install software, run applications and manage it.
If you're coming from a traditional server background, EC2 is a great place to understand how cloud compute works.
Start with:
Instances → AMIs → Key Pairs → Security Groups → EBS → Auto Scaling
3. S3 — More than just file storage
S3 is one of those AWS services you'll see everywhere.
You can use it to store:
- Images
- Videos
- Documents
- Backups
- Logs
- Static websites
- Application data
But don't stop at knowing how to upload a file.
Try to understand:
Buckets → Objects → Storage Classes → Versioning → Lifecycle Rules → Permissions
Once these concepts start making sense, S3 becomes much more than "a place to store files."
4. VPC — The networking foundation
This is where AWS starts getting really interesting.
A VPC is your virtual network in AWS.
You'll eventually come across:
- VPC
- Subnets
- Route Tables
- Internet Gateway
- NAT Gateway
- Security Groups
- Network ACLs
At first, networking can feel confusing.
I know it did for me.
But once you understand how traffic moves through a VPC, many AWS architectures suddenly become much easier to understand.
My advice: don't rush through networking.
It's worth taking your time here.
5. RDS — Managed relational databases
Need a relational database without managing everything yourself?
That's where RDS comes in.
RDS makes it easier to set up and operate relational databases in AWS.
Learn the basics of:
- Database instances
- Backups
- Multi-AZ
- Read replicas
- Security
- Database engines
And at some point, make sure you understand the difference between RDS and DynamoDB.
6. Lambda — Run code without managing servers
Lambda is where the serverless concept starts becoming real.
Instead of running a server continuously, you can run your code in response to events.
For example:
User uploads an image
↓
S3 event
↓
Lambda runs
↓
Image gets processed
No server management required.
Once you're comfortable with Lambda, explore how it works with:
API Gateway + S3 + DynamoDB + EventBridge
That's when serverless architecture starts getting really interesting.
7. Route 53 + CloudFront
Two services worth knowing when learning how applications reach users.
Route 53 → DNS and domain routing
CloudFront → Content delivery / CDN
A simple way to remember them:
Route 53 helps users find your application, while CloudFront helps deliver content efficiently.
8. Elastic Load Balancing + Auto Scaling
What happens when your application suddenly gets thousands of users?
You don't want everything depending on one server.
That's where these concepts become important.
Load Balancer
→ Distributes incoming traffic.
Auto Scaling
→ Adds or removes compute capacity based on demand.
Together, they help you build applications that can handle changing workloads.
9. CloudWatch — Don't just deploy. Observe.
One thing I think beginners sometimes overlook:
Building an application is only half the job.
You also need to know what's happening inside it.
CloudWatch helps with:
- Metrics
- Logs
- Alarms
- Monitoring
- Troubleshooting
Because when something breaks, knowing that something is wrong isn't enough.
You need to know why.
10. CloudTrail — What happened?
CloudWatch helps you monitor your resources.
CloudTrail helps answer questions like:
Who performed this action?
When did it happen?
What API call was made?
This becomes especially important when you're working with security, auditing and troubleshooting.
And then there are the services you'll meet along the way...
Once your fundamentals are comfortable, start exploring:
Application Integration
- SQS
- SNS
- EventBridge
- API Gateway
- Step Functions
Containers
- ECR
- ECS
- EKS
Infrastructure as Code
- CloudFormation
And if you're interested in AI/ML:
🤖 AI & Machine Learning
- Amazon Bedrock
- Amazon SageMaker
You don't need to learn all of these at once.
One step at a time.
What About You?
If you're learning AWS right now:
Which AWS service did you find the most confusing when you first started?
Or if you're already working with AWS:
Which service do you think every beginner should learn first?
I'd genuinely love to hear different perspectives. Maybe your answer will help someone else decide what to learn next.
Enjoyed reading this content? Let the author know!
Your likes, comments, shares, and saves help creators reach more builders.
Loading recommendations
Loading article