A company has a website behind an Application Load Balancer (ALB) that handles HTTP and HTTPS separately. The company wants all requests redirected so they use HTTPS. What should a solutions architect do?

The correct solution is to create a listener rule on the ALB to redirect HTTP traffic to HTTPS. ALBs have built-in capabilities to handle redirects. You can configure an HTTP listener (port 80) to automatically redirect all incoming requests to an HTTPS listener (port 443) using a 301 (permanent) or 302 (temporary) redirect. This ensures all traffic uses the secure protocol without requiring changes to the application. Updating the ALB's network ACL to accept only HTTPS traffic would block all HTTP traffic, but it wouldn't redirect users. They would simply receive an error. Creating a rule that replaces HTTP in the URL with HTTPS is not a standard ALB feature; URL rewriting is typically handled at the web server or application layer, not directly by the ALB for redirection purposes. Replacing the ALB with a Network Load Balancer (NLB) is incorrect because NLBs operate at Layer 4 and do not natively support HTTP/HTTPS redirection based on URL or host headers, which is a Layer 7 function. SNI is used for multiple SSL certificates on a single IP, not for redirecting HTTP to HTTPS.