Getting Started with AWS: History, Global Infrastructure & Fundamentals

Introduction

As part of my journey toward mastering AWS Solutions Architect and system design, I started by understanding the foundation of AWS — its history, scale, and global infrastructure.

Before deploying EC2 or designing scalable systems, it is important to understand how AWS evolved and how its global architecture works.

AWS Cloud History

Understanding AWS history gives context to its dominance today.

• 2002 – AWS launched internally inside Amazon

• 2003 – Amazon realized infrastructure was one of its core strengths and decided to commercialize it

• 2004 – First public launch with Amazon SQS

• 2006 – Relaunched publicly with SQS, S3, and EC2

• 2007 – Expanded into Europe

What started as internal infrastructure became the backbone of modern cloud computing.

AWS Cloud – Market Facts

AWS is not just popular — it is dominant.

• In 2023, AWS generated $90 billion in annual revenue

• In Q1 2024, AWS holds 31% market share (Microsoft Azure is second with 25%)

• Recognized as a leader in the cloud market for 13 consecutive years

• Over 1,000,000 active users worldwide

This scale explains why AWS knowledge is critical for modern architects.

AWS Cloud Use Cases

AWS enables building sophisticated and scalable systems across industries:

• Enterprise IT

• Backup & Storage

• Big Data analytics

• Website hosting

• Mobile & Social apps

• Gaming platforms

In short: If it runs at scale, AWS likely supports it.

AWS Global Infrastructure

AWS global architecture is built on four key layers:

• Regions

• Availability Zones (AZs)

• Data Centers

• Edge Locations (Points of Presence)

Reference:
https://aws.amazon.com/about-aws/global-infrastructure/regions_az/

AWS Regions

AWS has regions worldwide.

Examples:

• us-east-1

• eu-west-3

A Region is a cluster of data centers.

Most AWS services are region-scoped, meaning resources you create belong to a specific region.

How to Choose an AWS Region?

When launching a new application, consider:

1. Compliance requirements
   Data should not leave a region without permission.

2. Proximity to customers
   Closer region = lower latency.

3. Service availability
   Not all services are available in every region.

4. Pricing
   Pricing varies across regions.

This is a fundamental architectural decision.

AWS Availability Zones (AZs)

Each region has multiple AZs (usually 3–6).

Example:

• ap-southeast-2a

• ap-southeast-2b

• ap-southeast-2c

Each AZ:

• Contains one or more discrete data centers

• Has redundant power and networking

• Is isolated from other AZs for disaster protection

• Connected via ultra-low latency networking

This enables high availability architecture.

AWS Edge Locations (Points of Presence)

AWS has:

• 400+ Edge Locations

• 10+ Regional Caches

• 90+ cities

• 40+ countries

These locations deliver content closer to users, reducing latency.

Services like CloudFront leverage this.

Global vs Region-Scoped Services

Global Services

• IAM (Identity & Access Management)

• Route 53 (DNS)

• CloudFront (CDN)

• WAF (Web Application Firewall)

These operate globally.

Region-Scoped Services

• Amazon EC2 (IaaS)

• Elastic Beanstalk (PaaS)

• Lambda (FaaS)

• Rekognition (SaaS)

Understanding this distinction is crucial for designing cloud architectures.

Final Thoughts

Before building scalable systems, understanding AWS infrastructure fundamentals is essential.

As I progress in my AWS learning journey, my focus is to:

• Design highly available systems across multiple AZs

• Deploy scalable architectures

• Optimize latency using Edge locations

• Build production-grade cloud systems

This is the foundation for architect-level cloud expertise.

GitHub repository with notes and diagrams:
[https://github.com/JaniShaik/aws-cloud-fundamentals]

Connect with me on LinkedIn:
[https://www.linkedin.com/in/jani-shaik-a1550731/]