AWS Route 53 - Managed DNS Service

1. Architecting Traffic
Management with
Amazon Route 53

2. Question
• Have you ever heard this questions?
What version of Gmail are you on?
• Why?

3. What is Amazon Route
53
• Managed DNS service with advanced functions
• Main functions are:
• Register domain names
• Route internet traffic to the resource for you domain
• Check the health of your resources
• Whether you’re running a simple website, a mobile app, or a suite of business
applications, DNS is a fundamental part of any architecture in the cloud.
• How did Route 53 get it’s name?

4. What is DNS

5. Basic DNS Setup

6. Route 53 Features
• Worldwide anycast network with redundant locations
• 100% availability SLA - over provisioned network and server infrastructure
• Advanced routing policies
• AWS integration - alias
• Manageable with API, CLI, SDKs, third-party tools
• Fault tolerance and zone isolation
• DDoS protection - always-on, fast mitigation without external routing

7. Route 53 Alias
• Alias resource record sets proved an Amazon Route 53 specific extension to
DNS functionality
• Pointer to a CloudFront distribution, and Elastic Beanstalk environment, an
ELB (Classic/Application/Network), and S3 bucket hosting a static website, or
another Route 53 resource record set in the same hosted zone.
• Can point zone apex to an alias
• Can’t set TTL on an alias

8. Types of Health Checks
• Health checks can monitor:
• an endpoint
• CloudWatch alarms
• other health checks

9. Choosing a Routing Policy I
• Simple - use for a single resource ( a web server or an S3 bucket); enter
multiple IPs for round robin
• Failover - use for active-passive setup; requires a health check on primary
resource
• Wighted - use to route traffic to multiple resources in proportions that you
specify

10. Example A
Start here when not using policy
editor

11. Example B

12. Resource Map

13. Demo I: Simple,
Wighted, and Failover

14. Choosing a Routing Policy II
• Latency - use when you have resources in multiple locations and you want to
route traffic to the resource that provides the best latency
• Geolocation - use when you want to route traffic based on the location or your
users
• Geoproximity - use when you want to route traffic based on the location of
your resources and, optionally, shift traffic from one resources in one location
to resources in another.
• Multivalue answer - use when you want Amazon Route 53 to respond to DNS
queries with up to eight healthy records selected at random

15. Geolocation

16. Amazon Route 53 Traffic
Flow
Amazon Route 53 Traffic Flow connects your users to the best endpoint based
on latency, geography, and endpoint health
• Traffic policy is a version document consisting of rules and endpoints
• Versioning provides atomic roll back/roll forward
• Traffic policy is applied to an actual domain name, so all rules and endpoints
apply to that domain name; it can be reused for other domain names

17. Demo II: Complex
Traffic Policies

18. Demo II

19. Resource Map

20. Private DNS
• Route 53 feature that creates authoritative DNS within your VPC (one or more
VPCs in one or more accounts (CLI/API only) without exposing the DNS
records to the Internet

21. Summary
• Route53 - easy to use and cost effective managed DNS service
• Service Oriented Architecture
• 7 routing policies
• Health checks
• Traffic flow policies

22. References
• http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/Welcome.html
• https://www.youtube.com/watch?v=AAq-DDbFiIE&t=1078s
• https://www.youtube.com/watch?v=QU7FQBgL0Po&t=1518s
• https://aws.amazon.com/route53/pricing/