7. DNS, Caching and Performance Optimization

Amazon Cloudfront

AWS Global Accelerator

Explore

Amazon Route 53

Routing Policies

Last edited 59 days ago by Kirtan Chavda

Routing policies determine how Route 53 responds to queries.

When you create a record, you choose a routing policy, which determines how Amazon Route 53 responds to queries:

Simple routing policy – Use for a single resource that performs a given function for your domain, for example, a web server that serves content for the example.com website. You can use simple routing to create records in a private hosted zone.

Failover routing policy – Use when you want to configure active-passive failover. You can use failover routing to create records in a private hosted zone.

Geolocation routing policy – Use when you want to route traffic based on the location of your users. You can use geolocation routing to create records in a private hosted zone.

Geoproximity routing policy – Use when you want to route traffic based on the location of your resources and, optionally, shift traffic from resources in one location to resources in another location. You can use geoproximity routing to create records in a private hosted zone.

Latency routing policy – Use when you have resources in multiple AWS Regions and you want to route traffic to the Region that provides the best latency. You can use latency routing to create records in a private hosted zone.

IP-based routing policy – Use when you want to route traffic based on the location of your users, and have the IP addresses that the traffic originates from.

Multivalue answer routing policy – Use when you want Route 53 to respond to DNS queries with up to eight healthy records selected at random. You can use multivalue answer routing to create records in a private hosted zone.

Weighted routing policy – Use to route traffic to multiple resources in proportions that you specify. You can use weighted routing to create records in a private hosted zone.

Key function of each Routing Policy

Key function of each Routing Policy

Policy

What it Does

Simple

Simple DNS response providing the IP address associated with a name

Failover

If primary is down (based on health checks), routes to secondary destination

Geolocation

Uses geographic location you’re in (e.g. Europe) to route you to the closest region

Geoproximity

Routes you to the closest region within a geographic area

Latency

Directs you based on the lowest latency route to resources

Multivalue answer

Returns several IP addresses and functions as a basic load balancer

Weighted

Uses the relative weights assigned to resources to determine which to route to

There are no rows in this table

⁠

Simple Routing Policy

An A record is associated with one or more IP addresses.

Uses round robin.

Does not support health checks.

⁠

Failover Routing Policy

Failover to a secondary IP address.

Associated with a health check.

Used for active-passive.

Routes only when the resource is healthy.

Can be used with ELB.

When used with Alias records set Evaluate Target Health to “Yes” and do not use health checks.

⁠

Geo-location Routing Policy

Caters to different users in different countries and different languages.

Contains users within a particular geography and offers them a customised version of the workload based on their specific needs.

Geolocation can be used for localising content and presenting some or all your website in the language of your users.

Can also protect distribution rights.

Can be used for spreading load evenly between regions.

If you have multiple records for overlapping regions, Route 53 will route to the smallest geographic region.

You can create a default record for IP addresses that do not map to a geographic location.

⁠

Geo-proximity routing policy:

Use for routing traffic based on the location of resources and, optionally, shift traffic from resources in one location to resources in another.

⁠

Latency Routing Policy

AWS maintains a database of latency from different parts of the world.

Focused on improving performance by routing to the region with the lowest latency.

You create latency records for your resources in multiple EC2 locations.

⁠

Multi-value Answer Routing Policy

Use for responding to DNS queries with up to eight healthy records selected at random.

⁠

Weighted Routing Policy

Like simple but you can specify a weight per IP address.

You create records that have the same name and type and assign each record a relative weight.

Numerical value that favours one IP over another.

To stop sending traffic to a resource you can change the weight of the record to 0.

⁠

Key function of each Routing Policy

Simple Routing Policy

Failover Routing Policy

Geo-location Routing Policy

Geo-proximity routing policy:

Latency Routing Policy

Multi-value Answer Routing Policy

Weighted Routing Policy

Want to print your doc?
This is not the way.

Try clicking the ⋯ next to your doc name or using a keyboard shortcut (

CtrlP

) instead.