3 ms·
Consider: my team owns a public-facing website for AWS and relies on a number of back-end services to support it. We occasionally face DoS attacks. And sometime
by mabbo 6y ago
Consider: my team owns a public-facing website for AWS and relies on a number of back-end services to support it. We occasionally face DoS attacks. And sometimes, they can get past our various security measures to prevent them.
By everyone else having quotas on how often I can call their systems, they protect every other client they have. They protect customers who are using anything other than my website. Otherwise, someone could take down all of AWS by spamming just one system. I want them to throttle me, quota me, because I want to protect other customers if I get compromised.
And even if it's one internal system calling another, it's better to have protection at every layer than to try to only have it on the outer layer.
This can burn us, of course. We're always growing, and quotas need to be managed (automatically or manually). It all has to be done carefully.
Edit: as always, I speak for myself and not for AWS in any official capacity. I'm mabbo, not jeffbar :)