Closed dhardy92 closed 1 year ago
Thanks for sharing your feedback @dhardy92 .
This was included to the solution roadmap and we'll post an update to this thread once we have more information.
Closing the ticket due to low customer demand. The out-of-box solution provides a starting point for implementing AWS WAF rules. We recommend you to add custom rule or customize source code to meet your company’s needs.
Some search engine are legitimate to scan ours (Bing Google Qwant ...) and they might be blocked by probe and scan log parser if there is too much Error code (4xx) per minute.
It could be usefull for SEO to prevent those bot from being block by doing some reverse resolution of IP and white list corresponding IP ranges ?
Ex: 157.55.39.224 is making too much 404
In config I whitelisted "search.msn.com."
I would like to automatically add 157.56.0.0/14, 157.60.0.0/16, 157.54.0.0/15 in whitelist IP range.
Some references : https://www.bing.com/webmaster/help/verifying-that-bingbot-is-bingbot-3905dc26 https://support.google.com/webmasters/answer/80553?hl=en