Fawry cloud devops internship
  • Application production deployment architecture
  • Application Deployment Process
  • Application Deployment pricing
  • Kubernetes ConfigMap and Secret
  • Kubernetes Network
  • Kubernetes PV & PVC
  • kubernetea Labs
  • Kubernetes Session 3
  • Kubernetes Session 2
  • Kubernetes Architecture
  • Amazon SQS
  • AWS SNS
  • AWS Elastic Transcode
  • AWS RDS
  • Amazon Aurora RDS
  • Amazon RDS for Oracle
  • Amazon RDS for PostgreSQL
  • Amazon RDS for MySQL
  • Amazon RDS for SQL Server
  • Amazon RDS Multi-AZ with one standby
  • AWS RDS Automated Backup
  • Amazon RDS - Event Notifications
  • Amazon RDS - DB Access Control
  • Amazon RDS - Data Import / Export
  • Amazon RDS - DB Monitoring
  • Amazon RDS on VMware
  • Amazon Aurora Serverless
  • Cloud Computing
  • AWS
  • AWS Features
  • AWS Global Infrastructure
  • AWS Services
  • AWS IAM
  • AWS S3
  • AWS S3 Lifecycle Management
  • EC2
  • Instance types
  • AMI
  • EBS
  • Elastic File System
  • EC2 Lab with EFS shared
  • AWS Route53
  • AWS VPC
  • EC2 placement group
  • AWS LB
  • EC2 Auto Scaling
  • Cloud Watch
  • SeMA Deployment Architecture
    • SeMA application sizing-estimation process .
    • SeMA Deployment Architecture
  • Laravel Deployment Architecture
    • Larvel application sizing-estimation process .
    • SeMA Deployment Architecture
  • SeMA Survey Application Deployment Architecture
  • Fawry DevOps internship Agenda
  • Fawry cloud devops internship
  • User Guide
  • FAQ
  • Application Architecture
    • Architecture
    • UI : Angular 8
    • Web : PHP Laravel
    • Analytics : Metabase
    • DB : MariaDB
    • Application Security Course
  • ZiSoft Deployment
    • Non-Production Deployment
    • Kubernetes Production Deployment
    • Offline Production Deployment
    • SaaS :Kubeapps
  • Linux for DevOps
  • Architecture of Linux system
  • Linux Directory Structure
  • Linux Commands
  • Linux labs
  • Docs
  • GIT
  • Git vs SVN
  • Git Flow / Git Branching Model
  • Git Version Control System
  • Git Terminology
  • Git Commands
  • Git Remote
  • Git Stash
  • Git Merge and Merge Conflict
  • Merge vs Rebase
  • Git Tags
  • Containerization
  • Dockerfile
  • Docker Compose
  • Docker Architecture
  • DevOps part 1 : interview
Powered by GitBook
On this page
  • Availability zone as a Data Center
  • Region
  • Edge Locations
  • Regional Edge Cache

Was this helpful?

Export as PDF

AWS Global Infrastructure

Last updated 2 years ago

Was this helpful?

  • AWS is a cloud computing platform which is globally available.

  • Global infrastructure is a region around the world in which AWS is based. Global infrastructure is a bunch of high-level IT services which is shown below:

The following are the components that make up the AWS infrastructure:

  • Availability Zones

  • Region

  • Edge locations

  • Regional Edge Caches

Availability zone as a Data Center

  • An availability zone is a facility that can be somewhere in a country or in a city. Inside this facility, i.e., Data Centre, we can have multiple servers, switches, load balancing, firewalls. The things which interact with the cloud sits inside the data centers.

  • An availability zone can be a several data centers, but if they are close together, they are counted as 1 availability zone.

Region

  • A region is a geographical area. Each region consists of 2 more availability zones.

  • A region is a collection of data centers which are completely isolated from other regions.

  • A region consists of more than two availability zones connected to each other through links.

  • Availability zones are connected through redundant and isolated metro fibers.

Edge Locations

  • Edge locations are the endpoints for AWS used for caching content.

  • Edge locations consist of CloudFront, Amazon's Content Delivery Network (CDN).

  • Edge locations are more than regions. Currently, there are over 150 edge locations.

  • Edge location is not a region but a small location that AWS have. It is used for caching the content.

  • Edge locations are mainly located in most of the major cities to distribute the content to end users with reduced latency.

  • For example, some user accesses your website from Singapore; then this request would be redirected to the edge location closest to Singapore where cached data can be read.

Regional Edge Cache

  • AWS announced a new type of edge location in November 2016, known as a Regional Edge Cache.

  • Regional Edge cache lies between CloudFront Origin servers and the edge locations.

  • A regional edge cache has a large cache than an individual edge location.

  • Data is removed from the cache at the edge location while the data is retained at the Regional Edge Caches.

  • When the user requests the data, then data is no longer available at the edge location. Therefore, the edge location retrieves the cached data from the Regional edge cache instead of the Origin servers that have high latency.