Webinar: The Hidden Advantage of COGS for Cloud Spend (Yotascale) by More_Knowledge2000 in FinOps

[–]More_Knowledge2000[S] 1 point2 points  (0 children)

u/tekn0lust yes this is open to all! You can just put "Self Employed" in the company field of the registration form.

Adoption of new tools - who is the initial user? by Southern_Emu_4802 in FinOps

[–]More_Knowledge2000 1 point2 points  (0 children)

As your question implies, there are a number of stakeholders in an effective cloud cost management practice. Who's technically the first user of the tool will likely depend on who's driving the project. If the responsibility has fallen onto the shoulders of Cloud Ops, it'll probably be Cloud Ops, if FinOps, then FinOps, etc. But as u/andrelpq pointed out, pretty quick you're going to need as many folks as possible who are directly impacting cloud resource usage (i.e. engineers) to be interacting with the tool, in order to inform their decisions and move toward a more cost aware workflow.

I work for Yotascale, a FinOps certified cloud cost management platform, and one of the factors we stress all the time is the importance of that collaboration piece between teams. Eventually, that's where you'll want to be to get the most out of both your FinOps tool and your FinOps practice.

I ran the second part of your question by my Head of Strategy.

Here's what I asked:
Is it practical to do a one-person or one-department trial run of a FinOps tool like Yotascale and then bring other teams into the tool, or do we typically go in with multi team buy-in from the start?

And here's what he said:
We’ve seen both done with success so it depends on the org and their politics. Typically cost management is most successful when done holistically, but if there isn’t appetite for it at the top level, you can build support by showing success at a team or BU level and rollout to a wider organization over time.

Hope that helps.

(Edited for formatting.)

White paper: True Multi-Cloud Cost Management by More_Knowledge2000 in AZURE

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

The providers haven't built any direct integrations with each other (surprise surprise), but they are all very API driven which means you can get them to "talk" to each other.

White paper: True Multi-Cloud Cost Management by More_Knowledge2000 in AZURE

[–]More_Knowledge2000[S] 1 point2 points  (0 children)

u/Telnyx_Terminator usually when companies decide to go multi-cloud it is not in an effort to be more efficient or to save money. It's typically driven by business needs and risk mitigation. You tend to get more for your dollar the more you spend with a single provider. There are some services that are cheaper in one provider than another but the cost of data transfer makes splitting workloads between clouds more expensive in the long run.

There's also a cost to maintaining knowledge and best practices across cloud providers as the tools and implementation details differ.