Managed Discounts Connection Process — GCP

Overview

This guide outlines how to connect your Google Cloud environment to the Cloudsaver platform in order to enable Managed Discounts or to validate an offline savings assessment. The steps below ensure a secure connection that provides Cloudsaver with the billing, pricing, and resource metadata required to calculate savings, as well as the necessary permissions to manage your cloud commitment instruments on your behalf.

Important Notes

Purpose of Connection

The GCP connection allows Cloudsaver to securely access billing and commitment data required to deliver Managed Discounts or to validate an offline savings assessment.

Minimal Costs

You may incur minor Google Cloud charges related to BigQuery and Cloud Storage for exporting billing data. These costs are typically minimal and scale with the amount of historical billing data you have.

Validation Time

After setup, Cloudsaver will validate the connection and data before it becomes active within the platform. This process typically takes 1–3 business days.

Connection Process

1. Enable Required APIs

Ensure the following API is enabled in your environment:

• Infrastructure Manager API — allows Google Cloud to execute the deployment required for Managed Discounts configuration.

2. Create the Google APIs Service Agent (Temporary Deployment Account)

The Infrastructure Manager deployment requires a Google-managed service account with elevated permissions during the initial setup. These permissions are temporary and may be removed after deployment is completed.

Assign the following roles to the Google APIs Service Agent:

Project-Level Roles:

• Owner
• Role Administrator

Organization-Level Roles:

• Organization Administrator
• Organization Role Administrator

These roles allow Google Cloud to automatically deploy the IAM configuration and dataset access required for Managed Discounts.

3. Retrieve the Terraform Configuration Source

A service account within the Cloudsaver GCP organization will be granted permissions at the organization level to read necessary metadata and billing information. The Terraform configuration URL will be provided during onboarding.

4. Create the Deployment in Google Cloud Infrastructure Manager

1. Open Infrastructure Manager in the Google Cloud Console
2. Click Create Deployment
3. Provide:
   • Deployment ID: e.g., cloudsaver-mds-deployment
   • Region: any preferred region
   • Service Account: select the Google APIs Service Agent created in Step 2
4. Under Configuration Source:
   • Select GCS
   • Paste the provided Terraform URL

Infrastructure Manager will use this configuration to deploy the IAM and access components required for Managed Discounts.

5. Enter the Required Deployment Inputs

When prompted by Google Infrastructure Manager, enter the following values:

• org_id— Your GCP organization's numeric Organization ID
  Example: 98765189871
  (Do not use your domain name, such as "cloudsaver.com.")
• billing_account_id — Your GCP Billing Account ID, a hex-style identifier
  Example: 01ABCD-FFE3DD-C54321
• billing_project — The Project ID that contains your BigQuery billing export datasets
  Example: cloud-billing-prod
• export_datasets — A list of dataset IDs for billing, pricing, and optional CUD export data
  Format as: ["<dataset-id>", "<dataset-id>"]

These inputs allow the deployment to correctly attach permissions to your billing exports and metadata resources.

6. Complete Deployment & Cloudsaver Verification

Once deployment completes, Infrastructure Manager will have configured:

• IAM roles for reservation, commitment, and metadata visibility
• BigQuery dataset access for billing and pricing exports
• Cloud Storage pathways for secure billing ingestion

Cloudsaver will then:

• Validate access
• Confirm visibility into billing and commitment information
• Notify your team once the environment is fully active

Expected validation time: 1–3 business days