Choosing a ROUTE 53 Routing Policy | Simple | Latency based | Geo | Weighted
Channel: Pythoholic
Date: 25/03/2020

Simple routing lets you configure standard DNS records
With simple routing, you typically route traffic to a single resource, so you have your application and you set a record and route traffic to that URL based on the record type.

⭐ Kite is a free AI-powered coding assistant that will help you code faster and smarter. The Kite plugin integrates with all the top editors and IDEs to give you smart completions and documentation while you’re typing. I've been using Kite for 6 months and I love it! 
https://www.kite.com/get-kite/?utm_medium=referral&utm_source=youtube&utm_campaign=pythoholic&utm_content=description-only

Weighted routing lets you associate multiple resources with – 
The single domain name (pythoholic.com) 
Subdomain name (apps.pythoholic.com) with power to chose how much traffic can be distributed
To use latency-based routing, you create latency records for your resources in multiple AWS Regions. 

Failover routing lets you route traffic to a resource when the resource is healthy or to a different resource when the first resource is unhealthy. The primary and secondary records can route traffic to anything from an Amazon S3 bucket that is configured as a website to a complex tree of records.
 
Geolocation routing lets you choose the resources that serve your traffic based on the geographic location of your users, meaning the location that DNS queries originate from. 

Multivalue answer routing lets you configure Amazon Route 53 to return multiple values, such as IP addresses for your web servers, in response to DNS queries. 

#Route53 #SAAC02 #AWSROUTE53