How an empty S3 bucket can make your AWS bill explode

Re:How an empty S3 bucket can make your AWS bill explode by indigodaddy on Tuesday April 30, 2024 @06:02PM (#40216955)

private in the sense that the connection will never make it to the S3 bucket, is that correct?

private in the sense that it is locked down to allowed source IP's or IAM-- then the connection still gets there and AWS incurs a charge for the Access Denied response, etc

[ Parent | on HN ]

Re:How an empty S3 bucket can make your AWS bill explode by martin-lim on Thursday May 02, 2024 @02:11AM (#40233205)

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 S3 bucket" is nearly impossible. May this can be achieved by choosing some "secret" S3 bucket name.

[ Parent | on HN ]