lab-2-traffic-distribution

Multi-Region traffic management with AWS Global Accelerator - Intelligent traffic distribution

Workshop Progress

✅ Lab 0: Workshop Initialization

✅ Lab 1: Create your first AWS Global Accelerator

Lab 2: Implement Intelligent Traffic Distribution

Lab 3: Implement Fine-grained traffic control

Lab 4: Implement Client Affinity

Lab 5: Continuous availability monitoring and Failover

Lab 6: Origin Cloaking

Lab 7: AWS Global Accelerator Performance

Bonus Lab: CloudWatch metrics and enabling flow logs

Clean up

Lab 2 - Intelligent Traffic Distribution

In this lab we will help you understand how AWS Global Accelerator routes requests based on the origin of the requester.

Traffic dials dictate the percentage of traffic an endpoint group can receive. Learn more...

For each endpoint group, you can set a traffic dial to control the percentage of traffic that is directed to the group. The percentage is applied only to traffic that is already directed to the endpoint group, not to all listener traffic.

By default, the traffic dial is set to 100 (that is, 100%) for all regional endpoint groups in an accelerator. The traffic dial lets you easily do performance testing or blue/green deployment testing for new releases across different AWS Regions, for example.

For more information, see our documentation

Let's see how AWS Global Accelerator routes the requests based on the origin of the requester - we spinned up 4 clients in different regions (Ohio, Singapore, Paris and Sao Paulo). Again, we are not testing performance, just how AWS Global Accelerator routes requests based on user locations.

We use the following command to send 100 requests to the accelerator DNS per client:

$ for i in {1..100}; do curl http://123abc456def.awsglobalaccelerator.com/ --silent >> output.txt; done; cat output.txt | sort | uniq -c ; rm output.txt;

Comments

1. Requests from Paris are processed in EU-WEST-1 (Dublin).
2. Requests from Ohio and Sao-Paolo are processed in US-WEST-2 (Oregon), we have two endpoints in Oregon region, AWS Global Accelerator sends 50% of traffic to each endpoint (Endpoint weights).
3. Requests from Singapore are processed in AP-NORTHEAST-1 (Tokyo).

Checkpoint

Now that we have seen how AWS Global Accelerator inteligently distributes traffic from users to endpoint groups, let's see how to send more or less traffic to an endpoint group or to a specific endpoint in an endpoint group. When you're ready proceed to Lab 3!

Participation

We encourage participation; if you find anything, please submit an issue. However, if you want to help raise the bar, submit a PR!