Review the following list of feature limitations of VMware Cloud on AWS integration.

  • Setting the Costing Enabled option to true, collects VMware Cloud on AWS bills. The cost collection depends on the invoice generation. For instances, where the invoices are not generated, contact the VMware on Cloud for AWS support.
  • vRealize Operations Manager does not calculate the datacenter, cluster, or VM costs for VMware on AWS SDDCs even if the bills are being collected. Cost drivers also cannot be configured for VMware Cloud on AWS.
  • The cloudadmin@vmc.local user in VMware Cloud has limited privileges. In-guest memory collection using VMware tools is not supported with virtual machines on VMware Cloud. Active and consumed memory utilizations continue to work in this case.
  • The compliance workflows in vRealize Operations work for virtual machines running on a vCenter Server in VMware Cloud on AWS. The compliance checks for VMware management objects such Hosts, vCenter, and so on, are not available.
  • Workload optimization including pDRS and host-based business intent does not work because VMware manages cluster configurations.
  • Workload optimization for the cross cluster placement within the SDDC with the cluster-based business intent is fully supported with vRealize Operations Manager 8.0 onwards. However, workload optimization is not aware of resource pools and places the virtual machines at the cluster level. A user can manually correct this in the vCenter Server interface.
  • VMware Cloud does not support vRealize Operations Manager plugin.
  • You cannot log in to vRealize Operations Manager using your VMware Cloud vCenter Server credentials.