AWS Global Infrastructure

Today we will learn about the global infrastructure of AWS

So what is Global Infrastructure

AWS Global Infrastructure?allows you to choose how and where you want to run your workloads, and when you do, you are using the same network, control plane, API`s, and AWS services. If you want to run your applications globally, you can choose from any AWS Regions and AZs.

What are the main components of Global Infrastructure?

1. Regions
2. AZs (Availability Zones)
3. Edge Locations or points of presence
4. Regional Edge Cache
5. Local Zones
6. Wave Length Zones

Regions

AWS has the concept of a Region, which is a physical location around the world where there are cluster data centers. Each group of logical data centers is called an Availability Zone. Each AWS Region consists of a minimum of three, isolated, and physically separate AZs within a geographic area.

AZs (Availability Zones)

An Availability Zone (AZ) is one or more discrete data centers with redundant power, networking, and connectivity in an AWS Region. AZs give customers the ability to operate production applications and databases that are more highly available, fault-tolerant, and scalable than would be possible from a single data center.

Edge Locations or points of presence

In addition to the AWS Regions and Availability Zones, AWS also operates a globally distributed point of presence (PoP) network. These PoPs host Amazon CloudFront, a content delivery network (CDN); Amazon Route?53, a public Domain Name System (DNS) resolution service; and AWS Global Accelerator (AGA), an edge networking optimization service. The global edge network currently consists of over 410 PoPs, including more than 400 Edge Locations, and 13 regional mid-tier caches in over 90 cities across 48 countries.

Each PoP is isolated from the others, which means a failure affecting a single PoP or metropolitan area does not impact the rest of the global network. The AWS network peers with thousands of Tier 1/2/3 telecom carriers globally is well connected with all major access networks for optimal performance and has hundreds of terabits of deployed capacity.

Regional Edge Cache

Regional Edge Caches are deployed globally, close to the viewers, and are located between the origin servers and the Edge Locations. Regional edge caches support multiple Edge Locations and support a larger cache size so objects remain in the cache longer at the nearest regional edge cache location. Regional edge caches help with all types of content, particularly content that tends to become less popular over time.

So what is different between Regional Edge Cache and Edge Locations?

Edge locations are not tied to Availability Zones or regions.?Regional Edge Caches are located between origin web servers and global edge locations and have a larger cache. Regional Edge Caches have larger cache-width than any individual edge location, so your objects remain in the cache longer at these locations.

Local Zones

AWS Local Zones are a type of infrastructure deployment that places compute, storage, database, and other select AWS services close to large population and industry centers.

So what is the difference between Local Zones and AZs?

Local Zones are designed to bring the core services needed for the latency-sensitive portions of your workload closer to end-users, while Availability Zones provide access to the full array of AWS services.

Wave Length Zones

Wavelength Zones are?AWS infrastructure deployments that embed AWS compute and storage services within telecommunications providers' data centers at the edge of the 5G network, so application traffic can reach application servers running in Wavelength Zones without leaving the mobile providers' network.

Then there is AWS Outpost for on-premises. It is?designed for workloads that need to remain on-premises due to latency requirements.

You can learn more about AWS Global Infrastructure in

That's it for this post. I hope you find this useful.?

keep learning, keep up to date, and keep growing.

#aws?#awscloud?#awscommunity?#awsdevops?#awscommunitybuilders?#lambda?#ec2?#amazon?#amazons3?#cloud?#cloudcomputing?#cloudarchitect?#cloudengineer?#cloudinfrastructure?#fargate?#s3?#amazoneks?#amazonec2 #awscertified #awssolutionsarchitect