As I am based in the UK, I often work with customers based in central London who face a common issue: real estate is expensive. Many of our customers are dealing with space, power or cooling constraints which means they cannot increase the size of their IT infrastructure because of expensive square footage. VMware Cloud on AWS gives them the ability to burst to the Cloud on a temporary basis (giving them time to address the capacity constraints) or permanent basis (making VMC a permanent extension to their D.C.).
A number of our customers want to leverage VMware Cloud on AWS to expand into a new market. As the VMC SDDC can be deployed in a matter of hours, it allows customers to enter a new market without having to commit CAPEX. A side benefit of using VMC for this use case is that, if the market expansion were to fail, customers can exit the market as fast as they entered it (they are not left with racks of hardware).
Many of our customers are using VMware Cloud on AWS as an infrastructure Island. VMC can be used temporarily for projects, development sprint, testing purposes and avoid the need to invest in long-term CAPEX. Once the project is completed, workloads can be migrated back on-prem or simply discarded.
As customers migrate or create virtual machines in VMware Cloud on AWS, they might want to leverage to run services accessible from the Internet, such as web services. We make it very easy to do this in three steps:
In the July 2018 release of VMware Cloud on AWS was introduced Route-based VPN as part of the NSX-T roll-out. Route-Based VPN provides vast improvements from the traditional Policy-Based VPN.