Programming

17354 readers

338 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 1 year ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

118

Fix Incoming! Empty S3 buckets won't be able to make your AWS bill explode (aws.amazon.com)

submitted 5 months ago by pro_grammer@programming.dev to c/programming@programming.dev

14 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] VeganCheesecake@lemmy.blahaj.zone 18 points 5 months ago* (last edited 5 months ago)

Haven't read into this too much, but I think the affected person that made this get attention was a solo dev that was prototyping a solution for one of his customers.

And the reason he raised a stink was because he had a huge bill, as the name he chose for his bucket was by chance the same an open source project used as a sample bucket name, so whenever someone deployed it without first customising the config, it was pinging his bucket and getting a 403.

Edit: Here's his original medium post / Archive