GCP Integration Setup
Beta Program – Request Access
GCP integration is currently in beta testing. We’re working with select customers to refine the experience before general availability.
What Beta Means:
- ✅ Fully functional scripts and automation
- ✅ Multi-billing account support
- ✅ Technical support available
- ⚠️ Configuration may change based on feedback
- ⚠️ Uses UAT environment during beta period
Request Access
Contact [email protected] or your Tailpipe Account Manager.
Estimated General Availability: Q1 2026
GCP Integration Setup
Automated Infrastructure Deployment for GCP
Connect your GCP billing accounts to Tailpipe using our automated setup script. Supports multiple billing accounts exporting to a single BigQuery dataset.
What Gets Created
Our setup script automatically provisions:
Storage Account – Stores your Azure cost export data
Cost Management Exports – Daily cost and usage data
Azure Policy (Policy method) – Automatic deployment and compliance
Automation Account (Runbook method) – Scheduled execution engine
Managed Identity – Secure, keyless authentication
Note: Due to GCP API limitations, you’ll need to manually configure the billing export in the Cloud Console (we provide step-by-step instructions).
Multi-Billing Account Support
A single project can consolidate billing data from multiple billing accounts. This simplifies management and reduces costs.
- Each billing account creates uniquely named tables in the same dataset
- Interactive selector during setup
- Support for organizations with multiple billing structures
Estimated Time to Setup
Single Billing Account: 10-15 minutes (including manual billing export step)
Multiple Billing Accounts: 15-25 minutes
Security and Privacy
Tailpipe ensures that your data is protected at all times.
- Read-Only Access – Cannot modify any GCP resources
- Workload Identity Federation – No service account keys required
- Keyless Authentication – Short-lived tokens (1 hour), auto-rotated
- Least Privilege – Minimal permissions required
- Audit Trail – All access logged in Cloud Audit Logs
- You Stay in Control – Remove access anytime with our cleanup script
Prerequisites
Before you begin, ensure you have:
- gcloud CLI installed and configured (Installation Guide)
- A GCP account with Billing Account Administrator role
- Project Creator role (or existing project)
Quick Start
1. Download the Setup Script
# Clone the repository
git clone https://github.com/tivarri/tailpipe-cloud-data-export.git
cd tailpipe-cloud-data-export/gcp
2. Run the Setup Script
# Interactive mode (recommended)
./setup-tailpipe.sh
# Or automated mode
PROJECT_ID=tailpipe-export \
BILLING_ACCOUNT=123456-789ABC-DEF012 \
REGION=us-central1 \
./setup-tailpipe.sh
# Preview changes first (dry-run)
DRY_RUN=1 ./setup-tailpipe.sh
3. Configure Billing Export (Manual Step)
The script provides detailed instructions for configuring the billing export in the Google Cloud Console. This takes 2-3 minutes and is a one-time setup per billing account.
4. Share Configuration with Tailpipe
The script outputs a JSON configuration containing your service account details and BigQuery dataset information. Share this with your Tailpipe account manager.
What Happens Next?
- 1. GCP begins streaming billing data to BigQuery (near real-time).
- 2. Tailpipe connects using Workload Identity Federation.
- 3. Your carbon emissions data appears in Tailpipe within 24-48 hours.
Resources
- Complete Setup Guide – Detailed documentation with troubleshooting
- Architecture Overview – GCP architecture and features
- Setup Script – Main automation script
- Cleanup Script – Remove all resources
Need Help?
Contact our support team at [email protected] or consult our Troubleshooting Guide.
Ready to Get Started?
Connect your cloud accounts to Tailpipe and start tracking carbon emissions today: Get Started with AWS | Get Started with Azure | Get Started with GCP
Questions? Contact our team at [email protected]
