Documentation and Best Practices

Learn how to use Cloudability and get the most out of our cloud cost management tool.

Setup Overview Guide - Billing

Introduction and Layout

The purpose of this guide is to help walk you through the process of credentialing your organization's billing account so that Cloudability can start ingesting your Google Cloud Platform (GCP) billing data. If your organization has multiple GCP billing accounts, then this process must be repeated for each of those billing accounts.

3. Select Keep if your browser prompts you with a warning when downloading the shell script

Run Script

Follow the steps below to run the script via Cloud Shell within your cloud console. It does not matter from where, within the Cloud Shell, you run the script so long as you have the permissions listed in IAM Permissions.

If the script is successful, you will see output similar to the following in your Cloud Shell,

Verify Credentials

1. Click Verify Credentials.

2. Your billing account is added and a green balloon notifies you of success.

3. Click the refresh icon to update status.

4. The green check mark indicates that this billing account has been successfully credentialed.

Conclusion

You have now successfully added your billing account to Cloudability. We ingest data at regular intervals and your billing data will be available starting from the next ingest cycle. Upon the next ingest, we will also enumerate the projects associated with this billing account; return to the GCP credentials page to see the list of projects linked to the billing account.

Lastly, if your organization has additional GCP billing accounts that you would like to add then please repeat this process for each of those billing accounts.

Troubleshooting Script Errors

1. ERROR: (gcloud.iam.roles.create) FAILED_PRECONDITION: You can't create a role with role_id (CloudabilityRole_Billing) where there is an existing role with that role_id in a deleted state.

Context: This can occur when you run the script after deleting an existing role, from your billing project, with role_id CloudabilityRole_Billing. The role could be in a deleted state and the script cannot create a new role with that role_id. You can view the role's status -- Enabled, Disabled, Deleted -- in your cloud console.

Solution: Undelete the existing role with role_id CloudabilityRole_Billing, from your billing project, and re-run the script.

2. ERROR: (gcloud.iam.roles.create) Resource in project is the subject of a conflict.

Context: This can occur when you have an existing role, within your billing project, with role_id CloudabilityRole_Billing. The error indicates that the script is unable to create a new role with role_id CloudabilityRole_Billing because one already exists.