Google Compute Engine Target HTTPS Proxy

This page shows how to write Terraform for Compute Engine Target HTTPS Proxy and write them securely.

google_compute_target_https_proxy (Terraform)

The Target HTTPS Proxy in Compute Engine can be configured in Terraform with the resource name google_compute_target_https_proxy. The following sections describe 5 examples of how to use the resource and its parameters.

Example Usage from GitHub
resource "google_compute_target_https_proxy" "app-thp" {
  name       = "backend-target-proxy"
  url_map          =
  ssl_certificates = []
resource "google_compute_target_https_proxy" "default" {
  name             = "author-target-proxy"
  url_map          =
  ssl_certificates = values(google_compute_managed_ssl_certificate.default)[*].id
resource "google_compute_target_https_proxy" "this" {
  description      = var.description
  name             =
  project          = var.project
  quic_override    = var.quic_override
  ssl_certificates = var.ssl_certificates
resource "google_compute_target_https_proxy" "TPROXY_HTTPS" {
  name                  = coalesce(, local.default_name)
  url_map               = var.urlmap_id
  ssl_certificates      = var.ssl_certificates
  ssl_policy            = var.ssl_policy_name
resource "google_compute_target_https_proxy" "static" {
  provider         = google
  name             = "static-target-proxy"
  url_map          = google_compute_url_map.static.self_link
  ssl_certificates = [google_compute_managed_ssl_certificate.static.self_link]

Review your Terraform file for Google best practices

Shisho Cloud, our free checker to make sure your Terraform configuration follows best practices, is available (beta).


Creation timestamp in RFC3339 text format.

An optional description of this resource.

  • id optional computed - string
  • name required - string

Name of the resource. Provided by the client when the resource is created. The name must be 1-63 characters long, and comply with RFC1035. Specifically, the name must be 1-63 characters long and match the regular expression 'a-z?' which means the first character must be a lowercase letter, and all following characters must be a dash, lowercase letter, or digit, except the last character, which cannot be a dash.

This field only applies when the forwarding rule that references this target proxy has a loadBalancingScheme set to INTERNAL_SELF_MANAGED.

The unique identifier for the resource.

Specifies the QUIC override policy for this resource. This determines whether the load balancer will attempt to negotiate QUIC with clients or not. Can specify one of NONE, ENABLE, or DISABLE. If NONE is specified, uses the QUIC policy with no user overrides, which is equivalent to DISABLE. Default value: "NONE" Possible values: ["NONE", "ENABLE", "DISABLE"]

A list of SslCertificate resources that are used to authenticate connections between users and the load balancer. At least one SSL certificate must be specified.

A reference to the SslPolicy resource that will be associated with the TargetHttpsProxy resource. If not set, the TargetHttpsProxy resource will not have any SSL policy configured.

A reference to the UrlMap resource that defines the mapping from URL to the BackendService.

Explanation in Terraform Registry

Represents a TargetHttpsProxy resource, which is used by one or more global forwarding rule to route incoming HTTPS requests to a URL map. To get more information about TargetHttpsProxy, see:

Tips: Best Practices for The Other Google Compute Engine Resources

In addition to the google_compute_disk, Google Compute Engine has the other resources that should be configured for security reasons. Please check some examples of those resources and precautions.



Ensure the encryption key for your GCE disk is stored securely

It is better to store the encryption key for your GCE disk securely. Secret Manager could be used instead.



Ensure your VPC firewall blocks unwanted outbound traffic

It is better to block unwanted outbound traffic not to expose resources in the VPC to unwanted attacks.



Ensure appropriate service account is assigned to your GCE instance

It is better to create a custom service account for the instance and assign it.



Ensure OS login for your GCE instances is enabled at project level

It is better to enable OS login for your GCE instances. Enabling OS login ensures that SSH keys used to connect to instances are mapped with IAM users, allowing centralized and automated SSH key management.



Ensure to use modern TLS protocols

It's better to adopt TLS v1.2+ instead of outdated TLS protocols.



Ensure VPC flow logging is enabled

It is better to enable VPC flow logging. VPC flow logging allows us to audit traffic in your network.

Review your Google Compute Engine settings

In addition to the above, there are other security points you should be aware of making sure that your .tf files are protected in Shisho Cloud.

Frequently asked questions

What is Google Compute Engine Target HTTPS Proxy?

Google Compute Engine Target HTTPS Proxy is a resource for Compute Engine of Google Cloud Platform. Settings can be wrote in Terraform.

Where can I find the example code for the Google Compute Engine Target HTTPS Proxy?

For Terraform, the pankajakhade/assignments, ONSdigital/eq-author-terraform-gcp and niveklabs/google source code examples are useful. See the Terraform Example section for further details.


Automate config file reviews on your commits

Fix issues in your infrastructure as code with auto-generated patches.