2 Answers
- Newest
- Most votes
- Most comments
1
Hi,
NLB is a Lyer 3/4 component while WAF is a Layer 7 protection component.
That is why WAF is only available for Application Load Balancer in the ELB portfolio. NLB does not terminate the TLS session therefore WAF is not capable of acting on the content. I would consider using AWS Shield at Layer 3/4.
Jeff
answered a year ago
0
As stated above, WAF does not integrate with the NLB. Depending on your requirements, a Network Firewall may be appropriate.
Relevant content
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 4 months ago
While I agree with the rationale of NLB not be available for WAF giving the fact they act at different OSI layers, NLB does support TLS session termination, since back 2019: https://aws.amazon.com/blogs/aws/new-tls-termination-for-network-load-balancers/. Also I do make use of it. Please currect if I am wrong.