Your VMware Cloud on AWS SDDC provides all the tools you need to, you deploy, configure, and customize VMware virtual machines (VMs).
Because it is a service, VMware Cloud on AWS imposes a few constraints on VM operations, especially those that require you to have physical access to the host hardware or root access to the host operating system. But with a few exceptions (which we point out in this document), on-premises operations described in vSphere Virtual Machine Administration work the same way in your VMware Cloud on AWS SDDC.
|Introduction to vSphere Virtual Machines||
|Deploying Virtual Machines||Step-by-step instructions for creating VMs. You have many options, including:
|Using Content Libraries||Content libraries are container objects for VM and vApp templates and other types of files, such as ISO images, text files, and so on. You can use the templates in the library to deploy virtual machines and vApps in the vSphere inventory. You can also use content libraries to share content between your on-premises infrastructure and your SDDC.|
|Configuring Virtual Machine Hardware||Detailed information about the options for configuring different hardware options, such as CPU, memory, and devices. You can modify existing virtual devices or add new devices, though as we've noted some constraints may apply in VMware Cloud on AWS compared to what you can do in your on-premises vCenter environment.|
|Configuring Virtual Machine Options||Explains VM options and how to change them.
|Customizing Virtual Machines||Instructions for performing post-deployment customization tasks, including:
|Managing the VMware Remote Console Proxy Configuration||VMware Remote Console proxy for vSphere (VMRC proxy) is a service in the SDDC vCenter Server system that simplifies the establishment of VMRC connections to workload VMs.|