Prerequisites
- GCP project or organization with permissions to create service accounts, IAM roles, and Workload Identity pools
- Google Cloud CLI (
gcloud) installed and authenticated - Access to the Draftt dashboard (Integrations > GCP)
Setup Methods
Draftt supports three installation methods. Workload Identity Federation via CLI is recommended.Workload Identity Federation - CLI (Recommended)
Workload Identity Federation - CLI (Recommended)
Enter GCP project details
Enable necessary APIs
Create a Workload Identity Pool
Add the Draftt AWS Provider to the Pool
339712924365) is Draftt’s production account, which hosts the draftt-fetcher service used to fetch data from your GCP project.Create a GCP Service Account
Grant permissions to the Service Account
Allow AWS Role to act as the GCP Service Account
arn:aws:sts::339712924365:assumed-role/draftt-fetcher) to impersonate the GCP service account:Generate Credentials JSON
Upload the JSON file to Draftt
Workload Identity Federation - UI
Workload Identity Federation - UI
Create a GCP Service Account
- Service account name:
draftt-wif-int-readonly - Service account ID:
draftt-wif-int-readonly - Description:
A read only service account for Draftt integration
ViewerBrowseriam.securityReviewer
Create a Workload Identity Pool
- Pool name:
draftt-wif-integration - Pool ID:
draftt-wif-integration - Description:
Workload Identity Pool for Draftt.io integration
- Provider name:
draftt-wif-aws-integration - Provider ID:
draftt-wif-aws-integration - AWS Account ID:
339712924365
Grant Draftt permissions to impersonate the service account
aws_role attribute name and enter Draftt’s fetcher role:draftt-wif-aws-integration as the provider and download the JSON config file. This file does not include any secrets.Upload the JSON file to Draftt
Service Account Keys
Service Account Keys
Name your integration
Create a GCP Service Account
ViewerBrowseriam.securityReviewer
Generate a JSON key
Upload the JSON file to Draftt
What Draftt Reads
Draftt’s service account is read-only. It cannot create, modify, or delete any resources in your GCP environment. The required roles provide access to resource metadata across compute (Compute Engine, GKE, Cloud Run, Cloud Functions), storage (Cloud Storage, Filestore), databases (Cloud SQL, Spanner, Memorystore), networking (VPC, Load Balancing, Cloud CDN), and security (IAM, Secret Manager, KMS).Verifying Your Connection
After setup, return to Integrations > GCP in Draftt. Each connected project or organization shows a status:- Healthy - All required access is in place. Draftt is collecting data as expected.
- Unhealthy - Something is wrong with the service account or permissions. Verify the WIF configuration and IAM role bindings.
Troubleshooting
WIF authentication fails: Confirm the AWS account ID (339712924365) matches in the provider configuration. Verify the service account email and project number are correct in the credential config.
Missing resources in inventory: Check that the service account has roles/viewer and roles/browser at the correct scope (organization vs. project). New connections may take one scan cycle to fully populate.
API not enabled errors: Ensure both cloudresourcemanager.googleapis.com and iamcredentials.googleapis.com are enabled in your project.