Known Limitations

Review the following list of feature limitations of
VMware Cloud on AWS Outposts
integration.
  • VMware Cloud on AWS Outposts
    does not support Bill Based Costing.
  • VMware Cloud on AWS Outposts
    does not support configuration maximums. You can ignore the displayed configuration maximums and related alerts.
  • The compliance workflows in
    VMware Aria Operations
    work for the virtual machines running on a
    vCenter Server
    in
    VMware 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 the
    VMware Aria Operations
    cluster configurations in
    VMware Cloud on AWS Outposts
    .
  • Workload optimization for the cross cluster placement within the SDDC with the cluster-based business intent is fully supported with
    VMware 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 the
    vCenter Server
    interface.
  • VMware Cloud on AWS Outposts
    does not support
    VMware Aria Operations
    plugin.
  • You cannot log in to
    VMware Aria Operations
    using your
    vCenter Server
    credentials.
  • Credential-less service discovery is not supported on
    VMware Cloud on AWS Outposts
    .
  • If you have subscribed to both VMC on AWS service and
    VMware Cloud on AWS Outposts
    service, 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 and
    VMware Cloud on AWS Outposts
    services are onboarded for monitoring within
    VMware Aria Operations
    .