AWS vs Cloud: What Are You Actually Learning?
AWS is a cloud provider, but cloud computing is much bigger. Learn the concepts behind AWS services and build cloud knowledge that goes beyond one platform.
AWS vs Cloud: What Are You Actually Learning?
When I first started learning AWS, I thought learning cloud computing basically meant learning AWS services.
Learn EC2. Learn S3. Learn Lambda. Learn RDS.
Then learn more AWS services.
But there is an important distinction:
Learning AWS is not exactly the same as learning cloud computing.
AWS is a cloud provider.
Cloud computing is the much broader set of concepts, architectures, and technologies behind those services.
Understanding this difference changed how I approached learning AWS.
1. AWS Is Not the Cloud
Amazon Web Services (AWS) is a cloud computing platform.
But AWS itself is not "the cloud."
Other major cloud platforms exist, including Microsoft Azure and Google Cloud.
At a very simplified level:
1
2
3
4
5
Cloud Computing
│
┌────────────┼────────────┐
│ │ │
AWS Azure Google CloudEach provider has its own services, names, interfaces, and ecosystem.
But many of the fundamental problems they solve are similar.
For example, applications need somewhere to run.
AWS offers services such as Amazon EC2.
Microsoft Azure has Virtual Machines.
Google Cloud has Compute Engine.
The product names are different, but the underlying concept is similar:
Compute resources running in the cloud.
This is why understanding the concept behind a service can be more valuable than simply memorizing its name.
2. Think in Concepts Before Services
Imagine you want to build a web application.
Before thinking about AWS, your application already has certain requirements.
It needs:
1
2
3
4
5
6
7
8
Application
│
├── Compute
├── Storage
├── Database
├── Networking
├── Security
└── MonitoringThese are cloud and software architecture concepts.
AWS provides services that can solve these problems.
For example:
| Concept | Example AWS Services |
|---|---|
| Compute | EC2, Lambda, ECS |
| Object Storage | S3 |
| Database | RDS, DynamoDB |
| Networking | VPC, Route 53, Elastic Load Balancing |
| Security & Access | IAM |
| Monitoring | CloudWatch |
| Containers | ECS, EKS |
| Messaging | SQS, SNS |
Instead of thinking:
"I need to learn 50 AWS services."
I find it much easier to think:
"I need to understand the problems these services are designed to solve."
Once the concept makes sense, the service becomes much easier to understand.
3. Example: Learning EC2 vs Learning Compute
Suppose I learn how to launch an EC2 instance.
I choose an instance type, configure a Security Group, connect to the machine, install my application, and start the server.
That's useful AWS knowledge.
But what did I actually learn?
At the AWS level:
1
2
3
4
5
Amazon EC2
Security Groups
EBS
AMI
Instance TypesAt the cloud level, I am learning concepts such as:
1
2
3
4
5
6
Virtual Machines
Compute Resources
Virtual Networking
Block Storage
Machine Images
ScalabilityThe first group helps me use AWS.
The second group helps me understand cloud infrastructure.
Both are important.
But the second group is more transferable.
4. The Same Idea Applies to Storage
Take Amazon S3.
If I only memorize AWS terminology, I might learn:
1
2
3
4
5
S3
↓
Bucket
↓
ObjectBut behind S3 is a broader concept:
Object storage
Now I can ask better questions.
How is object storage different from block storage?
When should an application store files in object storage instead of a traditional file system?
How does object storage scale?
Why is it useful for images, videos, backups, logs, and static assets?
Now I am not only learning how to click "Create bucket."
I am learning why that type of storage exists.
5. What About IaaS, PaaS, and Serverless?
Another useful part of learning cloud computing is understanding how much infrastructure you are responsible for managing.
Infrastructure as a Service
A virtual machine is a common example.
You receive infrastructure, but you still manage many parts of the environment.
Conceptually:
1
2
3
4
5
6
7
8
9
Cloud Provider
↓
Infrastructure
↓
Virtual Machine
↓
Your OS
↓
Your ApplicationAmazon EC2 is an example of a service that fits this model.
Managed Platforms and Services
Cloud providers can also manage more of the infrastructure for you.
Instead of managing everything yourself, you focus more on your application or data.
Managed database services are a good example.
With Amazon RDS, AWS handles many infrastructure-related tasks that would otherwise be your responsibility when operating a database server yourself.
Serverless
Serverless takes the abstraction even further.
With AWS Lambda, you focus primarily on your code and its execution.
Conceptually:
1
2
3
4
5
Event
↓
Your Function
↓
ResultYou don't provision and maintain a traditional server for each function.
The servers still exist somewhere.
You simply don't manage them directly.
This is an important cloud concept:
Serverless doesn't mean there are no servers. It means the infrastructure is abstracted away from you.
6. Containers Are Another Cloud Concept
Docker is not an AWS technology.
Containers are not exclusive to AWS either.
You might build a container locally:
1
2
3
4
5
Application
↓
Docker Image
↓
ContainerThen decide to run it on AWS using Amazon ECS or Amazon EKS.
But the knowledge of:
- Containers
- Images
- Registries
- Orchestration
- Scaling
- Service discovery
goes beyond AWS.
AWS provides services that implement or support these concepts.
That distinction matters.
7. What Knowledge Transfers Between Cloud Providers?
Suppose one day you move from AWS to another cloud provider.
Knowing where every button is in the AWS Console may not help much.
But understanding concepts such as these will:
- Virtual machines
- Containers
- Object and block storage
- Virtual networks
- Load balancing
- DNS
- Identity and access management
- Relational and NoSQL databases
- Auto scaling
- Serverless computing
- Monitoring and observability
The implementation will change.
The terminology may change.
The architecture concepts remain useful.
For example:
1
2
3
4
5
6
7
8
9
10
11
12
13
Concept: Virtual Machine
AWS
↓
EC2
Azure
↓
Virtual Machines
Google Cloud
↓
Compute EngineYou still need to learn each provider's implementation.
But you are no longer starting from zero.
8. So Should You Learn AWS or Cloud First?
I don't think they need to be separated.
A better approach is to learn them together.
For every AWS service you study, ask two questions:
1. What cloud problem does this service solve?
and
2. What is the underlying concept?
For example:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
EC2
→ Virtual Machines / Compute
S3
→ Object Storage
RDS
→ Managed Relational Databases
Lambda
→ Serverless / Event-driven Compute
ECS
→ Container Orchestration
VPC
→ Virtual Networking
IAM
→ Identity and Access Management
CloudWatch
→ Monitoring and ObservabilityNow your AWS learning becomes cloud learning at the same time.
9. A Better Way to Study AWS
Instead of learning services randomly:
1
2
3
4
5
6
7
8
9
EC2
S3
Lambda
RDS
ECS
CloudFront
SQS
DynamoDB
...I prefer grouping them by concepts:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
Cloud Fundamentals
↓
Compute
↓
Storage
↓
Networking
↓
Databases
↓
Security
↓
Containers
↓
Serverless
↓
Monitoring
↓
ArchitectureThen learn how AWS implements each area.
This makes the AWS ecosystem feel much less overwhelming.
You stop seeing hundreds of unrelated services.
Instead, you start seeing building blocks.
Final Thoughts
AWS is a toolset.
Cloud computing is the bigger picture.
When you learn Amazon EC2, don't just learn how to launch an instance.
Learn virtual machines and compute.
When you learn Amazon S3, don't just learn how to create a bucket.
Learn object storage.
When you learn Amazon VPC, don't just memorize AWS networking options.
Learn networking.
And when you learn AWS Lambda, don't just learn how to create a function.
Learn serverless and event-driven architecture.
The goal isn't:
"How many AWS services do I know?"
A better question is:
"What problems do these services solve, and do I understand the concepts behind them?"
Once you start learning AWS this way, you aren't just learning one cloud platform.
You're building a foundation for understanding cloud architecture itself.
Enjoyed reading this content? Let the author know!
Your likes, comments, shares, and saves help creators reach more builders.
Loading recommendations
Loading article