Open pkit opened 6 years ago
This isn't really anything to do with zappa. I've had a similar situation occur completely outside of zappa. It's just Amazons' way of stopping DOS attacks. You'll be glad it's in place if someone apart from you was to do this to your server.
This is fascinating and not something I have encountered. Would an option to change the refresh rate be satisfactory?
From my phone..
On Feb 17, 2018 11:05 AM, "Nick Polet" notifications@github.com wrote:
This isn't really anything to do with zappa. I've had a similar situation occur completely outside of zappa. It's just Amazons' way of stopping DOS attacks. You'll be glad it's in place if someone apart from you was to do this to your server.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/Miserlou/Zappa/issues/1315#issuecomment-366450942, or mute the thread https://github.com/notifications/unsubscribe-auth/AAIi0_cHJQbabiNXFrCeA2uKcPmuw7z-ks5tVvi6gaJpZM4RL7Z5 .
Would an option to change the refresh rate be satisfactory?
I suppose so. Switched to chalice
meanwhile.
This isn't really anything to do with zappa. I've had a similar situation occur completely outside of zappa.
So? If something happens because zappa is hammering AWS with 1req/sec and also happens because something else can hammer AWS with 1req/sec it somehow makes it ok? :)
Context
Left log tailer running overnight accidentally, got my IP banned from
aws.amazon.com
Expected Behavior
Be able to access aws services
Actual Behavior
No access to ANY aws serivce. I.e. full block for
*.aws.amazon.com
*.amazonaws.com
Changing IP address works around the issue (obviously).Possible Fix
Probably need either hammer log services less frequently (currently hardcoded as 1req/sec) Or just stop if running for a long time
Steps to Reproduce
zappa tail
for 24 hours from residential IP address.Your Environment