Route 53 vs Cloudfront vs Global Accelerator

Photo by JJ Ying on Unsplash

Introduction

Route 53

The confusion comes from the similarity of the geographic records with cloudfront’s geographic restriction.

And the latency records with the aws global accelerator.

Geographic based record

Cloudfront

Geo restriction can be set on Cloudfront by set up a whitelist/blacklist to restrict the geo that can access the content.

In terms of security, it is backed by AWS shield and AWS global network, also users can set up CloudFront signed URL / Cookies (for a batch of files) to allow access no matter the origin. It makes use of an account-wide key pair that manages by the root account.

Also, field-level encryption is available using asymmetric keys.

For availability, we can set up origin groups across regions (1 primary origin, 1 secondary origin) to do failover.

For direction, it can be configured to redirect to different origins based on the path patterns (/images/*).

Global accelerator

It is fast because it makes use of anycast IP (other than unicast IP) which means all the routers hold the same IP addresses and the user’s requests will be directed to the nearest one.

Two static anycast IPs will be created for our application and it will direct the traffic to the edge locations and the edge locations will direct the traffic through the AWS internal network.

The global accelerator works with HTTP protocol and lower level protocol such as HTTP / UDP, it is a good fit to enhance performance for gaming, etc.

Moreover, it also offers health checks, weight configuration for endpoint groups, and failover.

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store