As companies look to improve performance and availability for their users by expanding their architecture's global footprint, it can become complex to manage routing and traffic to multiple network resources, such as web servers, app servers, and load balancers across multiple locations. Amazon Route 53 Traffic Flow provides a policy-based management interface you can use to easily control your application's global traffic based on latency, health, and other considerations. In this session, we show you how to use Traffic Flow to solve routing and traffic management use cases while taking advantage of code control and versioning for easier management of your traffic management configuration.

2. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Advanced Traffic Management
with Route 53 Traffic Flow
Sean Meckley
Principal Product Manager
Amazon Route 53
N E T 4 0 7

3. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Agenda
Goal: a good discussion
Questions/Discussions/Debates are welcome
Prepared topics:
What is Amazon Route 53 traffic flow?
Real-world use cases for traffic flow: from simple to complex
Geoproximity routing

4. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
What is Route 53 traffic flow?
Global traffic management in the cloud
Built on top of Route 53
Policy-based traffic management and routing
Automatic versioning of policies and easy rollback
Additional routing rules/capabilities
Geoproximity routing with load biasing

5. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Policy management in the Route 53 console

6. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Use case: Simple backup website
Add redundancy to your website
Backup “fail whale page”
Or a backup copy of your dynamic application

7. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Use case: Simple backup website
Endpoint (+Health Check):
IP 1.2.3.4
Rule: Failover
Primary
Secondary
Endpoint:
S3 Website
Rules
+ add rule
Endpoints
+ add endpoint
Start

8. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Use case: Simple backup website

9. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Use case: Simple backup website
{
"AWSPolicyFormatVersion":"2015-10-01",
"RecordType":"A",
"StartRule":"failover-rule-1",
"Endpoints": {
"endpoint-failover-1": {
"Type":"value","Value":"1.2.3.4"
},
"endpoint-failover-2": {
"Type":"s3-website","Value":"example.com.s3-website-us-east-1.amazonaws.com","Region":"us-east-1"
}
},
"Rules": {
"failover-rule-1": {
"RuleType":"failover",
"Primary": {
"EndpointReference":"endpoint-failover-1",
"EvaluateTargetHealth":false,
"HealthCheck":"70448823-e87b-47fd-aee8-c183944d7bf4"
},
"Secondary": {
"EvaluateTargetHealth":true,
"EndpointReference":"endpoint-failover-2"
}
}
}
}

10. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Use case: Simple backup website
$ aws route53 create-traffic-policy --name "Simple Backup Website" --document file://~/myPolicy.json
Create traffic policy:
Apply traffic policy:
$ aws route53 create-traffic-policy-instance --hosted-zone-id Z3509RV2ZY3SLP --name example.com --ttl 60 --traffic-policy-id
4cc427e2-d0bf-4cbd-a216-133b845127f1 --traffic-policy-version 1

11. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Questions?
How do Route 53 health checks interact with traffic flow policies?
How does traffic flow work with alias records?
How do I do failover between Elastic Load Balancing/Application Load
Balancing/Network Load Balancing endpoints?

12. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Use case: Weighted round robin
Distribute traffic among multiple app stacks or servers
Take health of each endpoint into account
Examples:
Blue/green deployment of stacks behind ELB: gradually increase weight of new stack and
reduce weight of old stack
DNS load balancing directly across servers
Containers—Amazon Elastic Container Service (Amazon ECS), Amazon Elastic Container
Service for Kubernetes (Amazon EKS)
Specialized applications where HTTP load balancing (such as ELB) isn’t possible

13. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Use case: Weighted round robin
Endpoint:
IP: 1.2.3.4
Rule: Weighted Round Robin
33%
33%
34%
Endpoint:
IP: 2.3.4.5
Endpoint:
IP: 3.4.5.6
Health Check
Health Check ID: abc123
Health Check
Health Check ID: def345
Health Check
Health Check ID: ghi789
Rules
+ add rule
Endpoints
+ add endpoint
Start
Typical container use case: simple WRR with health checks

14. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Blue/Green deployment
Traffic policy version Comment
1 Stack A: 1% / Stack B: 99%
2 Stack A: 2% / Stack B: 98%
3 Stack A: 5% / Stack B: 95%
… …
15
Stack A: 100% / Stack B: 0%

15. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
$ aws route53 create-traffic-policy --name “Blue Green Deployment" --document file://~/blueGreen.json
{ ... "Id": "3cac5d4b-5dcf-4865-a486-c0611e486991" ... }
Blue/Green deployment: Policy versioning
Create traffic policy:
Apply traffic policy:
$ aws route53 create-traffic-policy-instance --hosted-zone-id Z3509RV2ZY3SLP --name bluegreen.example.com --ttl 60
--traffic-policy-id 3cac5d4b-5dcf-4865-a486-c0611e486991 --traffic-policy-version 1
{ ... "Id": "8aab72aa-b2e6-4ed1-a9d8-353164098cdf" ... }
$ aws route53 create-traffic-policy-version --id 3cac5d4b-5dcf-4865-a486-c0611e486991 --document file://~/blueGreen.json
Create another traffic policy version with different weights:
Roll forward traffic policy:
$ aws route53 update-traffic-policy-instance --id "8aab72aa-b2e6-4ed1-a9d8-353164098cdf" --ttl 60
--traffic-policy-id "3cac5d4b-5dcf-4865-a486-c0611e486991" --traffic-policy-version 2

16. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
$ aws route53 update-traffic-policy-instance --id "8aab72aa-b2e6-4ed1-a9d8-353164098cdf" --ttl 60
--traffic-policy-id "3cac5d4b-5dcf-4865-a486-c0611e486991" --traffic-policy-version 1
Deployment automation and rollback
Rollback (can do this at any time):
Fully automated blue/green deployment:
POLICY_INSTANCE='--id "8aab72aa-b2e6-4ed1-a9d8-353164098cdf" --ttl 60 --traffic-policy-id "3cac5d4b-5dcf-4865-a486-c0611e486991"'
for i in $(seq 2 1 10)
do
# move to next policy version
aws route53 update-traffic-policy-instance $POLICY_INSTANCE --traffic-policy-version $i
# check health every 10 seconds for next 10 minutes before we move on.
for t in $(seq 0 10 600)
sleep 10
# Rollback and abort if we become unhealthy
if ! ~/bin/check-all-is-healthy; then
aws route53 update-traffic-policy-instance $POLICY_INSTANCE --traffic-policy-version 1
exit
fi
done
done | tee deployment-logfile.txt

17. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Use case: Multi-region application
Application endpoints distributed around the world
Redundancy plus improved performance for end users globally
Can be a mix of AWS Regions and own data centers or other endpoints
Can include one or more CDNs in front of your application

18. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Use case: Multi-region application
Endpoint:
ELB 1234 (Evaluate ELB Health)
Rule: Geo
Geo 1: [List of Eastern US states]
…
…
...
Geo 2: [List of Western US states]
…
…
...
Endpoint:
ELB 4567 (Evaluate ELB Health)
Rule: Failover
Primary
Secondary
Rule: Failover
Primary
Secondary
Rules
+ add rule
Endpoints
+ add endpoint
Start

19. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Questions?
Can I combine routing techniques like latency and geo in the same policy?
How can I manage load on each of my endpoints?
How can I reuse the same policy for multiple DNS names?

20. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Geoproximity routing
Tag record sets with geo coordinates
Resolvers/user networks matched to closest record set
eDNS client subnet enabled
Load balancing: change endpoint weight using bias

21. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
“us-west-1”
loc=45,-122
“us-east-1”
loc=37,-78
Geoproximity routing: Load management

22. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
“us-west-1”
loc=45,-122
“us-east-1”
loc=37,-78
a
b
Geoproximity routing: Load management

23. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Geoproximity routing: Load management
Bias expands or shrinks the size of the geographic region routed to a
given resource
Positive bias:
Biased distance = actual distance * [1 - (bias/100)]
Negative bias:
Biased distance = actual distance / [1 + (bias/100)]
Allowed bias values: {-99, +99}; default value is 0

24. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
“us-west-1”
loc=45,-122
bias=0 “us-east-1”
loc=37,-78
bias=0
a
b
Geoproximity routing: Load management
Biased distance (us_west_1) < biased distance (us_east_1),
so send user to West

25. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
“us-west-1”
loc=45,-122
bias=0 “us-east-1”
loc=37,-78
bias=50
a
b
Biased distance (us_west_1) > biased distance (us_east_1),
so send user to East
Geoproximity routing: Load management

26. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.

27. Thank you!
© 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Sean Meckley
meckleys@amazon.com

28. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.