[stressback]

I read a lot of the posts at the little blog here and, uh, every single one sounds like a complete amateur making a cloud configuration mistake. I haven't found one that is the provider's fault or the fault of "serverless"

I would be embarrassed to put my name on these posts admitting I can't handle my configs while blaming everyone but myself.

Serverless isn't a horror, serverlesshorrors poster. You are the horror. You suck at architecting efficient & secure systems using this technology, you suck at handling cloud spend, and you suck at taking responsibility when your "bug" causes a 10,000x discrepancy between your expected cost and your actual bill.

Just because you don't understand it doesn't mean it sucks

[Cpoll]

You're not wrong about cloud configuration mistakes, but a tool that lets you increase costs 10000x (without even letting you set a safety) is a hell of a chainsaw.

I'm more worried about the overconfident SRE that doesn't stay up at night worrying about these.

[bhk]

Consider this analogy: Instead of using a root command shell, it is wise to use an account with appropriately restricted capabilities, to limit the downsides of mistakes. Cloud services support the notion of access control, but not the notion of network resource usage limits. It's an architectural flaw.

Or do you always log in as root, like a real man, relying purely on your experience and competence to avoid fat-finger mistakes?

[Bluecobra]

That being said, the cloud providers could do a better job explaining to new/naive users that great power comes with great responsibility and there is no hand holding. Someone might be more hesitant to willy nilly spin up something if a wizard estimates that the maximum cost could be $X per month.

[McGlockenshire]

> every single one sounds like a complete amateur making a cloud configuration mistake

Golly if only the configuration wasn't made this way on purpose exactly to cause this exact problem.

[webdevver]

truth nuke