3 ms·
Agreed. We're full-stack AWS hosted, and I have no real indication of whether or not we've ever been attacked (doubtful) or if AWS could automatically mitigate
by themartorana 11y ago
Agreed. We're full-stack AWS hosted, and I have no real indication of whether or not we've ever been attacked (doubtful) or if AWS could automatically mitigate an attack (possibly??). I presume Netflix is probably a common target, and they're AWS-heavy, but I have no way of knowing for sure.
- mschuster91 11y ago> I presume Netflix is probably a common target, and they're AWS-heavy, but I have no way of knowing for sure. Well, DDoS operators usually don't do their job for fun (okay, I'm discarding Lulzsec and other vandalism-motivated folks here). It's much more profitable to hunt for not-CDN-backed sites and extort them for money. Or to look for processor-heavy API endpoints (e.g. login with huge work factors) to improve the DDoS effectivity, but then again a lot of DDoS ops are script-kiddies looking for a quick bunch of monies, all too often not skilled enough for this.
- caleblloyd 11y agoELB is simply a Reverse Proxy with an upstream pointing to your app servers. Last time I checked, I think they were running nginx. I doubt they have advanced DDOS detection code running on that reverse proxy. Netflix likely implements their own DDOS protection layer somewhere in their routing library. For example, since most resource-intensive Netflix endpoints are protected (you have to login to watch a movie), they could use rate-limiting based on User Account ID.