You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One thing that I think is especially important is to monitor is lambda scaling since the default account limit is 1000 concurrent instances and 1000 lambda instance running none-stop will be very expensive and while amazon claims that CloudFront protects agains d-dos attacks, I still want to know if someone runs an ab -c 1000 on my endpoint.... which isn't really a d-dos.
The text was updated successfully, but these errors were encountered:
Good hint, although by quickly looking over it, it seems like a slightly different syntax for vanilla alarms. I think I have to experiment more with it to see what problems that plugin tries to solve.
That's interesting, I would be 👍 to merge a documentation about this.
This could fit well as a new article in the Environment section:
One thing to keep in mind if you put some examples: explain clearly what the alerts are about. The code example you posted is interesting, but to be honest it's hard to clearly understand when the alarm triggers exactly.
I'd like documentation about CloudWatch alarms.
I'm not fluent in that topic yet but i'll have to experiment with it in the future so I can add something in the coming weeks.
I mean something like this CloudFormation template:
One thing that I think is especially important is to monitor is lambda scaling since the default account limit is 1000 concurrent instances and 1000 lambda instance running none-stop will be very expensive and while amazon claims that CloudFront protects agains d-dos attacks, I still want to know if someone runs an
ab -c 1000
on my endpoint.... which isn't really a d-dos.The text was updated successfully, but these errors were encountered: