AWS network-firewall documentation change
Summary
Removed 'AWS' prefix from 'Direct Connect' for terminology consistency
Security assessment
This is a branding/naming convention change with no security implications. The modification does not alter technical functionality or security posture.
Diff
diff --git a/network-firewall/latest/developerguide/vpc-interface-endpoints.md b/network-firewall/latest/developerguide/vpc-interface-endpoints.md index 7e5207901..fc18ae118 100644 --- a//network-firewall/latest/developerguide/vpc-interface-endpoints.md +++ b//network-firewall/latest/developerguide/vpc-interface-endpoints.md @@ -9 +9 @@ ConsiderationsCreate an interface endpointCreate a VPC endpoint policyExample VP -You can create a private connection between your VPC and AWS Network Firewall. You can access AWS Network Firewall as if it were in your VPC, without the use of an internet gateway, NAT device, VPN connection, or AWS Direct Connect connection. Instances in your VPC don't need public IP addresses to access AWS Network Firewall. +You can create a private connection between your VPC and AWS Network Firewall. You can access AWS Network Firewall as if it were in your VPC, without the use of an internet gateway, NAT device, VPN connection, or Direct Connect connection. Instances in your VPC don't need public IP addresses to access AWS Network Firewall.