budget enforcement is our next cloud governance principle
in this module will cover the concepts of budget transparency and agnostic reporting.
We'll also be looking at some best practices around proactive enforcement.
All organizations care about cost control
in the cloud of the cost management optimization and reporting life cycle requires that CFO's received assurance that cloud spend can be controlled and budgets adhere to and respected.
While this sounds simple enough, the reality is often different at any scale in the cloud.
As we discussed earlier, providing a single cloud account or subscription to a user is synonymous with giving them their own data center.
Controlling costs, while still empowering users with the power of the cloud, is a balance that must be struck early to avoid unexpected overruns.
One of the first steps in budget enforcement is providing cloud users transparency to their cloud costs.
Sounds straightforward, but the cost of cloud computing alone, with nothing to compare or related against, provides very little value to the end user.
Aligning the cloud account or subscription with a budget
gives dimension to resource costs over time and provides more context around spend on a daily or weekly basis.
This visibility to cloud costs with the added context of how it fits within a budget provides users with a fuller picture of their cloud spending trajectory,
enabling them to better plan and strategize efforts for the long term.
Another dimension of budget enforcement is proactively handling waste management. This could be a simple is turning off resource is and non production environments when not in use or alerting users and leadership to unused or orphaned resource is provisioned. Cloud resources continue to turn the meter and generates Ben
whether they're being used or not.
So handling these concerns at scale requires an automated and programmatic approach. As most cloud services are billed in single second Interval,
nothing will stifle cloud adoption in an organization faster than unbounded and unaccounted expenses.
Establishing an automated solution toe automatically and proactively look for re sources that are over provisioned and underutilized can help drastically pulling unnecessary costs.
One best practice that can alleviate complexity and understanding cloud costs at scale is providing users agnostic data reporting from multiple cloud service providers. A cloud tamer. We've seen an increase over time in the amount of organizations that work with more than one cloud service provider.
So here's an example of how we provide this agnostic reporting in our tool.
Here we are inside Cloud Tamer at the organizational chart for Company A.
As we drill down into the company's structure, we see the research and development department within research and development. There are a number of projects with associate ID accounts and subscriptions from multiple cloud providers.
For instance, in the Asthma research project alone, there is an AWS commercial account, an azure subscription and an address CSP Resource Group
with agnostic reporting at any level, a user with the right permissions can select, in this case, the Research and Development Department and poll aggregated financial reporting.
This first spending view gives us a summary of cost across all of the accounts underneath.
But if we want to drill in more, we can go into spend reports and filter the data even further, say by cloud provider.
Now we can see the cost breakdown between AWS and Azure. In this case,
we can take it one step further by filtering our results. But each cloud service giving us a full breakdown of both AWS and azure services that have been used in all of the accounts and subscriptions in research and development.
We couldn't even isolate our particular service in a month to view resource level details around the spend, giving us even more insight.
Another best practice in budget enforcement that we have brought to our cloud tamer customers is proactive budget enforcements.
This allows users to create automated enforcements that could be configured to take any number of actions. When a cost threshold is reached,
back in cloud tamer. We're taking a look at this remote support project,
which we can already visually tell is overspending their planned budget.
Let's go into enforcements to see how they work. And if we can tighten the reins on this particular environment
in enforcements, we have a myriad of options to create an appropriate custom trigger.
We could set the enforcement on a particular cloud service or on the entire project, which will do here.
We can also customize the timeframe and spend type of this trigger
for this first enforcement.
We're going to set the trigger when monthly spend surpasses 85% of her monthly budget for this project.
When that happens, let's have our developers on this project notified. We hit save and then see that our enforcement is active on the project.
And because this project is already passed this spend threshold, the enforcement automatically triggers sending email and platform notifications to our Debs that this enforcement has been triggered.
Now let's add in another enforcement.
Let's set this one to trigger an event when spending is past 95% for the given month.
When that happens, we'll have this enforcement kick off a cloud resource that will restrict easy to skews to those that are under $2 an hour.
Once we save this enforcement and it's triggered, we can actually see that this cost restricting cloud resource has been deployed within this project
and its cloud environment.
Finally, let's make an enforcement that triggers at 99% of our monthly spend
this time, we'll have it kick off a system freeze rule and notify. Our admits
This system freeze rule deploys policies to the project to deny all but read only actions in this environment,
meaning no one can spend up. New resource is creating additional spend.
These are just a few examples of how our customers use proactive enforcements, toe limit cloud costs
to review providing users of an organization with cloud cost transparency. An agnostic reporting is instrumental for finding balance in budget enforcement.
Also, establishing proactive enforcement actions can give financial leaders peace of mind that cost won't spin out of control.