Configuring a Google Cloud Account in CloudCheckr CMx

To connect your Google Cloud account to CloudCheckr CMx, you must create and configure a Google Cloud account in the CloudCheckr CMx environment.

This workflow shows you what steps you must perform in CloudCheckr CMx and in your Google Cloud Platform Console to create a successful configuration.


Click the drop-down boxes to review and follow each step in this workflow.

  1. Launch CloudCheckr CMx.
  2. In the Search bar at the top of the screen, type Account Hierarchy.
  3. From the Accounts tab, click the + CREATE button.
  4. Select Account from the fly-out menu. The Create Account sub-drawer opens.
  5. Type a name for your account.
  6. From the Cloud Provider drop-down list, select Google.
  7. From the Location drop-down menu, select an option if you want to place your account within an existing folder.
  8. Click Save.

A service account is a type of account used by an application or a virtual machine (VM) instance—not by an individual user. Identified by its email address, a service account lets you control access to the resources in your Google projects.

  1. In the Google Cloud Platform Console, select IAM & Admin > Service Accounts .
  2. Click Select a Project and choose your project from the list.
  3. Click the Create Service Account button.
  4. Type a name for your service account.
  5. Select a role you wish to grant to your service account.
    CloudCheckr CMx requires read-only access for your environment. We recommend the Project Viewer role.
  6. Click Save.

To use a service account outside of Google Cloud, you must create service account keys as a secure way to establish the identity of the service account.

  1. Return to the Services Account page in the Google Cloud Platform Console.
  2. Follow the instructions in the Creating and Managing Service Account Keys topic.
  3. Make sure to copy your new service account key to a safe location.
  1. From the Accounts tab on the Account Hierarchy page, click
    The Edit Account sub-drawer opens.
  2. Click the Manage Credentials link.
    The Credentials sub-drawer opens.
  3. Drag the service account key you created earlier to the selected area under Import.
  4. Click Close.

As part of your Google Cloud configuration, you will need to export three key Google Cloud billing data points to CloudCheckr CMx:

  • Google Project ID
  • BigQuery Dataset ID
  • BigQuery Table ID
  1. Verify that you have following permissions:
    • Billing Account Administrator role for the selected account
    • BigQuery User role for the Cloud project that contains the BigQuery dataset which stores the Cloud Billing data
  2. Log in to the Google Cloud Platform Console.
  3. Click Select a Project and choose an existing project from the list. You can also create a project.
  4. Select BigQuery.
  5. Follow the instructions in the Export Cloud Billing data to BigQuery topic.
  6. Copy the Project ID, BigQuery Dataset ID, and BigQuery Table ID to a safe and easily accessible location. You will need these values in the final procedure, Step 6: Add Your Google Cloud Billing Data To CloudCheckr CMx.
  1. Return to CloudCheckr CMx.
  2. From the Accounts tab on the Account Hierarchy page, select the CloudCheckr account where you want to add the Google Cloud billing data. The Edit Account sub-drawer opens:
  3. Click the Manage billing data source link.
    The Edit Billing Data Source sub-drawer opens.
  4. Remove any prefixes from the Google Project ID, BigQuery Dataset ID, and BigQuery Table ID: In this example, you would need to remove cumulus-shared-services:
  5. Paste the revised IDs into the appropriate fields. If you do not remove the prefixes from your data or there is any other reason why CloudCheckr CMx cannot process your Google Cloud billing configuration, you will see an error message like this one:
    As per the message, check your credentials and try to save your billing configuration again. If the error persists, contact Support and provide them with your unique Credential ID.
  6. Click Save.

How did we do?