A tourism bureau serves static park maps globally and also exposes…

Question

A tourism bureau serves static park maps globally and also exposes a latency-sensitive API that benefits from static anycast entry IPs. How should edge and global performance services be applied?

Accepted Answer

Use Amazon CloudFront to cache static park maps at the edge and AWS Global Accelerator for static-IP anycast entry to the regional API — Maps love CloudFront’s edge cache; APIs that want a stable anycast front door love Global Accelerator. Use each tool for the job it actually does.

Answer

Serve park maps only from a single Region origin with no CDN and ignore Global Accelerator for the API

Answer

Use Global Accelerator to cache static map files at the edge instead of CloudFront

Answer

Replace both needs with a single public EC2 Elastic IP advertised only in one metro

A tourism bureau serves static park maps globally and also exposes a latency-sensitive API that benefits from static anycast entry IPs. How should edge and global performance services be applied?

Short Explanation

Full Explanation