Google Cloud Integration
Connect your Google Cloud Platform project to Devpilot to provision and manage Compute Engine instances for your deployments.
Google Cloud Integration
The GCP integration connects your Google Cloud Platform project to a Devpilot workspace. Once connected, Devpilot can provision Compute Engine instances on your behalf, install the Devpilot agent on new servers, and manage their lifecycle.
GCP provisioning is available, but live credential validation is limited — Devpilot does not pre-flight GCP credentials in the same way it does for AWS, Azure, DigitalOcean, or Vultr. If your credentials are wrong the provisioning run itself will fail with the error returned by Google Cloud.
Prerequisites
- A Google Cloud project with billing enabled
- The Compute Engine API enabled for that project
- Permission to create IAM service accounts and keys
- An active Devpilot workspace
Required Credentials
Devpilot stores the following fields for a GCP integration:
| Field | Description |
|---|---|
| Access Key | The service account client email (used as the authentication principal). |
| Secret Key | The private key value from the service account JSON key file. |
| Project ID | The Google Cloud project Devpilot should provision resources in. |
| Region | Default GCP region (for example us-central1, europe-west1). |
Creating a Service Account
Do not use your personal Google account credentials. Create a dedicated service account so you can revoke its key without affecting your own access.
Create the Service Account
In the Google Cloud Console, open IAM & Admin > Service Accounts > Create service account. Name it devpilot-integration and proceed.
Grant Required Roles
On the Grant this service account access to project step, add the Compute Admin role so Devpilot can create and manage Compute Engine resources. Add Service Account User so the service account can attach itself to VMs it creates.
Generate a JSON Key
Open the service account, go to the Keys tab, and select Add key > Create new key > JSON. Download the JSON key file and keep it safe — it cannot be downloaded again.
Enable the Compute Engine API
From APIs & Services > Library, search for Compute Engine API and ensure it is enabled for the project.
Connect GCP in Devpilot
Open Workspace Settings > Integrations and select Connect on the GCP card. Paste the service account's client_email into the Access Key field, the private_key into the Secret Key field, and enter your Project ID and default Region.
What Devpilot Does on GCP
When you provision a server, Devpilot:
- Creates a Compute Engine instance in the chosen project, region, and zone
- Generates an SSH key pair and attaches it to the instance
- Configures the firewall for the ports the deployment needs
- Tags the instance with Devpilot workspace metadata
- Installs the Devpilot agent on the new instance
Testing Credentials
GCP credentials are exercised during provisioning rather than by a separate pre-flight test. If you want to confirm the service account works before creating a server, run a small test deployment and inspect the provisioning log.
Rotating Credentials
Create a new JSON key for the service account in Google Cloud, update the Secret Key value in the Devpilot integration, and then delete the old key from the Google Cloud service account's Keys tab.
Troubleshooting
Provisioning Fails with Permission Errors
- Confirm the service account has Compute Admin and Service Account User on the project.
- Ensure the Compute Engine API is enabled.
- Verify the Project ID in Devpilot matches the project the service account belongs to.
Quota Errors
- Check IAM & Admin > Quotas for the region and machine type you are provisioning into. New GCP projects often have low initial quotas.
Disconnecting GCP
Open the GCP integration and select Remove. Stored credentials are deleted from Devpilot. Compute Engine instances already provisioned through Devpilot remain in your GCP project — manage or delete them from the Google Cloud Console if no longer needed.