What’s the Best AWS Solution for Handling HTTP Redirects to Reduce Load on On-Prem Infrastructure?

The most AWS-native solution for your use case is to use the Application Load Balancer with IP Target Groups. This will let you push traffic back to your data center using options like Direct Connect or Site-to-Site VPN. Just keep in mind the costs involved with traffic volume and the specifics of the load balancer itself—there are some variable dimensions that can affect pricing.

If your requests are just HTTP, I recommend using the Application Load Balancer (ALB). For other ports, a Network Load Balancer (NLB) might be better. Alternatively, you could create an Nginx instance on EC2, which allows for more control without too much overhead.

For basic redirect cases, CloudFront with Lambda@Edge will work great, or you can opt for just CloudFront behaviors. They can easily handle a lot of requests without much hassle. If you need something explicit, an ALB with appropriate redirect rules could be effective and requires minimal operation effort. Just be mindful of the complexity of your redirect logic.

You might want to consider using CloudFront paired with Lambda@Edge. It’s cost-effective, performs well, and can handle basic redirects without needing a heavy setup. If you want something even simpler, just configuring CloudFront behaviors should suffice since it can scale automatically, removing the need to manage servers.