To manage your VMware Cloud on AWS instances in vRealize OperationsvRealize Operations Cloud, 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.

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.
  • For NSX monitoring, include NSX Cloud Admin or NSX Cloud Auditor roles from VMware Cloud on AWS service roles.

Procedure

  1. On the menu, click Administration and in the left pane, click Solutions > Cloud Accounts.
  2. On the Cloud Accounts page, click Add Accounts.
  3. On the Accounts Type 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 instance as you want it to appear in vRealize OperationsvRealize Operations Cloud.
    • Description. Enter any additional information that helps you manage your instances.
  5. To add credentials for the VMware Cloud on AWS instance, click the Add icon, and enter the required credentials.
    • Credential Name. The name by which you are identifying the configured credentials.
    • CSP Refresh Token. A CSP API token. For details on generating an API token, see Generating CSP API Token.
    • Proxy Host. A remote proxy server IP.
    • Proxy Port. The port that is enabled 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.
  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:

    The CSP token is used to access the publicly available VMware Cloud Services Portal API. It is recommended to use the Default Collector Group for this access. If you use a cloud proxy, ensure it has access to the Internet, or if the outbound internet access for the cloud proxy must be restricted, ensure the minimum cloud proxy prerequisites are met. For details, see Configuring Cloud Proxies in vRealize Operations Cloud.

  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. You can monitor the costs of running your VMware Cloud on AWS infrastructure by bringing in the billing from VMware Cloud on AWS to vRealize OperationsvRealize Operations Cloud. To do so, enable the costing option in Advanced Settings.
  10. Click Save.
    The page to configure the SDDC in VMware Cloud on AWS appears.
  11. Click Configure.
  12. Configure the vCenter adapter:
    1. Click the Add icon, 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 the 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 Remote collector. The best practice is to deploy the remote collector/cloud proxy on each SDDC instance of VMware Cloud on AWS.

      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. If you need help with this configuration, contact VMware Support.

    3. Click Next.
  13. By default, the vSAN adapter is enabled.
    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.
    4. Click Next.
  14. By default, the NSX-T adapter is enabled.
    1. Click Validate Connection to validate the connection.
    2. Click Next.
  15. Click Save This SDDC.
    Note: The Service Discovery adapter is optional. The steps to configure the VMware Cloud on AWS 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 account, with the configured SDDC, is added to the list.