You can configure one or more CloudHealth integrations, so that you can provide and use public cloud costs for deployments and projects.

You can only create one CloudHealth integration per organization in vRealize Automation.

CloudHealth provides two user roles: Administrator and Power User, which also work with the integration to Cloud Assembly. The user that owns the API key used in creating the integration must belong to the Global organization in CloudHealth to have visibility to all public cloud accounts.

When a CloudHealth integration is created, vRealize Automation creates perspective groups for each public deployment hosted in vRealize Automation.

The perspective is synced every 12 hours to sync any new vRealize Automation deployments with CloudHealth. Once synced, CloudHealth generates the cost for all perspective groups and sends the data to vRealize Automation. For more information on costs for public cloud deployments, see How to view pricing for AWS and Azure.

Prices are synced every 6 hours. You can also sync the perspective and prices on demand by clicking Sync Perspective and Sync Prices from the integration page.

Prerequisites

  • You must have at least one perspective available for reporting in CloudHealth. If you plan to deploy many public cloud deployments, you might need to increase the perspective group limit . By default, CloudHealth has a limit of 200 perspective groups for each perspective. If you plan to have more deployments, contact CloudHealth to request a limit increase.
  • The API key must have:
    • Perspective CRUD Privileges
    • AWS and Azure cost current and history report read privileges

Procedure

  1. Select Infrastructure > Connections > Integrations.
  2. Click Add Integration.
  3. Select CloudHealth.
  4. Enter a name and (optional) description.
  5. Click Display pricing information to enable price syncing from CloudHealth to Cloud Assembly.
  6. Enter the API key of the CloudHealth user and click Validate.
  7. (Optional) Add capability tags. For more information on capability tags, see Using capability tags in vRealize Automation Cloud Assembly.
  8. Click Save.
    The CloudHealth integration is saved.

Results

The CloudHealth integration is created. A vRealize Automation perspective is created in CloudHealth.
Note: Do not attempt to modify or edit the vRealize Automation perspective in CloudHealth.

What to do next

Verify that the integration was created successfully by navigating to a public cloud deployment and clicking Price. If no price is shown, the perspective might not have synced yet. Navigate to the CloudHealth integration and click Sync Perspective and Sync Prices.