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

[–] UFODivebomb@programming.dev 8 points 5 months ago

I think it's a combination of things. My experience definitely parallels yours: when developers have access to the bill they tend to realize the cost of the services they are using. Sometimes even resulting in optimizations to those costs.

At the same time AWS can get fucked with how horrible their bills are to understand. They don't exactly go out of their way or even slightly on a good path to deliver a clear bill.

So even if the developers have access to the bills they might just end up with an impenetrable list of bullshit from AWS