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

  • If a cluster is renamed in VMware Cloud on AWS, and as a result of renaming the cluster, if the management resource pool names change in VMware Cloud on AWS, then the following limitations are seen in vRealize Operations:
    • The view, "VMC Management Resource Pool" and the dashboard, "VMC Management VM Monitoring" excludes the management resource pool objects from the cluster that was renamed. As a workaround, update the filter definition for the view "VMC Management Resource Pool" to use a "contains" constraint instead of an "is" constraint for the name attribute that matches the value of "Mgmt-ResourcePool".
    • Jobs that are run through Automation Central will include the VMware Cloud on AWS management VMs instead of excluding them. Use caution with jobs as they may cause interruptions in the management VM functionality in VMware Cloud on AWS.
  • The compliance workflows in vRealize Operations work for the 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 do not work because of the VMware managers cluster configurations.
  • Workload optimization for the cross cluster placement within the SDDC with the cluster-based business intent is fully supported with vRealize Operations. 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 plugin.
  • You cannot log in to vRealize Operations using your VMware Cloud vCenter Server credentials.
  • Credential-less service discovery is not supported on VMware Cloud on AWS.