Skip to main content

Ripple – GCP Onboarding

How to connect your GCP cost data to Ripple.

Written by Yo Fukuda

Overview

This guide walks you through the steps to connect your GCP billing data to Ripple, including BigQuery setup and dataset sharing with Alphaus.

Before you begin, make sure you have the following information ready:

Billing Account ID
Project ID
Dataset ID
Location

Step 1: Create a New BigQuery Dataset

Create a new dataset in GCP BigQuery. This is where the cost data required for Ripple's aggregation process will be stored.

Note: If you want to use an existing dataset, skip this step and proceed to Step 2.

Fill in the required fields and click Create Dataset.


Step 2: Configure Billing Data Export Settings

Configure the save destination for your billing data.

Specify the Project ID and Dataset ID from Step 1. If you are using an existing dataset, specify that instead.


Step 3: Configure Sharing Settings for Alphaus

​Grant Alphaus access to the dataset so that Ripple can perform aggregation using your GCP billing data.

  1. Click Share Dataset — a settings panel will appear

  2. In the Add Member field, enter the following Alphaus service account:

    1. gcpimportd@alphaus-gcpbatch.iam.gserviceaccount.com
  3. Under Select Role, choose BigQuery Data Viewer

  4. Click Save to apply the settings

This completes the GCP configuration.


Step 4: Register a Billing Account in Ripple

​Add your GCP billing account in Ripple.

  1. Navigate to Preferences > Payer Account Setting > + Add payer account

  2. From the GCP Billing Dashboard > retrieve the Billing account ID. Enter your Billing Account ID to the pop up box in Ripple

  3. Enter any name of your choice in the Account Name field



Step 5: Register Dataset Information

Register your dataset details via the Register / Change Dataset menu.

Enter the following information as shown on screen:

  • Project ID

  • Dataset ID

  • Location


Need More Help?

If any errors occur during the process or if you have any questions, please reach out to us:

Did this answer your question?