User: you charge me when people make unauthorised requests to an S3 bucket?

AWS: yes of course

User: but

AWS: working as intended

User: but

AWS: thank you for your money

https://medium.com/@maciej.pocwierz/how-an-empty-s3-bucket-can-make-your-aws-bill-explode-934a383cb8b1

How an empty S3 bucket can make your AWS bill explode

Imagine you create an empty, private AWS S3 bucket in a region of your preference. What will your AWS bill be the next morning?

Medium
@jonty
I am trying to wrap my head around this. If a bad actor wanted to harass a person or organization that is running a service using S3, and can figure out bucket names, they could trivially make the target run up a bill of tens of thousands of dollars and there's absolutely nothing that can be done about it except begging AWS for mercy?
@tetron @jonty @clementd hot tip: use an S3 provider that doesn't charge egress or API fees... Backblaze, Wasabi, OVH, Leviaa, ...

@tetron @jonty @clementd Follow-up tip. In regular usage any of these suppliers will be 5-10x less expensive than doing S3 from Amazon anyway. Unless your entire infrastructure is based on AWS there’s no good reason to ever use Amazon’s S3 service (and even then it’s debatable)

Additional option: roll your own with something like Minio, Scality, …