AWS network-firewall documentation change
Summary
Updated scalability guidance by removing reference to VPC endpoint associations
Security assessment
This change updates architectural guidance without security implications. The removed VPC endpoint association reference doesn't indicate a security fix, but rather a documentation refinement for scalability best practices.
Diff
diff --git a/network-firewall/latest/developerguide/vpc-config-subnets.md b/network-firewall/latest/developerguide/vpc-config-subnets.md index 91baa58c9..051861a15 100644 --- a//network-firewall/latest/developerguide/vpc-config-subnets.md +++ b//network-firewall/latest/developerguide/vpc-config-subnets.md @@ -19 +19 @@ To prepare a VPC for your Network Firewall firewall, in each Availability Zone w -Network Firewall supports up to 100 Gbps of network traffic per firewall endpoint. If you require more traffic bandwidth, you can define additional endpoints in VPC endpoint associations, or you can split your resources into subnets and create a Network Firewall firewall in each subnet. +Network Firewall supports up to 100 Gbps of network traffic per firewall endpoint. If you require more traffic bandwidth, you can split your resources into subnets and create a Network Firewall firewall in each subnet.