Link copied to clipboard!
Group 10: Networking & Content Delivery
Global infrastructure and connectivity services: VPC, CloudFront, Route 53, API Gateway, Direct Connect.
Networking Principle: Design for global reach, low latency, security isolation, and scalable API management based on traffic patterns and geographic distribution.
Services & Roles
VPC
Virtual private cloud with subnets, security groups, and network isolation.
- Network isolation
- Security groups
- Route tables
CloudFront
Global CDN with 400+ edge locations for content delivery and acceleration.
- 400+ edge locations
- Origin failover
- Lambda@Edge
Route 53
Scalable DNS web service with health checks and traffic routing policies.
- Global DNS
- Health checks
- Traffic policies
API Gateway
Managed API service with caching, throttling, and authorization.
- API versioning
- Request throttling
- Custom authorizers
Direct Connect
Dedicated network connection from on-premises to AWS.
- Dedicated bandwidth
- Consistent latency
- Hybrid connectivity
Key Differences
| Dimension | VPC | CloudFront | Route 53 | API Gateway | Direct Connect |
|---|---|---|---|---|---|
| Function | Network isolation | Content delivery | DNS resolution | API management | Hybrid connectivity |
| Scope | Regional | Global | Global | Regional | Dedicated link |
| Performance | Network control | Edge caching | DNS routing | API optimization | Predictable bandwidth |
| Use Case | Resource isolation | Web acceleration | Domain management | Microservices | Enterprise hybrid |
| Cost Model | NAT/VPN hours | Data transfer | Queries + zones | API calls | Port hours + transfer |
Selection Model
0–10 sliders weight networking requirements, performance needs, and global distribution patterns.
Score_VPC = 0.28*C_networkIsolation + 0.24*C_securityControls + 0.18*C_subnetDesign + 0.14*C_hybridNetworking + 0.10*C_multiTier + 0.06*C_complianceRequirements
Score_CloudFront = 0.30*C_globalDelivery + 0.26*C_contentCaching + 0.18*C_edgeComputing + 0.12*C_webAcceleration + 0.08*C_originFailover + 0.06*(10 - C_dynamicContent)
Score_Route53 = 0.32*C_dnsManagement + 0.24*C_trafficRouting + 0.18*C_healthChecks + 0.12*C_globalLoadBalancing + 0.08*C_failoverRouting + 0.06*C_domainRegistration
Score_APIGateway = 0.30*C_apiManagement + 0.26*C_microservicesAPI + 0.18*C_requestThrottling + 0.12*C_apiVersioning + 0.08*C_customAuthorization + 0.06*C_apiCaching
Score_DirectConnect = 0.32*C_hybridConnectivity + 0.28*C_dedicatedBandwidth + 0.18*C_consistentLatency + 0.12*C_enterpriseNetworking + 0.06*C_complianceRequirements + 0.04*(10 - C_internetTraffic)
VPC {{vm.scores.vpc|number:2}}
CloudFront {{vm.scores.cloudfront|number:2}}
Route 53 {{vm.scores.route53|number:2}}
API Gateway {{vm.scores.apigateway|number:2}}
Direct Connect {{vm.scores.directconnect|number:2}}
Primary Emphasis: {{vm.recommended.name}} ({{vm.recommended.score|number:2}})
Heuristics
- High C_networkIsolation + C_securityControls → VPC for secure architectures.
- Strong C_globalDelivery + C_contentCaching → CloudFront for web performance.
- High C_dnsManagement + C_trafficRouting → Route 53 for DNS strategies.
- C_apiManagement + C_microservicesAPI → API Gateway for service mesh.
- C_hybridConnectivity + C_dedicatedBandwidth → Direct Connect for enterprise.
Anti-Patterns
- Using default VPC for production (design custom network topology).
- Using CloudFront for highly dynamic content (limited caching benefit).
- Using Route 53 without health checks for critical applications.
- Using API Gateway for high-throughput scenarios (consider ALB).
Summary
Choose VPC for isolation, CloudFront for global delivery, Route 53 for DNS, API Gateway for APIs, Direct Connect for hybrid.