Take this 5-step assessment to see how prepared you are to avoid these five common and disastrous cloud pitfalls. Along the way
you’ll learn how to prepare your project for cloud success.
Underestimating Bandwidth Requirements
Your network may be running like a well-oiled machine today, but what happens when you move workloads to the cloud?
Every packet that moves in, out and across clouds consumes network bandwidth, which may already be maxed out. Failing to plan for these extra file transfers, database transactions, service broadcasts and backups can quickly grind your existing and new cloud workloads to a halt.
Failing to Understand the True Costs
Nobody likes getting sticker shock, but without proper planning that’s exactly what you’ll have when the first bill arrives. Cloud providers charge for uptime of all the components that make up a cloud workload – compute, storage, memory, networking, bandwidth, and more. Not having a clear picture of the costs and, more importantly, how you will control them can quickly leave you with a skyrocketing bill.
Thinking All Clouds Are Created Equal
It’s easy to think that the mega clouds – AWS, Azure and Google Cloud Platform – are created equal and the only distinction is price, but this is simply not the case. Your specific use cases and requirements, especially 3rd party app compatibility and availability of the services you’ll use in the respective cloud marketplace, must dictate which cloud provider(s) you use. Failing to fully vet public cloud platforms could lead your cloud project down a dead-end road with a pricy U-turn.
Coming Up Short on Staff and Skills
Let’s face it, public cloud technology is complicated. You may have a rock-star team of on-premises experts, but designing, implementing and supporting cloud workloads is a whole new game. If you don’t yet have in-house cloud expertise, it’s best to staff up at the onset to keep the project running on-track and on-budget. Failing to account for staffing gaps can not only derail a project but lead to massive unplanned expenses along the way.
Assuming the Public Cloud Provider Has You Covered
Yes, most mega-clouds meet government compliance and regulatory requirements, but the onus for establishing governance still falls on you. The shared responsibility model of public clouds require that your organization establishes security policies, operational procedures, DR plans, and governance models to ensure data security. Assuming your cloud provider is going to cover all your compliance and governance needs can leave you in serious hot (and legal) waters.
How did you do?
Learn from our cloud experts about how to avoid these cloud failures and download, "Designing a Cloud Strategy for the Real World," by George Crump of Storage Switzerland.
Have you calculated the bandwidth requirements of your cloud project and planned for additional capacity?
Do you have a clear understanding of the costs involved in your cloud project and how you will limit spend by deactivating or powering down idle workloads?
Have you done due diligence to determine if everything you need to support your cloud workload can be accomplished on your desired public cloud platform?
Is your IT team adequately budgeted, staffed, and trained to successfully complete the entire lifecycle of your cloud project?
Have you established a cloud governance team, including legal, compliance, security, operations, and even PR?