InterviewHubPRO
Section Overview
Q1

Question 1 of 65

Part 1: Intro, Architecture & Well-Architected Framework (1 - 5)

2%
AWS Cloud Architecture•Part 1: Intro, Architecture & Well-Architected Framework (1 - 5)

What is Cloud Computing, and how is the AWS Global Infrastructure structured (Regions, Availability Zones, and Edge Locations)?

In Simple Words: Cloud Computing is the on-demand delivery of IT computing power, database storage, applications, and networking resources over the internet with pay-as-you-go pricing, replacing capital expenditure (CapEx) of physical on-premise hardware with operational expenditure (OpEx).

The AWS Global Infrastructure Architecture:

  1. AWS Regions: Separate geographic locations across the globe (e.g., us-east-1 N. Virginia, eu-west-1 Ireland). Each Region is completely isolated from other Regions to achieve maximum fault tolerance and stability.
  2. Availability Zones (AZs): Each AWS Region is composed of multiple (at least 3) isolated locations known as Availability Zones. An AZ consists of one or more discrete physical data centers with redundant power, cooling, and low-latency optical networking. Multi-AZ deployments protect against physical data center outages.
  3. Edge Locations & Local Zones: Global Points of Presence (PoPs) located in major metropolitan areas worldwide. Powered by Amazon CloudFront (CDN) and Amazon Route 53 (DNS), Edge Locations cache content close to end users to deliver sub-millisecond latencies.
  4. AWS Shared Responsibility Model:
    • Security OF the Cloud (AWS): Physical hardware, global data centers, virtualization hypervisors, and managed service infrastructure.
    • Security IN the Cloud (Customer): Customer data, IAM identities, firewall/security group configurations, OS patching on EC2, and encryption.
hcl
# Terraform: Multi-AZ provider configuration and Availability Zone data query:
terraform {
  required_providers {
    aws = {
      source  = "hashicorp/aws"
      version = "~> 5.0"
    }
  }
}

provider "aws" {
  region = "us-east-1"
}

# Fetch all available Availability Zones in the region dynamically:
data "aws_availability_zones" "available" {
  state = "available"
}

output "primary_az" {
  value = data.aws_availability_zones.available.names[0] # e.g. "us-east-1a"
}
output "secondary_az" {
  value = data.aws_availability_zones.available.names[1] # e.g. "us-east-1b"
}