Customers can design and consume cluster resources as required, deciding how many virtual machines to run inside a cluster. Virtual machines storage policies determine the fault tolerant method of the virtual machine data and the degree of storage capacity consumption. A default resource pool is created at the same level as the management virtual machines resource pool and supports child resource pools.

The customer cloud administrator has full virtual machine and resource pool permission to configure the resource pools to align with their business requirements; they can create, edit, and delete virtual machines. Virtual Machines can be created from scratch or imported from OVF templates.

The Cloud SDDC contains a group of virtual machine folders. By default, Workload VMs are provisioned in the “Workloads” folder.


Live Migration with vMotion allows virtual machines to be migrated while still powered on. If the virtual machine is to be migrated between clusters, a stretched Layer-2 network to be configured, either over VPN or Direct Connect. Please note that the firewall rules must be configured to allow inbound and outbound connectivity with the on-premises vCenter and ESXi hosts.

Virtual Machines provisioned in Cloud SDDC with a hardware version 13 configuration. This can impact hybrid cloud operations if the on-premises SDDC cluster containing hosts running ESXi 6.0 or older. Hybid Cloud Extension can help with migrations of older virtual machines.  For more information on vMotion, see Migrating Virtual Machines.

Content Library

vCenter Content Library is one of the primary means to copy virtual machine content, such as OVA and ISO images, from the on-premises data center to a Cloud SDDC deployment, and maintain the same versions of these files in both places. In addition, it can be used to synchronize these types of files, and also virtual machine templates, among different Cloud SDDCs.

The customer cloud administrator has full permissions to manage the Content Library. The recommended setup during on boarding of VMware Cloud on AWS is to use on-premises Content Library and publish the content to the Cloud SDDC. The Cloud SDDC acts as a subscriber to the on-premises Content Library.  For more information on using Content Library, see Use a Content Library to Import Content into Your SDDC

Hybrid Cloud Extension

Hybrid Cloud Extension, which is an add-on service, enables customers to link on premises environments to VMware Cloud on AWS, to facilitate a hybrid-cloud architecture. Once in place the Hybrid Cloud Extension hybrid interconnect facilitates seamless migration and hybrid scenarios with no retrofit/re-architecture of the source sites.

Hybrid Cloud Extension enables high throughput, secure network extension without the need for NSX on premises, enabling workloads to be moved in bulk and on a schedule, without changing IP or MAC address. It also works with legacy versions of vSphere, thus allowing migration to VMware Cloud on AWS without the need to upgrade the on premises vSphere deployment.  

Disaster Recovery

The VMware Site Recovery service expands and simplifies traditional disaster recovery operations by delivering on-demand site protection across a common, vSphere-based operating environment from on-premises to the cloud. The service protects workloads between on-premises data centers and VMware Cloud on AWS, as well as between different instances of VMware Cloud on AWS.

Built on top of enterprise-grade recovery plan automation (VMware Site Recovery Manager) and native hypervisor-based replication capabilities (vSphere Replication), the service provides an end-to-end disaster recovery solution that reduces the requirements for a secondary DR site, accelerates time to protection, and simplifies DR operations. This service is natively integrated into VMware Cloud on AWS, and provides support for multiple vSphere versions on-premises.

check-circle-line exclamation-circle-line close-line
Scroll to top icon