Blocking tens of thousands of IP's

Cox, Eric S eric.cox at kroger.com
Tue Nov 1 22:57:09 UTC 2016


Is it. However our frontend capacity spans across multiple data centers, a dozen+ nginx instances, and over 70 cores of processing power. We are not as concerned with overloading the frontend as we are with certain endpoints that might be single instance legacy apps etc.

-----Original Message-----
From: Rainer Duffner [rainer at ultra-secure.de]
Received: Tuesday, 01 Nov 2016, 6:54PM
To: nginx at nginx.org [nginx at nginx.org]
Subject: Re: Blocking tens of thousands of IP's


Am 01.11.2016 um 23:43 schrieb Cox, Eric S <eric.cox at kroger.com<mailto:eric.cox at kroger.com>>:

Unfortunately much like others have stated, we also don't have the automation at the firewall layer to move as quickly as we would like. So at the moment its not an option.


If you get hammered, even serving the 403-page is actually noticeable traffic.



________________________________

This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain information that is confidential and protected by law from unauthorized disclosure. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20161101/54b3cea8/attachment.html>


More information about the nginx mailing list