Google Compute Engine Target HTTPS Proxy

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

pankajakhade/assignments

resource "google_compute_target_https_proxy" "app-thp" {
  name       = "backend-target-proxy"
  url_map          = google_compute_url_map.app-um.id
  ssl_certificates = [data.google_compute_ssl_certificate.my_cert.id]
}

ONSdigital/eq-author-terraform-gcp

resource "google_compute_target_https_proxy" "default" {
  name             = "author-target-proxy"
  url_map          = google_compute_url_map.default.id
  ssl_certificates = values(google_compute_managed_ssl_certificate.default)[*].id

niveklabs/google

resource "google_compute_target_https_proxy" "this" {
  description      = var.description
  name             = var.name
  project          = var.project
  quic_override    = var.quic_override
  ssl_certificates = var.ssl_certificates

jeheyer/network-automation

resource "google_compute_target_https_proxy" "TPROXY_HTTPS" {
  name                  = coalesce(var.name, local.default_name)
  url_map               = var.urlmap_id
  ssl_certificates      = var.ssl_certificates
  ssl_policy            = var.ssl_policy_name
}

karthikrajdev99/terraform_gcp

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]
}

Parameters

• creation_timestamp optional computed - string

Creation timestamp in RFC3339 text format.

• description optional - string

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.

• project optional computed - string
• proxy_bind optional computed - bool

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

• proxy_id optional computed - number

The unique identifier for the resource.

• quic_override optional - string

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"]

• self_link optional computed - string
• ssl_certificates required - list of string

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.

• ssl_policy optional - string

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.

• url_map required - string

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

• timeouts single block
  • create optional - string
  • delete optional - string
  • update optional - string

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:

• API documentation
• How-to Guides
  • Official Documentation

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.

google_compute_disk

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.

google_compute_firewall

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.

google_compute_instance

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.

google_compute_project_metadata

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.

google_compute_ssl_policy

Ensure to use modern TLS protocols

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

google_compute_subnetwork

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.