Which solution will meet these requirements?
Configure a Gateway Load Balancer to use the URL path to direct traffic to the legacy application and the new Lambda function.
Configure a Network Load Balancer to use the URL path to direct traffic to the legacy application and the new Lambda function.
Configure a Network Load Balancer to use a regular expression to match the URL path to direct traffic to the new Lambda function.
Configure an Application Load Balancer to use the URL path to direct traffic to the legacy application and the new Lambda function.
Explanations:
A Gateway Load Balancer operates at the network layer (Layer 3) and is used for routing traffic based on IP addresses. It does not support routing based on URL paths.
A Network Load Balancer operates at the transport layer (Layer 4) and is designed for routing based on IP addresses and ports. It does not support routing based on URL paths.
A Network Load Balancer cannot use regular expressions or inspect the URL path. It only supports routing based on IP addresses and ports.
An Application Load Balancer operates at the application layer (Layer 7) and supports routing based on URL paths. This makes it the correct solution for directing traffic to different backend services based on URL path.
If I had to guess, I’d say the answer is:
Configure an Application Load Balancer to use the URL path to direct traffic to the legacy application and the new Lambda function.
As far as I can tell, the answer is:
Configure an Application Load Balancer to use the URL path to direct traffic to the legacy application and the new Lambda function.