For one domain, send /api to API servers and /assets to static-content servers.
Terminate TLS, run HTTP health checks, and route to target groups based on listener rules.
Which load balancer is most appropriate?
Use an Application Load Balancer listener with path-based routing to select target groups.
Detailed explanation
ALB understands HTTP/HTTPS and provides path-based routing, TLS termination, target groups, and health checks.
ALB understands HTTP/HTTPS and provides path-based routing, TLS termination, target groups, and health checks.
Gateway Load Balancer inserts and scales network virtual appliances; it is not an HTTP path router.
Gateway Load Balancer inserts and scales network virtual appliances; it is not an HTTP path router.
DNS resolves names but does not inspect HTTP URL paths or select target groups.
DNS resolves names but does not inspect HTTP URL paths or select target groups.
NLB primarily provides Layer 4 TCP, UDP, and TLS load balancing and does not implement HTTP path routing.
NLB primarily provides Layer 4 TCP, UDP, and TLS load balancing and does not implement HTTP path routing.
Check official documentation
Compare the following points with the official documentation.
Application Load Balancerのリスナールールとパスベースルーティングの公式説明を確認する。
Official references
What to confirm
L7のHTTPルーティングとL4の接続負荷分散、DNS名前解決の責務を区別できる。
Key points
- Application Load Balancer
- Path-based routing
- TLS termination
Notes
- Environment:
- Confirm current behavior in the official SAA-C03 guide and AWS service documentation.
Foundation review
Layer 7 versus Layer 4
HTTP headers and paths are Layer 7 concerns; connection forwarding is a Layer 4 concern.
Difference from DNS
Route 53 resolves names but does not inspect HTTP request paths.