Introduction to AWS - From Zero to Cloud-Ready

What you will learn

• What AWS is, why it exists, and what you can actually build with it
• How AWS's global infrastructure works - Regions, AZs, and Edge Locations
• The difference between Global and Regional services (and why it matters daily)
• How to choose the right AWS Region for your workload
• The three cloud service models and the Shared Responsibility Model
• How to navigate the AWS Console and avoid the most common beginner mistakes

Why this matters

Before you touch a single AWS service, you need to understand the foundation. Every decision you make - where to deploy, how to design for availability, how to reduce latency - traces back to understanding how AWS is structured globally. Engineers who skip this foundation spend months debugging problems that are architectural, not code-level.

What is AWS and What Can You Build?

AWS (Amazon Web Services) is a cloud provider. Instead of buying physical servers, networking equipment, and storage hardware, you rent it from AWS - on demand, paying only for what you use.

Think of it like Swiggy - they don't own a fixed fleet of bikes for every city. They scale delivery partners up during lunch rush and down at midnight. AWS does the exact same thing for your servers:

Amazon.in, Netflix, Swiggy, BYJU'S, Zomato, Zerodha, Razorpay, and Hotstar all run on AWS. It's not just for big companies - a solo developer in Pune uses the same infrastructure as a billion-dollar startup.

💡 Tip: AWS didn't start as a product. Amazon built it for their own e-commerce platform, then opened it to the world. That's why it's battle-tested - it was built to survive Amazon's own scale first.

AWS has 200+ services, but you don't need all of them. Here's what gets built with the core ones:

📌 Remember: Mastering 15-20 core AWS services covers 90% of real-world DevOps work. That's exactly what this course focuses on.

AWS Global Infrastructure - The Three Layers

This is the single most important concept to understand before using any AWS service.

Layer 1 - AWS Regions

A Region is a cluster of data centers in a specific geographic location. Each has a code name — ap-south-1 is Mumbai, us-east-1 is Virginia, eu-central-1 is Frankfurt. Most AWS services are region-scoped: an EC2 instance you launch in Mumbai is completely invisible when you're looking at Singapore. Resources don't cross regions automatically.

Layer 2 - Availability Zones (AZs)

Every Region contains multiple AZs (usually 3, min 3, max 6). Each AZ is one or more discrete data centers — physically separated, on different power grids, connected by AWS's own private high-bandwidth fiber.

This is why you always deploy across multiple AZs. If your entire app runs in ap-south-1a and that AZ goes down, you're fully down.

Layer 3 - Edge Locations (Points of Presence)

AWS has 400+ Edge Locations across 90+ cities. These aren't full regions - they're smaller caching and routing points close to end users. India alone has 10+ edge locations.

Edge Locations power CloudFront (CDN), Route 53 (DNS), and Global Accelerator.

Global vs Regional Services - the one thing that confuses everyone:

📌 Remember: When you switch regions in the AWS console (top-right dropdown), your EC2 instances, RDS databases, and Lambda functions all change. You're looking at a completely different environment. IAM users don't change - they're global.

How to Choose an AWS Region

🔴 Common Mistake: Defaulting to us-east-1 because it's the AWS console default — even when your users are in India and RBI mandates local data storage. If you're building for Indian users, start in ap-south-1 (Mumbai). Always make this decision deliberately.

The Three Cloud Service Models and Shared Responsibility

AWS spans all three cloud computing delivery models. Knowing which model a service falls under tells you how much you need to manage.

Most DevOps work sits at the IaaS level (EC2, VPC, RDS) with some PaaS services (Lambda, ECS Fargate) layered in for specific workloads.

The Shared Responsibility Model goes hand-in-hand with understanding service models. The more you manage (IaaS), the more security responsibility you carry:

⚠️ Security: In 2021, a misconfigured S3 bucket exposed Aadhaar-linked data of millions of Indians — that was the company's fault, not AWS's. AWS provided the bucket. The company left it public. Your configuration is your responsibility.

Hands-on Practice - Explore AWS Infrastructure

Before you deploy a single resource, spend 10 minutes understanding the environment. Open console.aws.amazon.com — the AWS Management Console. Three things to note immediately: the Region selector (top right, always check this first), the Search bar (fastest way to find any service), and the fact that switching regions shows you a completely different set of resources.

1. Go to https://infrastructure.aws/ — explore the interactive global map, find India's edge locations
2. Open the AWS Console → click the Region dropdown (top right) → switch to ap-south-1 (Mumbai) — this is your default for Indian workloads
3. Go to https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services → search for "Lambda" → find which regions don't have it
4. Open IAM in the console → notice the Region selector is greyed out — IAM is a Global service
5. Open EC2 → switch between ap-south-1 (Mumbai) and us-east-1 (Virginia) → your instances are completely separate — like two different countries

💡 Tip: Pin EC2, IAM, VPC, S3, and CloudWatch to your console toolbar. As a DevOps engineer, you'll live in these five services daily.

Expected Result: You understand that AWS is not one place. It's a global network of isolated regions (each with multiple AZs), stitched together by a private backbone, with 400+ edge locations pushing content close to users — including 10+ across India alone.