AWS Security ChangesHomeSearch

AWS waf: Bot Control now auto-detects Akamai CDN client IPs

Service: waf · 2026-10-09 · Documentation medium

File: waf/latest/developerguide/waf-bot-control-use-cases.md · Type: network

Summary

Updated the Bot Control use-cases guidance to state that the managed rule group automatically recognizes traffic from Akamai (in addition to Amazon CloudFront, Cloudflare, and Fastly) and uses the originating client IP from the CDN's standard client IP header, so no extra forwarded IP configuration is needed for those CDNs.

Security assessment

The change documents which CDNs Bot Control trusts for client-IP resolution, which directly affects the accuracy of IP-based evaluation, session-level rate limiting, and targeted bot detection. Incorrect client identity can let attackers evade rate limits or spoof source IPs, so this is security-adjacent hardening guidance, but it describes existing behavior rather than fixing a specific vulnerability.

Evidence

+If your application sits behind a third-party CDN, by default AWS WAF sees the CDN's IP address as the client. The Bot Control managed rule group recognizes traffic from Amazon CloudFront, Akamai, Cloudflare, and Fastly automatically and uses the originating client IP from the CDN's standard client IP header instead.

Diff

diff --git a/waf/latest/developerguide/waf-bot-control-use-cases.md b/waf/latest/developerguide/waf-bot-control-use-cases.md
index 3fbae82..0078753 100644
--- a//waf/latest/developerguide/waf-bot-control-use-cases.md
+++ b//waf/latest/developerguide/waf-bot-control-use-cases.md
@@ -156 +156 @@ Always deploy Bot Control in count mode first. In count mode, Bot Control labels
-If your application sits behind a third-party CDN, by default AWS WAF sees the CDN's IP address as the client. The Bot Control managed rule group recognizes traffic from Amazon CloudFront, Cloudflare, and Fastly automatically and uses the originating client IP from the CDN's standard client IP header instead. Both the common protection level and the targeted protection level use this detection, including session-level rate limiting and the targeted bot detection rules that depend on accurate client identity. You don't need additional forwarded IP configuration on the Bot Control rule group for these CDNs. For other rule statements in your protection pack (web ACL) that use IP addresses, such as your custom IP set match, geo match, ASN match, and rate-based rules, configure them with a forwarded IP configuration if you want them to evaluate the upstream client IP. For information about forwarded IP addresses, see [Using forwarded IP addresses in AWS WAF](./waf-rule-statement-forwarded-ip-address.html). If your application is behind a different reverse proxy or a CDN that Bot Control doesn't recognize automatically, configure your reverse proxy to forward the client IP in a header such as `X-Forwarded-For` and use a forwarded IP configuration on the rule statements that evaluate IP addresses.
+If your application sits behind a third-party CDN, by default AWS WAF sees the CDN's IP address as the client. The Bot Control managed rule group recognizes traffic from Amazon CloudFront, Akamai, Cloudflare, and Fastly automatically and uses the originating client IP from the CDN's standard client IP header instead. Both the common protection level and the targeted protection level use this detection, including session-level rate limiting and the targeted bot detection rules that depend on accurate client identity. You don't need additional forwarded IP configuration on the Bot Control rule group for these CDNs. For other rule statements in your protection pack (web ACL) that use IP addresses, such as your custom IP set match, geo match, ASN match, and rate-based rules, configure them with a forwarded IP configuration if you want them to evaluate the upstream client IP. For information about forwarded IP addresses, see [Using forwarded IP addresses in AWS WAF](./waf-rule-statement-forwarded-ip-address.html). If your application is behind a different reverse proxy or a CDN that Bot Control doesn't recognize automatically, configure your reverse proxy to forward the client IP in a header such as `X-Forwarded-For` and use a forwarded IP configuration on the rule statements that evaluate IP addresses.