AWS Advanced Networking Cram Sheet: Edge Services & Global Traffic Optimization

This cram sheet focuses on Domain 1.1: Designing solutions with edge network services to optimize global performance. It covers the critical distinctions between Amazon CloudFront, AWS Global Accelerator, and Route 53 for traffic management.

Topic Weighting

[!IMPORTANT] Domain 1 as a whole represents 30% of the ANS-C01 exam. Task 1.1 is the foundational objective for global architecture.

Key Concepts Summary

• Amazon CloudFront: A Content Delivery Network (CDN) that caches content at edge locations. Operates primarily at Layer 7 (HTTP/S). Best for static content, video streaming, and dynamic API acceleration.
• AWS Global Accelerator: Uses the AWS global network to route traffic to the nearest healthy endpoint via Anycast IP addresses. Operates at Layer 4 (TCP/UDP). Ideal for non-HTTP use cases or when you need static IP addresses for your application.
• Amazon Route 53: A highly available DNS service. It manages traffic via DNS records and health checks. It does not "proxy" traffic like CloudFront/GA but directs clients where to go.
• Amazon DAX & ElastiCache: Application-level caching. DAX is specific to DynamoDB; ElastiCache is for general-purpose in-memory data (Redis/Memcached).

Common Pitfalls

• CloudFront vs. GA: Don't use CloudFront for non-HTTP protocols (e.g., VoIP, MQTT). Use Global Accelerator instead.
• Caching Headers: Forgetting to configure Cache-Control or Expires headers at the origin, leading to poor cache hit ratios in CloudFront.
• Static IPs: CloudFront does NOT provide static IP addresses for the edge locations; Global Accelerator DOES provide two static Anycast IPs.
• TTL Confusion: Setting DNS TTLs too high in Route 53 while expecting fast failover (use Alias records or Route 53 Health Checks with low TTLs).

Mnemonics / Memory Triggers

• CF = Caching Fast: CloudFront is about Caching at the edge for Fast delivery of content.
• GA = Global Anycast: Global Accelerator provides two Anycast IPs for the Global AWS backbone.
• L7 vs L4: CloudFront is Content (Layer 7); Global Accelerator is Generic (Layer 4).

Formula / Equation Sheet

Edge Service Comparison

Practice Set

1. Scenario: A company has a legacy UDP-based gaming application and needs to reduce latency for users in Europe accessing a US-based server. Which service is best?
   • Answer: AWS Global Accelerator (supports UDP and optimizes the network path).
2. Scenario: You need to prevent "Cache Stampede" for a high-traffic S3 website. What should you configure?
   • Answer: CloudFront with Origin Shield.
3. Scenario: An application requires a single set of static IP addresses for firewall allow-listing at client sites. Which service provides this?
   • Answer: AWS Global Accelerator.
4. Scenario: You want to route users to the region with the lowest network latency based on DNS. Which Route 53 policy is used?
   • Answer: Latency-based Routing.
5. Scenario: Your DynamoDB-backed API is seeing high read latency. What is the most efficient edge-like optimization?
   • Answer: DynamoDB Accelerator (DAX).

Fact Recall Blanks

• CloudFront caches content at AWS  locations. (Edge)
• Global Accelerator provides  static Anycast IP addresses. (Two)
• The service that specifically optimizes DynamoDB performance is called . (DAX)
• Route 53  records are used to map a naked domain (example.com) to a CloudFront distribution. (Alias)

Worked Examples

Optimizing a Global API

Problem: A REST API hosted on an Application Load Balancer (ALB) in us-east-1 is experiencing 500ms latency for users in Singapore.

Solution Steps:

1. Analyze Protocol: It's HTTPS (Layer 7), so CloudFront is a candidate.
2. Evaluate Caching: API responses are dynamic but can be cached for 60 seconds. CloudFront is the best choice here.
3. Implementation:
   • Create a CloudFront distribution.
   • Set the Origin to the ALB DNS name.
   • Enable Origin Protocol Policy: HTTPS Only.
   • Use Caching Optimized policy to ensure the edge locations hold the API data.
4. Result: Users in Singapore hit a local Edge Location. The "First Mile" (Singapore to US-East-1) is handled over the AWS high-speed backbone rather than the public internet.

Visualization of Global Path Optimization