10 Hidden Costs in the Public Cloud

By Mark Tonsetic

10 Hidden Costs in the Public Cloud

The public cloud is emerging as a disruptive innovation for IT -- and not just for small and medium-size businesses. At this point, most large enterprises are experimenting with the public cloud as a development-and-test resource, or for production applications with low security, privacy and service level requirements.  The conventional wisdom is that the public cloud may even be just a niche interest for large companies, given their extensive legacy investments and the mission-critical nature of their systems. Nevertheless, a number of these companies do see big potential in the public cloud; they feel an acute need to choose between proactively working with the public cloud or getting left behind.

At the Corporate Executive Board, we have spoken with many of the early enterprise adopters of public cloud services from vendors such as Amazon and Rackspace. Naturally, the applications that these enterprises have considered for the public cloud are studied for their cost-effectiveness in this model.  Below is our consolidated feedback from these early adopters on the 10 hidden costs in the public cloud. We've broken these cost areas into four broad categories to watch:

  • One-Time Migration Costs
  • Billing Model Limitations 
  • Retained Management Costs
  • Risk Premium

One-Time Migration Costs

These are costs associated with the migration of existing applications from traditional, physical infrastructure to public cloud, including applications retrofitting time, server migration time, and potential impact on depreciation write-offs.

In this category, there are two potential costs to watch:

  1. Application retrofitting. The majority of a typical company's in-house application portfolio is not yet cloud-ready. Some of applications already suitable for virtual machines, or developed according to platform standards, can be ported easily. But most applications would require considerable retrofitting or recoding to become compatible. This is particularly true of legacy applications. Organizations need to evaluate the cost effectiveness of porting these applications, versus leaving them as-is or even totally decommissioning them in favor or new applications. Promoting platform standards, and building the business case for a technology refresh, have been perennial challenges for application teams. This remains true when considering the public cloud.
  2. Depreciation write-offs. Companies that choose to accelerate application or infrastructure refresh in order to jump-start public cloud migration face the possibility of no longer writing-off depreciation on existing hardware.  That explains why many companies are thinking of evaluating the cloud at existing refresh points.

Billing Model Limitations

There are three features of the current public cloud billing model that may be a poor fit for your enterprise applications.

  1. Elasticity premium. One of the most heralded features of the public cloud is its pay-as-you-go billing feature, which enables companies to tackle increasing application loads at peak usage time. Since prices are set accordingly, this may come at a premium for applications that sit in the public cloud full-time and don't peak greatly above their routine base.  For example, consider that Amazon's Large On-Demand Windows Instance costs 48 cents per hour while its comparable Reserved Instance is just 20 cents. Choosing the right type of cloud instance for each application is important; applications with steady or predictable workload will not be most cost effective in the on-demand models.
  2. Toll charges. The in-bound and out-going data transfer charges in the public cloud are a significant factor to keep in mind, especially for applications that experience heavy data usage. For instance, Amazon charges 10 cents per GB inbound and between 8 cents and 15 cents per GB transferred out. The additional latency introduced due to large-scale data transfer requests on the cloud servers is also a cause for concern.
  3. Storage costs. A virtual, multitenant server architecture introduces new storage costs and complexity, creating the need for optimization tools such as storage virtualization, thin provisioning and data de-duplication. These are tools with which most companies are just beginning to become familiar.

    10 Hidden Costs in the Public Cloud: Management and Risk

Retained Management Cost

It's important to keep in mind that you will have overhead for retained services that you will still need to provide internally even after moving to the public cloud. Here are four key management areas to watch:

  1. Security, particularly OS patch and anti-virus management. Certainly, there are routine and augmented security precautions to be taken when working in the public cloud.  There are basic costs associated with software licenses, upgrades and maintenance for patching and anti-virus software.  These costs are present whether a company chooses a public or private cloud, or opts for a more traditional on-premise, physical infrastructure.
  2. Backup. Most public cloud offerings do not include backup.  That is one of the many reasons why wholesale public cloud migration is not even being considered by many enterprises. Many companies would still need a full-scale internal infrastructure for backup and recovery. This is just another cost borne directly by user companies, bumping up the total cost of the public cloud service beyond its sticker price
  3. Load balancing and auto-scaling.  These functions are mandatory in order to be able to handle system requests and achieve optimal resource utilization and avoid overload. These activities require dedicated hardware and expensive new software, and oftentimes these costs fall to enterprise customers rather than being absorbed by the cloud vendors.
  4. Integration services. These are necessary for ensuring seamless compatibility between on-premise systems and cloud-based systems. Organizations moving to the public cloud will need to invest in expensive integration software to achieve this.

Risk Premium

Above all, enterprises using the public cloud must always be prepared for worst-case scenarios. You'll need to prepare for the potential expense of having services transitioned back in-house in the event that your public cloud provider experiences a failure, or you simply no longer want to use their services. It's important to consider the expenses that will be involved in such a migration effort.

Here's one key cost area to watch in this category:

  1. Exit plan. A solid game plan is needed to migrate back from the public cloud to a fully private setup (high unlikely) or onto another cloud vendor (more realistic). This type of exit plan requires additional time and energy as well as access to surge funding. These migration costs would not be high for companies that are already bursting from private to public cloud, or are otherwise embracing standards for portability. But, for most companies, these are not yet common practices, and so any venture into the public cloud should set aside funding for a sound exit strategy.

About the Author

Mark Tonsetic is practice manager at the Corporate Executive Board.

This article was originally published on 06-07-2011