To manage your VMware Cloud on AWS Outposts instances in vRealize Operations, you must configure a cloud account. The adapter requires the CSP API token that is used to authorize and communicate with the target VMware Cloud on AWS Outposts.

Prerequisites

Navigate to API Tokens under My Account and generate a CSP API token based on your operational needs:

  • To discover and manage SDDCs, include Administrator (Delete Restricted) or Administrator from VMWare Cloud on AWS service roles.
  • For data collection of bills, include either Billing Read-only or Organization Owner roles from All Organization Roles.
    Note: The data collection of bills requires the bills to be available in the CSP.
  • For NSX monitoring, include NSX Cloud Admin or NSX Cloud Auditor roles from VMWare Cloud on AWS service roles.
  • To activate the cost calculations based on VMware Cloud on AWS Outposts pricing, you must modify the VMware Cloud on AWS Outposts rate card on the Cloud Providers tab in the Cost Settings page. For details on updating the rate card, see the VMware KB article KB88488.
  • 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 vRealize Operations.

Procedure

  1. From the left menu, click Data Sources > Integrations.
  2. On the Accounts tab, click Add Account.
  3. On the Accounts Types page, click VMware Cloud on AWS.
  4. Enter a display name and description for the cloud account.
    • Name. Enter the name for the VMware Cloud on AWS Outposts instance as you want it to appear in vRealize Operations.
    • Description. Enter any additional information that helps you manage your instances.
  5. To add credentials for the VMware Cloud on AWS Outposts instance, click the Add icon, and enter the required credentials.
    Note: Enter the following details if you are using proxy server to access internet or public services.
    • Proxy Host. A remote proxy server IP.
    • Proxy Port. The port that is available on a remote proxy server.
    • Proxy username. Enter the username of the proxy server or if you want to add a domain configured remote proxy server, then enter the username as username@domain name.
    • Proxy Password. Password for the proxy server username.
    • Proxy Domain. The domain has to be empty while using the proxy with domain configuration.
    Note: The proxy credentials will be used by NSX-T adapters.
  6. Determine which vRealize Operations collector or collector group is used to manage the cloud account. If you have multiple collectors or collector groups in your environment, and you want to distribute the workload to optimize performance, select the collector or collector group to manage the adapter processes for this instance.
    Note:

    Ensure that you have Internet connectivity for the collectors to work.

  7. Organization ID. Click Get Organization to auto-fill this field. If you are offline or if you are unable to get the Organization ID, you can enter it manually.

    The Organization ID refers to the Long Organization ID in the Cloud Service Portal. To obtain this ID in the Cloud Service Portal, click Organization Settings > View Organization.

  8. Click Validate Connection to validate the connection.
  9. Bill-based costing is not supported in VMware Cloud on AWS Outposts. In the advanced settings, set "Billing Enabled" field to false
  10. Click Save.
    The page to configure the SDDC in VMware Cloud on AWS Outposts appears.
  11. From the list of available SDDCs in VMware Cloud on AWS Outposts, click any one of the SDDCs that you want to monitor from vRealize Operations.
  12. Configure the vCenter adapter:
    1. Click the vCenter tab, and enter the required credentials.
      • Credential Name. The name by which you are identifying the configured credentials.
      • User Name. The vCenter user name. Use a user with the 'cloudadmin' role which has full visibility to vCenter. Users with less privileges have limited visibility, for example, the read-only users do not have visibility into management VMs.
      • Password. The vCenter password configured for that vCenter user name.
    2. Select the required collector group.
      Note:

      If you have direct connectivity with your VMware Cloud vCenter Server, select Default collector group. If you are using a private IP for your vCenter Server or if you want to deploy telegraf agents for application monitoring, select Cloud Proxy. The best practice is to deploy the Cloud Proxy on each SDDC instance of VMware Cloud on AWS Outposts.

      Select the Cloud Proxy deployed on the given VC and ensure it has access to the Internet. If the outbound internet access for the Cloud proxy must be restricted, ensure that the minimum Cloud Proxy prerequisites are met.

      For details, see "Configuring Cloud Proxies in vRealize Operations" topic in VMware vRealize Operations vApp Deployment and Configuration Guide.

      It is advised not to use the default collector groups as the VMware Cloud on AWS Outposts management gateway firewall rule does not allow traffic originating from any address.

      If you have configured an HTTP proxy on your vRealize Operations cloud proxy, ensure that your HTTP proxy has an exception to access the NSX Management Policy endpoint.

    3. If you have installed cloud proxy in VMware Cloud on AWS Outposts SDDC, the cloud proxy might not have outbound internet access to reach the vRealize Operations service. To activate outbound internet access for the deployed cloud proxy and allow cloud proxy to connect to vCenter, perform the following steps:
      • Request a new public IP in the VMware Cloud on AWS Outposts SDDC where the cloud proxy was deployed. For details, see Request or Release a Public IP Address.
      • Add a new NAT rule for the internet that associates private IP of the cloud proxy with the public IP. For details, see Create or Modify NAT Rules.
      • Add a firewall rule that allows incoming traffic from the public IP that was associated with cloud proxy VM in earlier step to vCenter.
  13. Click the vSAN tab. By default, the vSAN adapter is activated.
    1. Select Use alternate credentials to add alternate credentials. Click the plus icon, and enter the credential name, vCenter username, and password, and click Ok.
    2. Select Enable SMART data collection, if required.
    3. Click Validate Connection to validate the connection.
  14. Click the NSX-T tab. By default, the NSX-T adapter is activated.
    1. Click Validate Connection to validate the connection. If you have hardened the SDDC environment, then you may get an error while validating the NSX-T connection. To resolve this issue, change NSX-T adapter instance to use the private IP address of NSX-T manager by following the steps below:
      1. Navigate to Environment > Inventory > Adapter Instances > NSX-T Adapter Instance and click your NSX-T adapter instance.
      2. In the list of objects shown, edit the object of type NSX-T adapter instance and enter the private IP address of NSX-T manager for your environment in the Virtual IP/NSX-T Manager field.
      3. Click OK.
  15. Click Save This SDDC.
    Note: The Service Discovery adapter is optional. The steps to configure the VMware Cloud on AWS Outposts Service Discovery adapter are similar to configuring vCenter Service Discovery. For more information about configuring the vCenter Service Discovery. see Configure Service Discovery.
    The VMware Cloud on AWS Outposts account, with the configured SDDC, is added to the list.