No blank checks: The value of cloud cost governance

No blank checks: The value of cloud cost governance

How much does you’re public cloud cost month to month? If you don’t know, you’re hardly alone. Most people in IT don’t have a good understand of what a public cloud service costs per month. Most wait to find out what the bill says rather than proactively monitor cloud consumption, much less have cloud cost governance in place.

Even if your financial budgeting model can handle uncertain costs, not knowing what you’re spending has a downside. When you moved to the public cloud, your company put a value driver in place when defining the business cases—and part of that was based on ongoing costs per month.

If those costs are higher than originally estimated, the value metrics won’t support your goals. Although you can make a case for the cloud’s value around agility and compressing time to market, that will fall on deaf ears among your business leaders if you’re 20 to 30 percent over budget for ongoing cloud costs.

There’s no reason to not know your ongoing cloud costs. In the planning phase, it’s just a matter of doing simple math to figure out the likely costs month to month. In the operational phase, it’s about putting in cost monitoring and cost controls. This is called cloud cost governance.

Cloud cost governance uses a tool to both monitor usage and produce cost reports to find out who, what, when, and how cloud resources were used. Having this information also means that you can do chargebacks to the departments that incurred the costs—including overruns.

But the most important aspect with cloud governance is not monitoring but the ability to estimate. Cloud cost governance tools can tell you not just about current use but also about likely costs in the future. You can use that information for budgeting.

Cloud cost governance also means placing limits on cloud computing usage based on allocation of costs. If the devops team is allocated $150,000 a month but spends $200,000, the tools should take automated corrective action—meaning turning off cloud services after multiple warnings. The idea is not to stop productivity but to make people aware of what costs they are incurring over that of what’s been budgeted.


Source: InfoWorld – Cloud Computing