Hi folks! Welcome to Day 6 of 100 Days of AWS🎯, where we will cover the complete AWS cloud from beginner to professional. Today, we will expand our horizons in the AWS cloud by Understanding AWS Global Infrastructure. selecting the region for deploying your application and service and obtaining maximum benefit out of it. what are availability zones and reason for keeping them isolated within a region? reducing the latency time by leveraging the Edge Location. and finally with a comparison of Edge locations and Local zones. Let’s get started🚀!
Day 5 Overview;
On Day 5 we discussed about IAM and its entities and how the Users are Authenticated & Authorized to access AWS resources. policies and writing custom policies. eliminating the overhead of maintaining IAM for Accounts by leveraging IAM Identity center so that maintaining in central location. Grouping AWS accounts into a single organization, and creating a subset of accounts has an Organization Unit. Service Control Policy.
Global Infrastructure Overview;
Regions;
AWS Region is a Geographical location around the world where Data Centers are clustered.
Each region is designed to be isolated from another region. therefore any natural or catastrophic disaster in one region will not affect other regions.
All the regions are Fault Tolerant and Highly stable. Currently, AWS has 36 launched regions with multiple availability zones.
how to select a Region;
All regions are not the same. Not all services are available in all regions.
Cost varies from region to region.
if you want your data to be compliant and regulated then it is mandatory to check does the region supports the necessary regulations
You should select regions as close to your customer’s location to reduce the latency time. and serve your content faster to the customer.
Availability Zone;
An Availability Zone (AZ) is one or more discrete data centers with redundant power, networking, and connectivity in an AWS Region.
All AZs in an AWS Region are interconnected with high-bandwidth, low-latency networking, over fully redundant, dedicated metro fiber providing high-throughput, low-latency networking between AZs. All traffic between AZs is encrypted.
AZs make partitioning applications for high availability easy. If an application is partitioned across AZs, companies are better isolated and protected from issues such as power outages, lightning strikes, tornadoes, earthquakes, and more.
AZs are physically separated by a meaningful distance, many kilometers, from any other AZ, although all are within 100 km (60 miles) of each other.
- If you have an application deployed in only one AZ, then the entire region is affected in case of failure in that AZ. so it is always suggested to replicate your application among multiple AZ so that your application will be highly available
Global Content Delivery & Edge Locations;
If you have your web server deployed in the US-east-1 region and initially all of the requests are within the surrounding area, then the application is served with less latency time. But if the request originates from India, then the request and response time will increase, which leads to customer dissatisfaction.
Also, replicating the webserver in another region will double the cost, so there is an Edge Location that primarily has Content Delivery services like Cloud Front, which will cache your content for faster delivery.
Local Zone;
Local zones are extensions of an AWS region located near the region.
They allow you to use select AWS services like compute, and storage. closer to the end user.
They provide a high bandwidth secure connection to the parent AWS region.
Great for low latency applications like real-time gaming, live streaming, and virtual workstation for local city.
Edge Locations vs Local Zone
Both help services get closer to the end user to improve user experience and reduce latency.
Local Zones are extensions of a region physically located across major cities in the world. whereas Edge Locations are small geographically dispersed compute sites that primarily support services like CloudFront, Route 53, and AWS WAF.
Local Zones have their own isolated Infrastructure but are connected to the parent AWS region through a high bandwidth network link.
Local Zone provides access to a subset of services like EC2 & EBS. whereas edge locations are limited to mostly CDN service not full compute service.
There are 100’s of Edge Locations since they are not full-sized datacenter; there are over 20+ Local zones.
Day 6 Wrap up;
On Day 6 of 100 Days of AWS, we covered the extensive use of AWS’ global Infrastructure, ensuring the application is Highly Available, and Fault-tolerant using the Availability zone, Edge Locations to reduce the latency time and Local Zone to extend the Parent AWS regions compute capacity. and compared and contrast of Local Zone and Edge Location.
Summary & Key Points;
Regions are locations to which certain services can be deployed.
Not all Regions have all services. it becomes necessary to evaluate and select regions suitable for your application workload.
Availability Zones(AZ) are isolated and independent data centres inside the regions.
Edge Locations are smaller points of presence where services are run close to the customers.
Local Zones are extensions of the AWS region located near the selected Metropolitan areas.
Up next on Day 7;
Introduction to Networking in AWS Cloud.
Exploring AWS’ Default VPC, Subnet, and much more.