4 ms·
This must be a regression bug in AWS's internal system. At a past job (2020) we used S3 to store a large amount of genomic data, and a web application read rang
by nicklecompte 2y ago
This must be a regression bug in AWS's internal system. At a past job (2020) we used S3 to store a large amount of genomic data, and a web application read range requests to visualize tiny segments of the genetic sequence in relevant genes - like 5kb out of 50GB. If AWS had billed the cost of an entire genome/exome every time we did that, we would have noticed. I monitored costs pretty closely, S3 was never a problem compared to EC2.
It also seemed like the root cause was an interrupted range request (although I wasn't fully clear on that). Even so that seems like a recent regression. It took me ages to get that stupid app working, I interrupted a lot of range requests :)
- __roland__ 2y agoYou are right, this is about canceling range requests and still getting billed, not about requesting ranges and getting billed for the complete file egress. Sorry; we'll make the post clearer.
- nextaccountic 2y agoThis seems like something that customers can potentially sue for. AWS is overcharging them and not correcting the bug once they become aware of it.
- nielsole 2y agoS3 egress costs are free if the traffic stays within AWS. Sounds like your clients were EC2 instances so this wouldn't apply to you, would it?
- mikepurvis 2y agoIf it was a web application as stated in the GP, then it would indeed be egress as the request would be coming from a browser.
- nicklecompte 2y agoYes, it was client-side JavaScript making the range requests, asking for a string of genomic data to render in the browser. It was only to give the scientists a pretty picture :) The EC2 costs were largely ElasticSearch for a different function, which never looked at the data in S3.
- belter 2y ago> S3 egress costs are free if the traffic stays within AWS Not if it's cross-region.