[hcazz]

I'm convinced folks who complain about "unexpected recurring small bills on AWS" have never taken the five minutes it takes to learn to using the billing console.

It's like asking why the knife you're using keeps cutting you when you put your finger on the sharp end. Learn to use your tools, and they won't surprise you. Learn to track your costs, and you won't have unexplainable recurring bills.

[papaf]

It's like asking why the knife you're using keeps cutting you when you put your finger on the sharp end.

Most cloud providers don't have this billing problem and so the analogy breaks. Its more like, why does this knife keep shooting me in the foot?

[aiCeivi9]

> five minutes it takes to learn to using the billing console.

I spent hour or two trying to find anything running and didn't find a damn thing. Yet Amazon decided to charge me a buck or two every month for "storage" so I just canceled whole account. I mean, if I can't find what I am paying for when not using it, how am I supposed to understand the bill when I actually have a dozen of instances?

[CJefferson]

That's a good comparison. Have you ever cut yourself with a knife, any time in your life? I certainly have. I've also had a £150 AWS charge I had to pay.

In both cases I learnt my lesson. I'm careful not to put my fingers where a knife can cut it, and to not put my bank details where AWS can charge them.

[lordlimecat]

Were in a room with 150 engineers, techies, and problem solvers who have been asked whether a cutting implement is overly complex or dangerous.

100 of them have provided an opinion and 99 of the opinions are that it is. Everyone in the room is bleeding.

I think it's fair to say that there's an issue with the tool, Stockholm syndrome not withstanding.

[pojzon]

Yup I also do find those arguments ridiculous. „I cut myself because I dont know how to use knifes, but its the knife fault fpr cutting me”.

You can even enable scans for unused respurces that generate costs..