AWS network-firewall documentation change

Service: network-firewall · 2026-05-31 · Documentation low

File: network-firewall/latest/developerguide/proxy-architecture-overview.md

Summary

Updated image descriptions with detailed alt text for network architecture diagrams

Security assessment

Changes are purely descriptive improvements for accessibility (alt text) without modifying security content. No security implications in diagram description updates.

Diff

diff --git a/network-firewall/latest/developerguide/proxy-architecture-overview.md b/network-firewall/latest/developerguide/proxy-architecture-overview.md
index 761a87790..bbef850f9 100644
--- a//network-firewall/latest/developerguide/proxy-architecture-overview.md
+++ b//network-firewall/latest/developerguide/proxy-architecture-overview.md
@@ -38 +38 @@ When the Network Firewall Proxy and the Applications are in the same VPC. This a
-![](/images/network-firewall/latest/developerguide/images/dedicated-vpc-proxy.png)
+![VPC architecture with private subnet containing clients and proxy endpoint connecting through NFW proxy and NAT gateway to internet gateway in public subnet.](/images/network-firewall/latest/developerguide/images/dedicated-vpc-proxy.png)
@@ -48 +48 @@ This architecture implements a centralized AWS Network Firewall Proxy that serve
-![](/images/network-firewall/latest/developerguide/images/centralized-proxy.png)
+![Three VPCs with private subnets connect through proxy endpoints to a central VPC containing Network Firewall proxy, NAT gateway, and internet gateway.](/images/network-firewall/latest/developerguide/images/centralized-proxy.png)
@@ -54 +54 @@ For environments with non-overlapping CIDR ranges, you can leverage AWS Transit
-![](/images/network-firewall/latest/developerguide/images/tgw-proxy.png)
+![Three VPCs with clients connected via Transit Gateway to a central VPC with proxy and NAT gateway.](/images/network-firewall/latest/developerguide/images/tgw-proxy.png)