Best practices for deployment with AWS Global Accelerator

This article provides best practices for deploying applications with AWS Global Accelerator to avoid connection collisions and improve performance and availability.

Specifically, the article covers:

• An overview of AWS Global Accelerator and its client IP address preservation feature
• Scenarios that can lead to connection collisions, such as using the same load balancer as an endpoint for multiple accelerators, allowing both direct internet traffic and accelerator traffic to the same load balancer, and using cross-zone load balancing with client IP preservation
• Solutions to avoid connection collisions, including configuring port overrides for accelerator listeners, disabling cross-zone load balancing, and replicating infrastructure with separate paths for direct and accelerated traffic
• A recommendation to replicate infrastructure with separate paths as a best practice to avoid connection collisions while enabling A/B testing and redundancy