Will lack of cloud governance be your Achilles heel?
The benefits of cloud are well heralded – pay as you go, opex v capex, spin-up / spin down, the list goes on. There is little doubt that Cloud is quickly becoming mainstream and is no longer the bastion of the technophile.
A recent survey on cloud adoption indicated that 80% of medium to large enterprises have plans to increase their cloud adoption in the next 12 months. Most surprising however was that nearly 60% of these organisations indicated that they had overshot there cloud budgets in the past. Most cited issues with holding the organisation and lines of business accountable for cloud spending as the primary cause (their Achilles heel).
At Kumolus we have focused on this issue to deliver capabilities in our platform that allow you to:
Set expenditure quotas per project / business unit / or environment
Organisations are notoriously poor when it comes to managing technology budgets and with cloud this becomes inherently more difficult. The key to managing cloud budgets across large organisations is visibility and control amongst the teams that are using the services. This ensures you remain informed on the state of your expenditure and can take appropriate actions in controlling your spend to avoid what is now commonly referred to as ‘Bill Shock’.
Identify opportunities for cost optimization
As an organisations cloud adoption increases and the subsequent number of cloud services being consumed grows, the identification of which services are and are not being effectively utilized diminishes. It is important that organisations have a defined method for reviewing their cloud environments and the services being consumed to pin-point potential optimization opportunities. Having a disciplined approach to identifying and addressing inefficiencies is critical in controlling cost in the cloud.
Define your Cloud SOE
With so many cloud resources readily available for consumption, an organisation needs to be weary of ‘Cloud Sprawl’. Cloud sprawl refers to the proliferation of an organization’s cloud instances, services or providers. It occurs when an organization lacks visibility and control over its cloud computing resources. It is important for an organisation to define which resources will make up their Cloud SoE thereby ensuring control around the cost and time taken to deploy, configure, maintain, support and manage your cloud services. Furthermore, it is essential to create policies to govern the deployment of these specific SoE patterns. Having a Cloud SoE and governing policies around its use will allow the organisation to fully exercise cloud control.
Enforce resource tagging for ongoing management
Tagging your cloud resources will allow you to more readily identify, track and manage your services. Applying a structured approach to resource tagging will allow the organisational to enforce standards and invoke discipline aimed at ensuring that the required break-down of your cloud spending is attainable.
Schedule the shutdown of services that are not being used
On demand, spin up / spin down and pay for use are the ‘out-of-the-box’ benefits of cloud, so why pay for cloud resources if they are not in use. It can be good practice to automatically schedule when cloud resources will and won’t be available, particularly focusing on those services that are periodically accessed during project phases or in response to specific operational needs such as some development and test environments. This allows the organisation to maximise resource usage and remove any costs associated with idle / unused resources.
At Kumolus we believe in prevention over cure and planned over unplanned. Don’t allow cloud governance to be your Achilles heel – trial the Kumolus Cloud Management Platform today at www.kumolus.com