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.
For Government Cloud Endpoint, after you restart or upgrade the cloud proxy, collector VM, or master/data node, you must manually change the configuration files to point to the government cloud endpoints for VMware Cloud on AWS and CSP. The vCenter adapter, vSAN adapter, and Service Discovery continue to function and collect data from the vCenter environment. However, the NSX-T and VMware Cloud adapters stop collecting data until the VMware Cloud and NSX-T configuration files have been changed to use the VMware Cloud on AWS government cloud endpoints. For details, refer to the Prerequisites section in the Configuring VMware Cloud on AWS Government Cloud Endpoint in vRealize Operations topic.
For Government Cloud Endpoint, bill-based costing is not supported, the costing defaults to rate card based costing.
Known limitations of monitoring a commercial VMC on an AWS endpoint also apply to VMC on an AWS government Cloud endpoint. For a full list of known limitations, see Commercial VMC on AWS Endpoint Known Limitations.
