Cool. Enjoy!

Yup.

One day, as you spend vast resources tracking and cutting and worrying about your AWS expenses, you’ll think “hey I could cut 100% of AWS costs by not using it!”.

Thinking about cutting AWS costs is your first step on the journey to never using it.

That’s great, until realise that you’re now spending money on infrastructure elsewhere instead.

I’m not going to pretend AWS is cost effective for every type of problem. But the comments here are overly simplistic.

Also, and more generally, I find it disappointing that when someone has made an open source tool to help the community, most of the comments are cheap attacks at the cost of running AWS. Poor etiquette guys.

> I’m not going to pretend AWS is cost effective for every type of problem. But the comments here are overly simplistic.

There overly simplistic comments from the "run from AWS" crowd as well as from the "just outsource everything to cloud" crowd. Nowadays going to cloud is still the easiest and safest bet if the company is not yours and it's big enough.

Run from AWS is also completely arbitrary. Someone building an expensive Rube Goldberg machine out of lambdas might hit cost problems way before someone essentially using AWS as a VPS provider with bare metal EC2

> There overly simplistic comments from the "run from AWS" crowd as well as from the "just outsource everything to cloud" crowd.

Not in this thread there isn’t. And that’s what I’m replying to.

Sorry, I didn't understand the comment

Using Hetzner or IVH will cut your infra bill by 4x or 5x

This is true, but be careful about losing the work experience. Companies love cloud computing and somehow are conditioned to want to pay for them and anyone who works on them. I received a devops job application rejection because they didn't see cloud computing providers on my resume. That's because I highlighted running my own dedicated servers.

That’s because architecting stuff for the cloud effectively means you’re building your infrastructure differently to how you’d run dedicated servers. I say this as someone who’s done both professionally.

As a DevOps hiring manager, if you said to me “I don’t have cloud experience but I can do all the same things with dedicated servers” then I’d likely pass on you for another candidate too.

A better way to frame your applications is “I have significant on prem experience using DevOps methodologies, and I’m excited to broaden them with Cloud technologies.” That way you’re acknowledging your knowledge gap and turning it into a positive.

Using AWS may not be your decision. If you're stuck using it by company policy, OP's tool could make you a workplace hero.