Learn about what cloud governance costs.
- [Teacher] So let's talk about what this should cost. Well, cost doesn't seem to be a consideration within the technical community, but in the business community it is. The cost should be considered with the value of governance. That's basically the way you want to present it to your leadership, and so governance systems could cost upward when you consider the labor and the talent and the risk and the resources that need to be placed into service, as much as a million dollars to get them implemented, just to get them into an operational state within an enterprise.
So, you need to be able to define the value, and the value with governance is of course, with compliance we talked about that, but the ability to place limits around existing resources as used in services. Guard rails for instance, allows us to see how we're going to control access to those resources. So keep in mind that the cost of the tool or service is just a fraction of the overall cost. We have a tendency to assign costs to the tools and the technology we're looking to leverage. I mean this not about that.
This is about the resources such as the talent and the people and the risk and the time it's going to take to actually get these things in place, and get these things operational. Let's answer the question directly based on what we talked about is an example of a governance cloud project. So we need to understand the requirements, find the right tools, test the cloud and governance systems, and look at cloud governance operations. So what does this take? Well, typically I'm finding that understanding your requirements takes about five weeks. Sometimes they can do it in three and sometimes it may take a couple of months depending on the size of the problem, I mean.
If we're looking at something that's relatively simple, say less than ten resources in a cloud, virtual machines, databases, things like that, and less than 1,000 services, then five weeks is a reasonable period of time just to get your requirements down, written down and understanding what needs to be managed, how they need to be managed. Perhaps even getting to the point where writing pseudocode for what the policy's are going to look like, and that's basically code that doesn't run on a machine, but defines logic and how it flows through a particular type of program. In this case a policy.
We need to find the right tools. That takes about five weeks, and that's pressing it, but you can go out there since everything is on demand, and the information is pretty much a commodity these days. It's pretty easy to research the tools you're looking for such as the cloud management platform tools, the service governance tools, things like that. Testing cloud governance, once we have things in place and things are deployed, is going to take about ten weeks. So we're placing things in service and we're testing things, and within staging platforms, and not live platforms, we're trying to understand how these things behave when they go into operations.
And then finally cloud operations. So we're going to basically put cloud governance into service and that's going to be ongoing, and so whatever we're paying for the first month of operations, we can look at that as a relative cost based on the number of resources and services that we're going to be governing. So it may cost us a million dollars to put this in place, yet this thing may cost us $50 to $100,000 a month in terms of people and processes and technology that are working on this, and as we expand the role of cloud governance and operations, we're going to see an expansion of the cost as well.
- Cloud governance basics
- Cloud resource governance
- How cloud security and governance are linked
- Defining governance policies
- Cloud management platform basics
- Reviewing service governance tools
- Cloud governance costs
- Understanding your requirements
- Finding the right tools
- Testing cloud governance
- How operations deals with governance