AWS for Beginners: Building a Mental Map of the Cloud
Starting with AWS can feel overwhelming because there are hundreds of services. This guide breaks down the core AWS concepts and services into a simple mental map to help beginners understand what each service does and when they might use it.
AWS for Beginners: Building a Mental Map of the Cloud
When you first start learning AWS, one of the hardest parts isn't necessarily learning individual services. It's understanding how everything fits together.
AWS has hundreds of services, and seeing names like EC2, S3, Lambda, RDS, VPC, IAM, and CloudWatch all at once can make cloud computing seem much more complicated than it needs to be.
A useful way to start is to organize AWS services by the problem they solve.
- Compute: Where does my code run?
Compute services provide the resources needed to run applications and code.
Amazon EC2
EC2 (Elastic Compute Cloud) provides virtual servers in the cloud.
Instead of purchasing and maintaining a physical server, you can launch an EC2 instance and choose the amount of computing resources you need.
Think of EC2 as:
"I want a computer in the cloud that I control."
AWS Lambda
Lambda takes a different approach. Instead of managing a server yourself, you provide code that AWS runs when it is triggered.
Think:
EC2 = I manage the server.
Lambda = AWS manages the server; I provide the code.
Lambda = AWS manages the server; I provide the code.
- Storage: Where does my data live?
Amazon S3
Amazon Simple Storage Service (S3) is AWS's object storage service.
It can be used to store things such as:
Images
Documents
Datasets
Backups
Application files
Documents
Datasets
Backups
Application files
A simple way to remember it:
S3 = storage for objects and files.
For someone working with large biological datasets, this is particularly interesting because cloud object storage can provide a place to keep datasets without relying on local storage.
- Databases: Where does application data live?
Storage and databases aren't quite the same thing.
Amazon RDS
Amazon RDS makes it easier to run relational databases without managing as much of the underlying infrastructure yourself.
Amazon DynamoDB
DynamoDB is a managed NoSQL database designed for applications that need fast, scalable access to data.
A useful beginner distinction is:
S3 → files and objects
RDS → relational databases
DynamoDB → NoSQL data
RDS → relational databases
DynamoDB → NoSQL data
- Networking: How do things communicate?
This is where AWS can start feeling complicated.
Amazon VPC
A Virtual Private Cloud (VPC) lets you define a logically isolated network for your AWS resources.
You can think of it as creating your own section of the AWS network where you control things such as subnets, routing, and network access.
Other services then operate within or interact with this environment.
- Identity and security: Who can do what?
One of the most important concepts for beginners is IAM — Identity and Access Management.
IAM controls who can access AWS resources and what actions they are allowed to perform.
For example, an application might need permission to read files from an S3 bucket but have no reason to delete them.
This leads to one of the most important security principles:
Least privilege
Give an identity only the permissions it actually needs.
The question shouldn't just be:
"Does this application work?"
It should also be:
"What does this application have permission to do?"
This is one area where hands-on experimentation can be particularly useful because seeing what a permission actually allows can be much more intuitive than simply reading about it.
- Monitoring: What's happening?
Once an application is running, you need to know what is happening.
Amazon CloudWatch
CloudWatch can be used to monitor AWS resources and applications through metrics, logs, alarms, and other monitoring capabilities.
AWS CloudTrail
CloudTrail records AWS API activity, helping you understand actions taken within your AWS environment.
A simple distinction:
CloudWatch → What's happening?
CloudTrail → Who did what?
CloudTrail → Who did what?
Putting the pieces together
You don't need to memorize hundreds of AWS services to start building.
A simple mental map might look like this:
Compute
→ EC2, Lambda
→ EC2, Lambda
Storage
→ S3
→ S3
Databases
→ RDS, DynamoDB
→ RDS, DynamoDB
Networking
→ VPC
→ VPC
Security & Identity
→ IAM
→ IAM
Monitoring
→ CloudWatch, CloudTrail
→ CloudWatch, CloudTrail
Once these categories start making sense, learning additional AWS services becomes much easier because you can ask:
"What problem does this service solve?"
rather than trying to memorize another AWS product name.
Start small
If you're new to AWS, don't try to learn everything at once.
Pick a few services and build something small. Then ask yourself:
Where does my code run?
Where does my data live?
Who has access to it?
How do the components communicate?
How do I know what's happening?
How much does it cost?
Where does my data live?
Who has access to it?
How do the components communicate?
How do I know what's happening?
How much does it cost?
Those questions provide a surprisingly useful foundation for understanding cloud architecture.
The goal isn't to memorize AWS.
It's to understand the problems AWS services are designed to solve.
Enjoyed reading this content? Let the author know!
Your likes, comments, shares, and saves help creators reach more builders.
Loading recommendations
Loading article