google_ cost estimation
A global forwarding rule is where the global Cloud Load Balancing charge lands. It bills an hourly rate per rule plus per-GB data processed, in front of a global HTTP(S) or proxy load balancer.
A google_
The charge is an hourly rate per forwarding rule plus a per-GB data-processing charge on traffic through the load balancer. The global product uses Google's premium network by default, so egress from the load balancer to clients is billed at premium-tier internet egress rates on top of the data-processing charge. A single global anycast IP serving many regions is one forwarding rule, which keeps the hourly component low relative to the reach it provides.
The other costs are the backends (VMs, serverless NEGs, or buckets) and any Cloud CDN enabled on a backend service. c3x prices the global forwarding rule's hourly and data-processing charges, the egress at the applicable network tier, and the backends, and treats the target proxy, URL map, and health checks as the free routing config they are.
Terraform example
A minimal but realistic configuration that C3X can estimate.
resource "google_compute_global_forwarding_rule" "app" {
name = "app-gfr"
load_balancing_scheme = "EXTERNAL_MANAGED"
port_range = "443"
target = google_compute_target_https_proxy.app.id
ip_address = google_compute_global_address.app.address
}Pricing dimensions
What you actually pay for when you provision google_.
| Dimension | Unit | What's being charged |
|---|---|---|
| Global forwarding rule (hourly) | per hour | An hourly charge per global forwarding rule, prorated to the second, regardless of traffic. ~$0.025/hour per rule |
| Data processed | per GB | Per-GB charge on data the global load balancer processes. ~$0.008-$0.012/GB |
| Internet egress (Premium tier) | per GB | Traffic from the load balancer to clients, billed at premium-tier egress rates by default. ~$0.12/GB (Premium tier) |
| Backends | per hour | The VMs, serverless services, or buckets behind the load balancer, which carry their own cost. |
Optimization tips
Common ways to reduce google_ cost without changing the workload.
Serve many regions through one global rule
One hourly charge for global reachA single global anycast IP and forwarding rule fronts backends worldwide, so you pay one hourly charge rather than a regional load balancer per region.
Enable Cloud CDN to cut egress
Offloads repeat traffic to cacheFor cacheable content, Cloud CDN on the backend service serves from edge caches and reduces both data processed and origin egress on the global load balancer.
Delete unused global rules
A global forwarding rule bills hourly whether or not it serves traffic. Removing rules for retired endpoints stops an open-ended charge.
FAQ
Does a global forwarding rule cost money?
Yes. It is where the global Cloud Load Balancing charge lands: an hourly rate per rule plus per-GB data processed, with premium-tier egress on traffic to clients. The proxy and URL map are free.
What is the difference from a regional forwarding rule for cost?
The billing model is the same (hourly per rule plus data processed), but the global rule fronts a global anycast load balancer and adds premium-tier internet egress to clients across regions.
How do I estimate a global HTTP(S) load balancer bill?
Price the global forwarding rule's hourly charge, the data processed per GB, the internet egress at premium tier, and the backends. c3x prices these and treats the proxy, URL map, and health checks as free.
Related resources
google_The free routing target the global rule reaches through a proxy and URL map.
google_The regional load balancer equivalent.
google_The VM backends behind the load balancer that carry the compute cost.
More Google Cloud 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_.