Three main barriers between AWS and businesses
Recently Gathering Clouds’ friend and cloud computing expert David Linthicum dug into a few ways in which AWS continues to create gaps between its offering and businesses.
While Linthicum focused on cost, contract, and utility-based computing issues, we thought we would explore a few other obstacles that still keep AWS from full enterprise adoption.
While we are sure AWS will eventually figure out how to crack the enterprise, (especially as enterprise IT becomes more comfortable with the cloud) there are aspects of the service that still don’t go far enough to fulfill the requirements of the businesses that are still tentative about cloud adoption.
1) Compatibility issues: AWS created*planned* conflicts with integrating with other systems.
Without any compatibility between AWS-specific tools, platforms and environments with in-house systems (no matter which platform a business is running in house – VMware, Windows, Citrix, etc., Amazon won’t be compatible), businesses either have to forego using the service, or make the choice to go all in. The latter being 99% of companies of scale will reject.
With AWS, companies also cannot build hybrids, move workloads between environments, or automate DR, among other desired features. This presents most companies with a zero sum decision, which is typically made for a more complex platform, or offloading less mission-critical (and thus smaller) components of infrastructure to AWS.
2) Compliance concerns: Linthicum touches on SLAs/Contracts, but compliance is a major sticking point for companies looking at AWS as well. Because AWS is the preeminent multi-tenant cloud platform, it cannot be as compliant as dedicated infrastructure deployments, or as a managed infrastructure from a hosting provider specializing in compliance.
Compliance includes accessing audit information, breaking down compliance responsibilities as well as meeting configuration standards. AWS definitely does not provide this, since the business using AWS is responsible for every aspect of provisioning and design.
3) Absent support: Hands-on support is not why a business uses AWS. In fact you can rarely get any support at all. Most enterprises are used to calling a help desk and having someone log in to servers and fix things.
While this lack of support might not deter some usage when internal teams can learn the platform, wholesale adoption is less likely, especially in the case of outages. With new tools that sync AWS environments with the rest of the organization, it is essential to have management and support, providing value in outsourced infrastructure.
There is no doubt that AWS is a powerful platform. Most businesses will likely make use of it. But for the foreseeable little while, as long as SLAs, support, management and compliance remain problematic, more complex and customized dedicated infrastructure providers will continue to be the cloud of choice for the enterprise.
- » Practical cloud considerations: Security and the decryption conundrum
- » The unforgiving cycle of cloud infrastructure costs – and the CAP theorem which drives it
- » How the HR industry has seen cost optimisation with SaaS: Exploring next steps
- » Why the antidote for multi-cloud complexity is a unified management strategy
- » A guide for database as a service providers: How to stand your ground against AWS – or any other cloud