[epberry]

This post, along with this Simon Wardley thread, https://twitter.com/swardley/status/1088780650860158978?s=20, attracted me to finops as an engineering problem. Consumption based pricing is really tough for a lot of orgs to handle at the $1M+ range, so much so that it requires dedicated software to line things up.

I started helping maintain https://ec2instances.info in my spare time and the code base is literally full of IF statements to paper over AWS billing quirks. Later, I joined Vantage, one of the companies linked in the article.

It's a little bit undecided whether finops will have the growth that devops did but the problem is seemingly felt very acutely.

[bigtones]

I love using https://ec2instances.info as a reference - thank you for maintaining it !

[red-iron-pine]

> attracted me to finops as an engineering problem. Consumption based pricing is really tough for a lot of orgs to handle at the $1M+ range, so much so that it requires dedicated software to line things up.

absolutely. massive struggle at the orgs I've been / am at.

processes for provisioning new resources haven't changed, and a lot of teams kind of push their own builds, or get reservations for X amount of space and dollars and then they can play with their space.

the result is OpEx shifts wildly from one quarter to the next, and control has been hit or miss. it continues mostly because projects need to deliver -- and do -- but that "do what you gotta do to make it work" approach has turned basically into the wild west and no one plays by the rules.

[epberry]

Yeah. In an infrastructure as code setup there's some more rigor that can be applied, at least in terms of tagging what's going out. But I've generally seen the finops team come in and optimize ex post facto.

[avn2109]

Thank you for ec2instances! I use it a lot and it's really great :)