2 ms·
> The surprising part here is lack of DDoS protection on your end or leaving a bucket public and exposed. It doesn't take anything near DDoS. If you dare to p
by Dylan16807 2y ago
> The surprising part here is lack of DDoS protection on your end or leaving a bucket public and exposed.
It doesn't take anything near DDoS. If you dare to put up a website that serves images from S3, and one guy on one normal connection decides to cause you problems, they can pull down a hundred terabytes in a month.
Is serving images from S3 a crazy use case? Even if you have signed and expiring URLs it's hard to avoid someone visiting your site every half hour and then using the URL over and over.
> AWS is just charging you for how much it served, it doesn't make sense to hold them to a fault here.
Even if it's not their fault, it's still an "inherent vulnerability of S3 pricing". But since they charge so much per byte with bad controls over it, I think it does make sense to hold them to a good chunk of fault.
- catlifeonmars 2y agoI think this just boils down to: S3 is expensive. It’s orthogonal to DDoS. Of course, the same principle applies for any expensive resource: put DDoS protection in front of it.
- Dylan16807 2y agoIt boils down to: S3 is expensive in a way that's hard to control. Do you expect DDoS protection to kick in from one person downloading a single digit number of images per second?