Learn how and why to connect the same VMware Private Cloud to multiple Virtual Private Clouds (VPCs) with Google Cloud VMware Engine
Not too long ago, we wrote about some key new capabilities in Google Cloud VMware Engine. One of the new main innovations we announced was multi-VPC connectivity, or the ability to connect the same VMware Private Cloud (that’s the name we use at Google to describe what VMware calls a Software Defined Datacenter, or SDDC) to multiple Virtual Private Clouds (VPCs) inside a customer’s organization. In today's post, we explore in more detail the benefits and use cases that this feature enables.
Because of this new feature, Google Cloud VMware Engine now supports connecting a Private Cloud to multiple customer VPCs (one-to-many). Previously, this was not possible, as the relationship between a VPC and a Private Cloud was unique (one-to-one).
To move or not to move? Benefits are multifold when you are migrating to the cloud. Get the correct information to make your decision, with our cloud engineering expertise.
Migrating your legacy VMware vSphere environment to Google Cloud VMware Engine can be a quick and easy way to get your systems back into compliance. Retire your tech debt: Move vSphere 5.5+ to Google Cloud VMware Engine.
The latest version of Google Cloud VMware Engine is chock full of new features and integrations, including enhanced networking capabilities. What’s new in Google Cloud VMware Engine in February 2021?
Today, we’re delighted to announce that Google Cloud VMware Engine is now available globally in the Americas, Europe, and Asia Pacific, with the expansion into the europe-west3 (Frankfurt), europe-west2 (London), and asia-northeast1 (Tokyo) regions.
Go deep on private cloud networking for Google Cloud VMware Engine with this whitepaper. In this post, you'll learn about the various connectivity options available in VMware Engine, with detailed explanations of traffic flows, optimization options and architectural design considerations.