Which solution will meet these requirements?
Use a Network Load Balancer with a certificate attached from AWS Certificate Manager (ACM). Use query parameter-based routing.
Use a Gateway Load Balancer. Import a generated certificate in AWS Identity and Access Management (IAM). Attach the certificate to the load balancer. Use HTTP path-based routing.
Use an Application Load Balancer with a certificate attached from AWS Certificate Manager (ACM). Use query parameter-based routing.
Use a Network Load Balancer. Import a generated certificate in AWS Identity and Access Management (IAM). Attach the certificate to the load balancer. Use query parameter-based routing.
Explanations:
A Network Load Balancer operates at the transport layer and does not support query string-based routing. It is suitable for TCP/UDP traffic but does not offer the necessary features for HTTP/S routing based on query strings.
A Gateway Load Balancer is designed for deploying, scaling, and managing virtual appliances, and is not suitable for direct HTTP/S request routing. It does not support query string-based routing and is not intended for handling HTTPS traffic directly with certificates.
An Application Load Balancer (ALB) operates at the application layer and supports advanced routing capabilities, including query parameter-based routing. It can use a certificate from AWS Certificate Manager (ACM) to handle SSL/TLS encryption, making it ideal for this scenario.
A Network Load Balancer does not support query string-based routing and operates at the transport layer, which limits its ability to handle HTTP/S traffic in the manner required. Additionally, the method of importing certificates via IAM is not appropriate for handling SSL termination at a load balancer level.
From what I’ve seen, the answer is:
Use an Application Load Balancer with a certificate attached from AWS Certificate Manager (ACM). Use query parameter-based routing.