What changed

AWS documented Web Bot Authentication in WAF Bot Control: HTTP message signatures and published keys produce verified, invalid, expired or unknown-bot labels for policy decisions. Version 6 extends support across AWS WAF resource types in commercial Regions.

Why it matters

Agent identity can be based on cryptographic request evidence instead of spoofable user agents or shared IP allowlists, but verified identity is not the same as authorization for every path or action.

What to do

Pin a supported static Bot Control version, sign synthetic agent requests, and test verified, expired, invalid and unknown keys against explicit allow, rate-limit and deny rules. Alert on label changes and keep application authorization separate.

Caveat

AWS says Bot Control allows verified traffic by default and bases the feature on standards plus active drafts. External-agent registration APIs were still on the roadmap, and AWS performance and latency claims need workload testing.