AWS Builder Center

MODULE 3 FROM MY AWS JOURNEY: AWS INFRASTRUCTURE

In this topic, I got to learn how AWS handles their infrastructure, how it's been balanced to reduce downtime, at maximum output

Series: Documenting Learning Journey. (4 articles)

  1. …
  2. 3
    MODULE 3 FROM MY AWS JOURNEY: AWS INFRASTRUCTURE This article
Module 3: AWS Global Infrastructure 🌍☁️
Before this module, I never really thought about where my AWS resources actually live.
Then I started asking: Where does all of this run?
That led me to three key concepts:
1. AWS Regions 🌍
A Region is a geographical area where AWS operates its infrastructure. Choosing a Region can depend on factors like latency, cost, service availability, and data residency.
The question becomes: Where should my resources live, and why?
2. Availability Zones
Each Region contains multiple Availability Zones, made up of one or more data centers. They are designed to be physically separate while remaining connected through AWS's network.
This enables high availability and fault tolerance by allowing resources to be distributed across multiple AZs.
Don't put all your eggs in one basket. 😂
3. Edge Locations 🌐
Edge Locations help bring content closer to users. With Amazon CloudFront, content can be cached at edge locations, reducing latency and improving delivery speed.
My simple takeaway:
Regions → Where resources run
Availability Zones → Resilience and availability
Edge Locations → Content closer to users
AWS's global infrastructure is starting to make a lot more sense.
Module 3: Done. 🚀
On to the next one.
#AWS #CloudComputing #AWSCloudClub #LearningInPublic

Series: Documenting Learning Journey. (4 articles)

  1. …
  2. 3
    MODULE 3 FROM MY AWS JOURNEY: AWS INFRASTRUCTURE This article
Any opinions in this article are those of the individual author and may not reflect the opinions of AWS.
Enjoyed reading this content? Let the author know!

Your likes, comments, shares, and saves help creators reach more builders.

Loading recommendations

Loading article