~/ nmadiraju.com Amazon EKS · Local Zones and Outposts
arrow_back Back to nmadiraju
Visual Walkthrough · Amazon EKS compute

How Local Zones and Outposts Work with Amazon EKS

Follow game-server to players in Los Angeles, then a hospital's records app onto an Outpost, then check yourself with 8 questions.

1Visual Walkthrough

An EKS cluster with nodes in a Los Angeles Local Zone, and a hospital Outpost running EKS An AWS Region, us-west-2, holds two EKS control planes and a VPC with a us-west-2a subnet and a Local Zone subnet in Los Angeles. Players in LA reach game-server Pods on Local Zone nodes, first through an NLB in Oregon and then through an ALB in the Local Zone. A hospital data centre holds an Outpost rack with two nodes running records Pods, linked to the Region by a service link; later a local control plane runs on the Outpost itself. You aws · kubectl Players Los Angeles wss://play.riftwave .games AWS REGION · us-west-2 (Oregon) EKS CONTROL PLANES arena · API server care · API server VPC 10.0.0.0/16 · cluster arena us-west-2a · 10.0.1.0/24 EKS ENIs 10.0.1.250 node-a · m5.xlarge game-server-c NLB · play-nlb subnet 10.0.1.0/24 AZ subnets only LOCAL ZONE us-west-2-lax-1a · LA ALB · play-alb subnet 10.0.64.0/24 lax-1 · c5.2xlarge lax-2 · c5.2xlarge game-server-a game-server-c game-server-b HOSPITAL DATA CENTRE Service link → us-west-2 OUTPOST RACK · 10.20.8.0/24 Local control plane ward-1 · m5.2xlarge ward-2 · m5.2xlarge records-a records-b records-c

    2Quiz to check understanding

    Check yourself