Replies: 3 comments 6 replies
-
thanks for the hint, might be worth a try to report it with some of the log entries |
Beta Was this translation helpful? Give feedback.
-
Amazon allows abuse. For 24 hours I have a server that is subject to a tornado of accesses from IPs owned by Amazon. The same pattern 2 - 3 accesses then it stops. We have up to this moment 4050 IPs caught and blocked in the ISP's router and the number is increasing. Most likely we will permanently block entire ranges of addresses. I will complain to Amazon again, but I don't have high expectations. It is obvious that those who manage the products they sell are incompetent. In the present case there is a moron who has created an AWS network to abuse websites. |
Beta Was this translation helpful? Give feedback.
-
Today we changed the strategy. We redirect all requests coming from Amazon IP addresses to ... Amazon.com and to the senders. If they want to harvest a domain it would be best to do it at the source. The intensity of the attack decreased significantly. |
Beta Was this translation helpful? Give feedback.
-
For a few days Amazon flooded my webservers logs. Here are a part of the actions added products to the cart, comparison, trying to create accounts, checkout process without finishing, search a long list of words and phrases. At this moment there are 40 established connections in a server. The behavior is different from a crawler it looks like a DoS.
If someone is facing with something like this, the fast solution is to block the following ranges of IP addresses. I am using Fail2Ban and IPset to catch every IP automatically then I use IPRange to join individual IP's in ranges.
47.128.16.0/24 .. 47.128.31.0/24
Beta Was this translation helpful? Give feedback.
All reactions