Route 53 101

Question 1

5 Routing Policy Types

Answer 1

Simple
Weighted
Latency
Failover
Geolocation

Question 2

Simple Routing Policy Overview

Answer 2

Default when creating new record set

Common for when you have single resource that performs one function

ie a single web server

Can do round robin

Question 3

Weighted Routing Policy Overview

Answer 3

Weight your traffic to different places
(2 ELB’s in same region, different regions, etc.

Use Case:
A/B testing 20% traffic to new site, 80% to production site

Does this over time, don’t see immediate effects

Question 4

Is Route 53 global?

Answer 4

Yes, like IAM

Question 5

Latency Routing Policy Overview

Answer 5

Routes traffic based on lowest latency for end user (to region that gives the fastest response)

Create a Latency Resource Record Set for the EC2 or ELB resource in each region that hosts your site.

When Route53 gets request for site, it selects the Latency Resource Record that gives user lowest latency

Question 6

Failover Routing Policy Overview

Answer 6

Used when you want an active/passive set up

ie you have a primary site in one region and a failover in another region

Route53 monitors health of primary site using a health check to monitor health of endpoints

Question 7

Failover Routing Policy Failover config example

Answer 7

Route 53 health check set to use DNS name of Elastic Load Balancer.

Healthcheck will fail if all instances behind ELB go down, or if the ELB itself goes down

Question 8

Geolocation Routing

Answer 8

Lets you choose where your traffic will be send based on geolocation of your users

Can use continents, countries, or states in USA

Question 9

Alias records vs CName records

Answer 9

Alias acts like CNAME but lets you resolve individual AWS resources like ELB or Cloudfront