✅ 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: Implement Origin Cloaking
Lab 7: AWS Global Accelerator Performance
Bonus Lab: CloudWatch metrics and enabling flow logs
By default AWS Global Accelerator distributes traffic equally between the endpoints in the endpoint groups for the listener. If you have stateful applications, you can choose to have Global Accelerator direct all requests from a user at a specific source (client) IP address to the same endpoint resource, to maintain client affinity. You do this by changing the Client Affinity from None (default) to Source IP for the listener.
Learn more: Client Affinity
Global Accelerator uses a consistent-flow hashing algorithm to choose the optimal endpoint for a user's connection. For more information, see our documentation
Let's see how AWS Global Accelerator will handle requests from Sao Paulo and Ohio.
US-WEST-2 has two endpoints, requests from Sao Paulo and Ohio have been processed by only 1 endpoint in the endpoint group because of the client affinity.
Now that we have implemented fine-grained traffic control and Client Affinity, let's see how Global Accelerator handles failover. When you're ready proceed to Lab 5
We encourage participation; if you find anything, please submit an issue. However, if you want to help raise the bar, submit a PR!