GCP

Your Google Cloud Billing Account needs to be configured to export Billing Data to BigQuery, and the application needs to authenticate with GCP to run queries on that data in BigQuery.

  1. Ensure you have a GCP Service Account with the permission to start BigQuery jobs and read Bigquery job results by granting at least roles/bigquery.dataViewer and roles/bigquery.jobUser to the service account. Learn more about GCP Service Accounts here.

  2. Ensure that your environment is configured to authenticate with Google Cloud as described here.

    • If you do download a service account key, make sure the environment variable GOOGLE_APPLICATION_CREDENTIALS points to the full path of the service account key file. E.g. /Users/<user>/path/to/credential
  3. Set up Google Cloud billing data to export to BigQuery. You can find the instructions for this here.

  4. Configure environment variables for the api and client:

    • After configuring your credentials, we need to set a number of environment variables in the app, so it can authenticate. We use .env files to manage this. Reference packages/api/.env.template for a template .env file. Rename this file as .env, optionally remove the comments and then set the environment variables for the “Billing Data'' approach. If you are only using one of these cloud providers, you can remove the environment variables associated with the other cloud provider in your packages/api/.env file.

    • There is also a packages/client/.env file that allows you to set some configuration for the data range the application requests data for. See packages/client/.env.template for a template. Rename this file as .env, optionally remove the comments and then set the environment variables.

    • By default, the client uses AWS, GCP and Azure. If you are only using one of these cloud providers, please update the appConfig object in the client Config file to only include your provider in the CURRENT_PROVIDERS array.

    • For more details on the GCP specific configuration options and their definitions, please read the Configuration Glossary

  5. Finally, start up the application:

    yarn start

⚠️ This will incur some cost. Use this sparingly if you wish to test with live data.

DISCLAIMER: If your editor of choice is VS Code, we recommend using either your native or custom terminal of choice (i.e. iterm) instead. Unexpected authentication issues have occurred when starting up the server in VS Code terminals.

Unsupported Usage Types#

The application has a file containing supported usage types located here. The current lists consist of types the application has faced, so there are likely to be some types not yet handled. When querying your data, you may come across unsupported types with a warning like this:

2021-03-31T09:48:38.815Z [BillingExportTable] warn: Unsupported Usage unit: Filestore Capacity Standard

If you come across a similar warning message, congratulations! You have found a usage type that the app currently isn’t aware of - this is a great opportunity for you to improve Cloud Carbon Footprint!

The steps to resolve are:

  1. Determine the type in question based on the warning message
  2. Add the type to the respective list in the BillingExportTypes.ts file
  3. Delete estimates.cache.json file and restart the application server
  4. Submit an issue or pull request with the update

Options for Google Authentication#

We currently only support authentication with Google via the GOOGLE_APPLICATION_CREDENTIALS environment variable.

Cloud Carbon Footprint is an open-source project, sponsored by Thoughtworks Inc. under the Apache License, Version 2.0

PRIVACY POLICY