Google Cloud (GCP)¶
Connect one or more GCP projects or a GCP Organization to bring billing, resource inventory, and commitment data into CloudVerse AI.
What you get¶
- Billing data from GCP BigQuery billing export
- Resource inventory across projects, regions, and services
- Committed Use Discount (CUD) coverage and recommendations
- Anomaly detection and budget tracking per project or organization
Prerequisites¶
- GCP project with billing enabled
- BigQuery billing export configured (standard or detailed)
- Service account with the required IAM roles
Connect GCP¶
- Go to Settings > Integrations.
- Select Google Cloud.
- Enter a connection name — for example,
gcp-production. - Complete the Billing Setup step:
- Confirm your BigQuery billing export dataset and project.
- Enter the billing account ID.
- Complete the Authentication step:
- Create a GCP service account.
- Grant the required IAM roles.
- Download and upload the service account JSON key.
- Select the projects or organization scope to include in discovery.
- Finish the flow and wait for initial data ingestion.
Verify the connection¶
- Open the GCP connection detail page in Settings > Integrations.
- Confirm that billing and discovery status indicators are green.
- Open Cost Management > Cost Explorer, filter by Provider: GCP, and confirm data appears.
- Open Cloud Infrastructure > Resources and filter by your GCP project to verify inventory.
Permissions required¶
The GCP service account needs:
roles/bigquery.dataVieweron the BigQuery billing export datasetroles/bigquery.jobUseron the project running the BigQuery jobsroles/viewerat the project or organization scope (for resource inventory)roles/billing.viewerat the billing account scope
Best practices¶
- Enable detailed billing export in BigQuery for full resource-level cost data.
- Connect at the organization level to pull all projects automatically.
- Rotate service account keys on schedule and update them in CloudVerse immediately after.
Troubleshooting¶
- No billing data — Check that BigQuery export is enabled and that the service account has
bigquery.dataVieweron the correct dataset. - Missing projects — Verify the service account has
viewerat the organization or folder level. - Authentication failure — Ensure the service account JSON key is valid and not expired.
See Integration setup issues for more help.