Known Limitations
Review the following list of feature limitations of
VMware Cloud on AWS
Outposts
integration. - VMware Cloud on AWS Outpostsdoes not support Bill Based Costing.
- VMware Cloud on AWS Outpostsdoes not support configuration maximums. You can ignore the displayed configuration maximums and related alerts.
- The compliance workflows inVMware Aria Operationswork for the virtual machines running on avCenter ServerinVMware Cloud on AWS Outposts. 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 theVMware Aria Operationscluster configurations inVMware Cloud on AWS Outposts.
- Workload optimization for the cross cluster placement within the SDDC with the cluster-based business intent is fully supported withVMware Aria 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 thevCenter Serverinterface.
- VMware Cloud on AWS Outpostsdoes not supportVMware Aria Operationsplugin.
- You cannot log in toVMware Aria Operationsusing yourvCenter Servercredentials.
- Credential-less service discovery is not supported onVMware Cloud on AWS Outposts.
- If you have subscribed to both VMC on AWS service andVMware Cloud on AWS Outpostsservice, ensure that they are in different CSP organizations. Otherwise, certain functionalities such as costing, and configuration maximums may not function as expected when both VMC on AWS service andVMware Cloud on AWS Outpostsservices are onboarded for monitoring withinVMware Aria Operations.