Is AWS API Gateway rate limiting sufficient to stop a brute force attack happening right now, or do we desperately need to deploy AWS WAF?
Download run
Fan-out diagram
The searches the AI actually ran for this prompt.
SEED QUERY
Is AWS API Gateway rate limiting sufficient to stop a brute force attack happening right now, or do we desperately need to deploy AWS WAF?
1 real search · 1 real-search pass
AWS API Gateway throttling limits best effort token bucket AWS documentation WAF rate-based rulesGoogle ↗
OBSERVED
Badge and edge weight = share of passes that produced the query. Hover a query for its intent and routing format.
Query classes
Google's semantic query class for every sub-query: what kind of answer each search is after, simulated vs real.
Classifying 1 queries…
Searches and sources
ChatGPT1 real searches · gpt-6
AWS API Gateway throttling limits best effort token bucket AWS documentation WAF rate-based rules Google ↗
- Throttle requests to your REST APIs for better throughput in API Gateway · docs.amazonaws.cn
- Throttle requests to your HTTP APIs for better throughput in API Gateway · docs.amazonaws.cn
- Apply rate-based rules in API Gateway with AWS WAF · repost.aws
- Troubleshoot AWS WAF rate-based rule not blocking · repost.aws
- Options for rate limiting in rate-based rules and targeted Bot Control rules - Amazon WAF, Amazon Firewall Manager, Amazon Shield Advanced, and Amazon Shield network security director · docs.amazonaws.cn
- Amazon API Gateway FAQs | API Management · aws.amazon.com