unknown

GCP doesn't offer a native hard spending cap — budget alerts notify but don't act. This guide walks through building an automated billing kill switch using Terraform, Cloud Functions (Gen 2), Pub/Sub, and Eventarc. When spend crosses a configurable threshold, a Python Cloud Function calls the Cloud Billing API to detach the billing account, stopping all paid services cold. The full stack is ~200 lines of Terraform and ~50 lines of Python, deployable across multiple dev/sandbox projects via tfvars. Key implementation details include IAM setup for billing-account-level permissions, a dry-run mode for safe testing, deduplication of budget threshold rules, and a deliberate no-retry policy. The approach is explicitly recommended only for dev, sandbox, and PoC environments — not production.

GCP Billing Kill Switch Terraform (Stop Cloud Costs Fast)

Divyansh

We ran into a real issue.

A GCP PoC (GKE + Cloud SQL) kept running and the bill crossed $1200.

Problem: Budget alerts only notify — they don’t stop anything.

So we built a Terraform-based billing kill switch.

Curious — how do you control

We ran into a real issue.

A GCP PoC (GKE + Cloud SQL) kept running and the bill crossed $1200.

Problem: Budget alerts only notify — they don’t stop anything.

So we built a Terraform-based billing kill switch.

Curious — how do you control

Full guide with setup:
<a href="https://www.kubeblogs.com/gcp-billing-kill-switch-terraform/" target="_blank" rel="noopener nofollow">https://www.kubeblogs.com/gcp-billing-kill-switch-terraform/</a>