google_compute_target_http_proxy cost estimation

A google_compute_target_http_proxy is the glue between a forwarding rule and a URL map in an HTTP load balancer. The forwarding rule points at the proxy, and the proxy references the URL map that routes requests to backend services. The target HTTP proxy is free. There is no charge for the proxy or for the requests it terminates.

Like the URL map and health checks, the proxy is free routing config, not a billed component. The Cloud Load Balancing charge lands on the forwarding rule (hourly plus per-GB data processed) that points at the proxy, and the backends behind the URL map carry the compute and egress. The proxy is a required connector, not a meter.

A cost-relevant design note: a plain HTTP proxy serves unencrypted traffic, which is usually only appropriate behind another TLS terminator or for internal redirects to HTTPS. For public traffic you typically want a target HTTPS proxy, which adds free Google-managed SSL certificates. c3x prices the forwarding rule and backends and treats the target HTTP proxy as the free connector it is.

Terraform example

A minimal but realistic configuration that C3X can estimate.

resource "google_compute_target_http_proxy" "app" {
  name    = "app-http-proxy"
  url_map = google_compute_url_map.app.id
}

Pricing dimensions

What you actually pay for when you provision google_compute_target_http_proxy.

Dimension	Unit	What's being charged
Target HTTP proxy	free	The proxy and the requests it terminates have no charge. $0
Forwarding rule it connects	per hour + per GB	The load balancer charge lands on the forwarding rule pointing at the proxy, plus data processed. ~$0.025/hour per rule + data
Backends behind the URL map	per hour	The VMs or services the proxy's URL map routes to, carrying their own cost.

Optimization tips

Common ways to reduce google_compute_target_http_proxy cost without changing the workload.

Use an HTTP proxy only for redirects

A target HTTP proxy is well suited to redirecting HTTP to HTTPS at the load balancer for free, avoiding a small always-on VM dedicated to redirects.

Prefer HTTPS proxy for public traffic

A target HTTPS proxy adds free Google-managed SSL certificates. There is no cost difference in the proxy, but it avoids running your own TLS termination elsewhere.

Share one proxy and URL map across services

One proxy referencing one URL map can front many backend services, keeping the paid forwarding rule count to one.

FAQ

Does a target HTTP proxy cost money?

No. The target HTTP proxy is free routing config. The Cloud Load Balancing charge lands on the forwarding rule that points at it, plus data processed, and on the backends behind the URL map.

What is the difference between HTTP and HTTPS proxies for cost?

Neither proxy is billed. The HTTPS proxy adds free Google-managed SSL certificates for encrypted traffic; the HTTP proxy is typically used for internal routing or HTTP-to-HTTPS redirects.

How do I estimate the cost around a target HTTP proxy?

Price the forwarding rule (hourly plus data processed) and the backends behind the URL map. c3x does this and treats the proxy, URL map, and health checks as free.