Cloud Computing & AWS Fundamentals Explained

A Beginner’s Guide — AWS Cloud Practitioner (Week 1)

Introduction

Cloud computing has become the backbone of modern technology. From streaming movies on Netflix to storing photos on Google Drive, we interact with the cloud almost every day — often without realizing it.

I recently started preparing for the AWS Certified Cloud Practitioner (CLF-C02) exam using Stephane Maarek’s course, and this blog is part of my Week 1 learning journey. In this post, I’ll explain the core concepts of cloud computing and AWS fundamentals in a simple and exam-oriented way, especially for beginners.

How Traditional IT Infrastructure Works

Before cloud computing, companies relied on traditional on-premises infrastructure.

This meant:

• Buying physical servers
• Setting up data centers
• Managing power, cooling, and networking
• Hiring teams for maintenance and monitoring

Businesses needed a more flexible and cost-effective solution — this is where cloud computing came in.

What Is Cloud Computing?

Cloud computing is the on-demand delivery of computing resources such as servers, storage, databases, and applications over the internet, with pay-as-you-go pricing.

Instead of owning and maintaining hardware:

• You rent resources when needed
• Scale up or down instantly
• Pay only for what you use

Real-World Examples

• Gmail — Email as a cloud service
• Dropbox — Cloud storage
• Netflix — Built entirely on AWS

Key Characteristics of Cloud Computing

These are very important for the AWS exam.

1. On-Demand Self-Service Users can provision resources without human interaction.
2. Broad Network Access Services are accessible via internet from laptops, mobiles, tablets, etc.
3. Resource Pooling Multiple customers share the same infrastructure securely.
4. Rapid Elasticity & Scalability Resources can scale up or down automatically based on demand.
5. Measured Service (Pay-as-you-go) You pay exactly for what you consume.

Remember the acronym-OBRRM

Cloud Deployment Models

1.Public Cloud

• Owned and operated by cloud providers
• Resources shared among customers
• Example: AWS

Use case: Startups, web apps, SaaS products

2. Private Cloud

• Used by a single organization
• More control and security
• Higher cost

Use case: Banks, government systems

3.Hybrid Cloud

• Combination of private and public cloud
• Sensitive data on-premise, rest on cloud

Use case: Enterprises migrating gradually to cloud

Cloud Service Models (Exam Favorite ⭐)

1.Infrastructure as a Service (IaaS)

• You manage OS and applications
• Cloud provider manages hardware

Example: Amazon EC2

2.Platform as a Service (PaaS)

• You deploy applications
• Platform manages OS and runtime

Example: AWS Elastic Beanstalk

3.Software as a Service (SaaS)

• Fully managed application
• No infrastructure management

Example: Gmail, Dropbox

AWS Global Infrastructure

AWS has built a global, highly available infrastructure.

1.Regions

• A geographical area (e.g., us-east-1)
• Most services are region-specific.

2.Availability Zones (AZs)

• Multiple isolated data centers within a region.
• Designed for fault tolerance and high availability

Best practice: Deploy across multiple AZs

3.Edge Locations

• Used for content delivery (CloudFront)
• Reduces latency for end users

checkout this link for AWS Regions, Availability Zones and Edge Locations

Shared Responsibility Model

A very important concept for AWS exams.

AWS is responsible for:

• Physical data centers
• Hardware, networking, infrastructure
• Security of the cloud

Customer is responsible for:

• Data security
• IAM (users, roles, permissions)
• OS, applications, configurations
• Security in the cloud

Mnemonic: AWS secures the cloud, customer secures what’s inside it.

Conclusion

In Week 1 of my AWS Cloud Practitioner journey, I learned:

• How cloud computing works
• Why businesses prefer cloud over traditional IT
• Core AWS concepts like Regions, AZs, and the Shared Responsibility Model

These fundamentals form the foundation for all AWS services, and understanding them clearly makes future topics much easier.

In the next phase, I’ll dive into AWS IAM, security, and access management.

This blog is part of my AWS Certified Cloud Practitioner (CLF-C02) preparation journey.