Day 2 of 100 Days AWS Cloud Challenge-: Unveiling the AWS Global Infrastructure: Powering the Digital World!

Rajaram Erraguntla
4 min readJul 5, 2023

--

In case, you missed reading my previous blog about cloud computing, read that before proceeding with AWS Global Infrastructure.

Cloud Computing Blog: https://iamrajaram1.medium.com/day1-of-100-days-cloud-challenge-mastering-the-cloud-unleashing-the-power-of-cloud-computing-d98755c55c85

Leveraging AWS Global Infrastructure

Let's break down the AWS global infrastructure to understand it most easily.

AWS Global Infrastructure — It's a vast network of data centers and services provided by AWS in different locations across the world.

Data Centers are commonly known as regions, These are spread across various geographic areas such as North America, Asia, Europe, etc.

AWS Global Infrastructure

Now, we will learn more about what are these regions, Availability Regions, and Edge Locations.

Regions :

In AWS there are more than 200+ services and can be launched any service or deployed an application just with a few clicks. To launch any service, the customer has to choose the region where the service is to be launched.

Moreover, the Customer prefers launching a service that is very close to the location., When a customer is near to Mumbai Area, the internet connectivity will be easy and Latency will lesser due to the shortest distance. In case if customer is launching a service for an application in a different region, the latency will be higher to access data for customers. The Request and response will take time to serve the user's request.

Region Means it's a physical location across the globe where we cluster data centers.

E.g.: Asia Pacific is a geographic location that contains regions like ‘Mumbai’ and ‘Hyderabad’. Each AWS Region consists of a minimum of three Availability Zones, isolated, and physically separate AZs within a geographic area.

SOURCE: AWS GLOBAL INFRASTRUCTURE MAP

AWS REGION NAMES AND CODES :

These region names and codes are used to identify easily which is the nearest location to launch the cloud resources.

Region Characteristics :

All the regions are fully independent and isolated. If one Region is impacted, it won't affect the other regions.

* All these regions are isolated and resources have to be manually replicated across each of them.*

AVAILABILITY ZONES:

In ASIA PACIFIC — we have two regions (Mumbai & Hyderabad)

  1. Mumbai and its region code is “ap-south-1”, for this region — there are “3 Availability zones” (ap-south-1A, ap-south-1B, ap-south-1C)
  2. Hyderabad and its region code is “ap-south-2”, for this region — there are 3 Availability zones (ap-south-2A,ap-south-2B,ap-south-3C)
AWS AVAILABILITY ZONES FOR ASIA-PACIFIC

Let, 's visualize where these Availability zones are located and what does it contain.

As we know, in every Region: we have a minimum of 3 isolated Availability zones.

What do we have in Availability Zones?

Region: A Geographical location that has more than two or more Availability zones.

Availability Zones: These are the collection of Data Centers within a region. All these AZs are isolated but connected.

REGION: ASIA PACIFIC

Why AWS has designed Availability Zones in the region?

By Designing this, AWS Provides the High Availability. In case any of the Data centers fails due to Power Supply, Security, Cooling Systems, or some intermittent issues. The Other Data centers can still be available to serve the request. Also, for each Data center to the data center, a minimum distance of 100KMS is maintained if any natural disaster occurs.

Edge Location: End Users will be accessing AWS Services. These edge locations are located for every region to distribute the content to end users to reduce latency by caching the copy of our content using Cloud Front (CDN).

AWS Edge Locations

Conclusion :

We have learned and gained some insights about AWS Global Infrastructure, Regions, Availability Regions, Data Centers, and Edge Locations.

Thank you

🌟 I want to express my heartfelt appreciation to every one of you who took the time to read my blog. I am truly grateful for your presence on this learning journey. 🌟

💡 I would also like to extend an open invitation for feedback. As I continue to share my knowledge and insights, I understand that growth comes from acknowledging and learning from our mistakes. So, if you spot any errors or have suggestions for improvement, I genuinely encourage you to correct me.

--

--

Rajaram Erraguntla
Rajaram Erraguntla

Written by Rajaram Erraguntla

MULTI-CLOUD-ENGINEER || AWS || AZURE || ORACLE ||DevOps || ELK || SPLUNK || 6xMulti-Cloud Certified (3xOCI 2xAzure 1xAWS) || Docker || Terraform || Kubernetes

Responses (1)