Skip to content

Instantly share code, notes, and snippets.

@tarunsinghaldotme

tarunsinghaldotme/infrastructure-components.csv

Created April 4, 2025 02:54
Show Gist options
  • Save tarunsinghaldotme/116507e40b2d7c0a1e7c9b95168351a8 to your computer and use it in GitHub Desktop.
Save tarunsinghaldotme/116507e40b2d7c0a1e7c9b95168351a8 to your computer and use it in GitHub Desktop.
Download ZIP
Choosing the Right AWS Infrastructure Components
Raw
infrastructure-components.csv
Feature Regions Availability Zones Edge Locations Local Zones Wavelength Zones Outposts
Primary Purpose Geographic isolation High availability within a region Content delivery and DNS Low latency for metropolitan areas Ultra-low latency for 5G applications AWS in your data center
Typical Latency Varies by distance <2ms between AZs <50ms to end users <10ms to metropolitan area <10ms for 5G users Local network speed
Services Available All AWS services Most AWS services CloudFront/Route 53 Subset focused on compute/storage/databases Limited subset (EC2/EBS/VPC) Subset of AWS services
Data Residency Control Regional Regional Global caching network Metro area with connection to parent region Telecom provider facilities Your data center
Best For Compliance/global presence Mission-critical production workloads Content-heavy websites/global audiences Interactive applications in specific metros Mobile edge computing/AR/VR Strict data sovereignty/hybrid deployments
Cost Consideration Standard AWS pricing Inter-AZ data transfer costs Pay for data transfer Premium pricing over standard regions Premium pricing for edge compute Highest cost with hardware commitment
Management Overhead AWS managed AWS managed Fully AWS managed AWS managed AWS managed with carrier coordination AWS managed hardware in your facility
Deployment Complexity Standard Standard Low (managed service) Medium High Highest
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment