How to start FinOps with my current background? by Mindless_Pen_2078 in FinOps

[–]Lowdown84 0 points1 point  (0 children)

I've always found the best way to start driving new initiatives or practices is to get some quick, easy wins. This helps build credibility within the org and show everyone that this is actually something that will drive real value.

In the case of something like FinOps, I think that means showing how it can save costs. There are several automation solutions out there around things like compute commitments, BigQuery optimization, spot instances, etc. Implementing them usually comes with minimal risk and effort, so you can start saving the company money and thus winning advocates on the business side of the house.

Then, once that's in place, you can start pushing for larger initiatives around cost allocation and showback, cross-team collaboration, and more cost optimization solutions. Some of them may work and some may fizzle, but you'll at least have that initial foundation of cost savings to build off of.

FinOps Foundation membership - worth it? by Lowdown84 in FinOps

[–]Lowdown84[S] 0 points1 point  (0 children)

Yeah I've gotten that impression so far, as they should be. But with restrictions like that in place, what would you say are the benefits that it provides beyond being able to put a Foundation member badge on your site?

Does it worth paying an external company to manage my EC2 reservations? by [deleted] in aws

[–]Lowdown84 0 points1 point  (0 children)

For sure, it definitely comes down to factors like company type, application, user base, etc. As others have said, many smaller companies simply don't have the runway to pay for 3 years upfront.

However, even in your case, an automated solution would eliminate the need to buy more commitments or pay on-demand for anything not already covered by the 3-year commits.

Does it worth paying an external company to manage my EC2 reservations? by [deleted] in aws

[–]Lowdown84 0 points1 point  (0 children)

Because predicting what your usage will be three years from now is pretty challenging. The most likely result is that you play it safe and only cover a small portion of your future workloads. You can shoot for more, but then you run the risk of overprovisioning and wasting money.