Security, Identity, and Compliance
AWS Network Firewall
Managed, stateful network firewall with intrusion detection and prevention for your VPCs. It filters traffic at the perimeter of the VPC, for example traffic that goes through an internet gateway, a NAT gateway, a VPN, or AWS Direct Connect.
Exam phrases that point here
«filter outbound traffic from the VPC based on domain name»
AWS Network Firewall can allow or block outbound connections based on the domain (for example, using the HTTPS SNI or the HTTP URL), something a security group or a network ACL cannot do because they filter only by IP address, port, and protocol.
When not: If what needs to be filtered is web requests that reach an application (SQL injection, cross-site scripting) on CloudFront, an Application Load Balancer, or API Gateway, the answer is AWS WAF. If it is enough to allow ports and IP addresses per instance, security groups are sufficient.
«inspect all VPC traffic with an intrusion prevention system (IPS)»
Network Firewall includes a stateful engine that can detect and block traffic based on known attack signatures, inline with the traffic of the entire VPC.
When not: If the scenario asks to detect threats by analyzing logs without sitting in the path of the traffic, it points to Amazon GuardDuty. GuardDuty alerts; Network Firewall filters.
«centralized inspection of traffic between VPCs and to the on-premises network»
With AWS Transit Gateway, traffic between VPCs or to Direct Connect and VPN can go through a single managed firewall instead of deploying one in every VPC.
When not: If you only need to connect the networks, without inspecting, Transit Gateway is enough. And if the VPCs are connected by VPC peering, be careful: Network Firewall does not support inspecting that type of connection.
«managed network firewall with stateful rules to protect the VPC»
It is a firewall managed by AWS that scales with traffic and applies stateful rules at the VPC level, without installing or maintaining appliances.
When not: If the problem is a volumetric DDoS attack, Network Firewall is not designed for that: think of AWS Shield Advanced. If the ask is to apply the same firewall policies across many accounts, AWS Firewall Manager comes in.
«block communication with known malicious domains and IP addresses»
Network Firewall offers rule groups managed by AWS, including some based on Amazon threat intelligence, which you turn on without writing the rules by hand.
When not: Network Firewall does not inspect the queries that EC2 instances make to the AWS-provided DNS (AmazonProvidedDNS); if the requirement is to filter those DNS queries, the solution lies elsewhere (for example, Route 53 Resolver DNS Firewall).