AWS waf documentation change

Service: waf · 2025-11-22 · Documentation low

File: waf/latest/developerguide/ddos-resiliency-example-tcp-udp.md

Summary

Updated diagram alt text (changed 'Elastic Load Balancing' to 'ELB' and fixed typo)

Security assessment

Cosmetic changes to diagram description without security impact

Diff

diff --git a/waf/latest/developerguide/ddos-resiliency-example-tcp-udp.md b/waf/latest/developerguide/ddos-resiliency-example-tcp-udp.md
index c246a75dc..2b5f837e1 100644
--- a//waf/latest/developerguide/ddos-resiliency-example-tcp-udp.md
+++ b//waf/latest/developerguide/ddos-resiliency-example-tcp-udp.md
@@ -28 +28 @@ The following reference diagram depicts an example DDoS resilient architecture f
-![The diagram shows users connected to Route 53 and to an AWS Global Accelerator. The accelerator is connected to an Elastic Load Balancing icon that's protected by AWS Shield Advanced and AWS WAF. The Elastic Load Balancing is itself connected to an Amazon EC2 instance. This Elastic Load Balancing instance and the Amazon EC2 instance are in Region 1. The AWS Global Accelerator is also directly connected to another Amazon EC2 instance, which isn't behind a protected Elastic Load Balancing intsance. This second Amazon EC2 instance is in Region n.](/images/waf/latest/developerguide/images/shield-resilient-tcp-udp-app-arch.png)
+![The diagram shows users connected to Route 53 and to an AWS Global Accelerator. The accelerator is connected to an ELB icon that's protected by AWS Shield Advanced and AWS WAF. The ELB is itself connected to an Amazon EC2 instance. This ELB instance and the Amazon EC2 instance are in Region 1. The AWS Global Accelerator is also directly connected to another Amazon EC2 instance, which isn't behind a protected ELB intsance. This second Amazon EC2 instance is in Region n.](/images/waf/latest/developerguide/images/shield-resilient-tcp-udp-app-arch.png)