martin-lim

3 ms·

1. 1.▲
   by martin-lim 2y ago

   That could be the same root cause. You download data via range request but with no upper bound and AWS is billing you for very much more than you downloaded in reality.
2. 2.▲
   by martin-lim 2y ago

   Sadly this is no bug. Customers are NOT billed for actual data transferred. Customers are billed for "some kind of" data requested. If you interrupt the data transfer before downloading all requested data then it's "your
3. 3.▲
   by martin-lim 2y ago

   Yes, private in the sense of "block public access" (your second point) ( https://docs.aws.amazon.com/AmazonS3/latest/userguide/access... ) Sadly, the private in the sense of "never make it to the
4. 4.▲
   by martin-lim 2y ago

   For me it looks like AWS has mainly different scenarios to handle. First, unauthenticated users are a big security pain for AWS and S3 because S3 is used for everything. But S3 was not designed for "secure" public access. As a re
5. 5.▲
   The AWS S3 Denial of Wallet Amplification Attack(blog.limbus-medtec.com)

   5 points by martin-lim 3y ago|0 comments