Even though public cloud adoption has become mainstream among enterprises, the heavily touted full cloud adoption has not become a reality for many companies, nor will it for quite some time. Instead we see greater adoption of hybrid cloud, a mixture of public and private clouds, as the predominant deployment of IT services. With private cloud deployments largely consisting of market share leader, VMware, it gives even more credence to a VMware Cloud on AWS solution.
Looking back 2 years to when VMware and AWS made the announcement that they had co-engineered a cloud solution, it makes a lot more sense, now. That wasn’t necessarily always the case. I’ll be among the first to admit that I failed to see how the two competitive solutions would coexist in a way that provided value to the customer. But then again, I was fully drinking the cloud punch that said refactoring applications and deploying in a “cattle vs pets” mentality was necessary to enable a full-on digital transformation to merely survive in the evolving aaS world.
What I was not considering was that more than 75% of private clouds were running on VMware. Or that companies had made a significant investment into not only the licensing and tooling, but also in their people, to run VMware. It would not have made sense to move everything to the cloud in many situations.
I viewed it solely as a “lift and shift” opportunity. It provided a means for companies to move their IT infrastructure out of the data center and “check the box” for fully migrating to the cloud while allowing for the gradual adoption of AWS cloud native solutions as they trained staff accordingly.
While it is true that performing a complete data center evacuation is a common request with various factors influencing the decision, delaying cloud native is less of a driver. Some companies are making the decision because they have been unsuccessful in renegotiating their contract with their colo-provider and find themselves in a tough situation resulting in the need to rapidly move or be locked-in for another lengthy contract. In other situations, the CIO has decided that their valuable human capital would be better spent delivering higher value to their company as opposed to running a data center and converting from a CAPEX to OPEX model for their IT infrastructure works better for their business.
However, there are two use cases that seem to be bigger drivers of VMware Cloud on AWS; the need for improved performance and disaster recovery.
Aside from on-demand access to infrastructure, another big advantage of AWS is the sheer number of solutions they have created that become available to use in a matter of minutes and can be easily connected to your applications residing on VMware VMs. With VMware Hybrid Cloud Extension (HCX), moving applications between on-Premises VMware deployments and VMware Cloud on AWS deployments is seamless. This allows your VMs be closer to the dependent AWS tooling to improve latency and may result in improved performance for your users. If you have a geographically disbursed user base, you can easily set up a VMware Cluster in a region much closer, further reducing latency.
I do want to caution, though, that prior to performing a migration of your applications to VMware Cloud on AWS, you should create a dependency map of all your VMs in your on-premises environment. It is necessary to have a thorough understanding of what other VMs your applications are communicating with. We have seen numerous cases where proper identification of dependencies has not occurred, resulting is dissatisfaction when the application is moved to VMware Cloud on AWS but the SAP database remains on-premises. So, while you may have brought the application closer to your users, performance could be impacted if the dependencies are not located nearby.
The other use case that has been gaining adoption is the ability to have a disaster recovery environment. With the severity of natural disasters occurring at what seems like an increased rate, there is a real threat that your business could be impacted with downtime. VMware Cloud on AWS coupled with VMware Site Recovery Manager provides you an opportunity to put in place a business continuity plan in geographically diverse regions to help ensure that your business keeps running.
The other exciting thing is that hybrid cloud no longer has to be located outside your data center. VMware Cloud on AWS has gained such wide spread acceptance that, at AWS re:Invent 2019, VMware announced the opening of a VMware Cloud on AWS Outposts Beta program, which brings the popular features of AWS Cloud right into your data center to work alongside VMware. This seems like it would be best for clients who need the benefits of VMware Cloud on AWS but have some data sovereignty issues or legacy applications that simply cannot migrate to off premise VMware Cloud.
As one of only a handful of North American VMware Partners to possess the VMware Master Services Competency in VMware Cloud on AWS, 2nd Watch has performed numerous successful VMware Cloud on AWS Implementations. We also support AWS Outposts, helping AWS customers overcome challenges that exist due to managing and supporting infrastructures both on-premises and in cloud environments, for a truly consistent hybrid experience.
If you want to understand how VMware Cloud on AWS can further enable your hybrid cloud adoption, schedule a VMware Cloud on AWS Workshop – a 4-hour, complimentary, on-site overview of VMware Cloud on AWS and appropriate use cases – to see if it is right for your business.
-Dusty Simoni, Sr Product Manager