google_ compute_ region_ instance_ group_ manager cost estimation
A regional (multi-zone) managed instance group, billed as the Compute Engine VMs it runs across zones. 3× e2-medium is ~$73/month.
A google_
The regional aspect doesn't change the per-instance price, it distributes the same instances across zones for availability. So the cost mechanics match a zonal MIG: you pay for the VMs, and the autoscaler varies target_
The levers are the standard VM-fleet ones: attach an autoscaler so target_
c3x prices the regional MIG from the template's machine type and target_
Terraform example
A minimal but realistic configuration that C3X can estimate.
resource "google_compute_region_instance_group_manager" "workers" {
name = "regional-worker-mig"
base_instance_name = "worker"
region = "us-central1"
target_size = 3
version {
instance_template = google_compute_instance_template.worker.id
}
distribution_policy_zones = ["us-central1-a", "us-central1-b", "us-central1-c"]
}Pricing dimensions
What you actually pay for when you provision google_.
| Dimension | Unit | What's being charged |
|---|---|---|
| Instances | per instance-hour | target_ $0.0335/instance-hour for e2-medium → 3 instances ≈ $73.37/month |
| Boot disks | per GB-month | Each instance's boot disk bills separately. |
Sample C3X output
Three e2-medium instances across zones (fixed target_size), 24/7:
google_compute_region_instance_group_manager.workers
└─ Instances (e2-medium × 3) 2190 instance-hours $73.37
Monthly $73.37Optimization tips
Common ways to reduce google_ cost without changing the workload.
Attach an autoscaler
Often 30 to 50% on variable loadA regional MIG pinned at a fixed target_
Use Spot VMs in the template for fault-tolerant workers
Up to ~91% on Spot instancesSet the instance template to Spot for stateless workers, 60-91% below on-demand. Regional distribution plus Spot gives both zonal resilience and deep savings for interruptible work.
Right-size machine type and apply CUDs
37 to 55% on the baselineMatch the template's machine type to the workload, and cover the steady baseline with committed-use discounts (1-3 year) for 37-55% off; sustained-use discounts apply automatically on top.
FAQ
How is a regional MIG billed?
As the Compute Engine instances it runs, target_
Does regional cost more than a zonal MIG?
Not per instance, the same VMs at the same rate, just distributed across zones for availability. You pay for target_
How does c3x estimate the cost?
From the instance template's machine type and target_
Related resources
Estimate this resource in your own Terraform
Free, open source, no API key. C3X parses your Terraform and shows line-item cost for every resource, including google_.