Google Compute Engine Region Target HTTPS Proxy

google_compute_region_target_https_proxy (Terraform)

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

Example Usage from GitHub

jeheyer/network-automation

resource "google_compute_region_target_https_proxy" "REGION_TPROXY_HTTPS" {
  name                  = coalesce(var.name, local.default_name)
  region                = var.region
  url_map               = var.urlmap_id
  ssl_certificates      = var.ssl_certificates
#  ssl_policy            = var.ssl_policy_name

niveklabs/google

resource "google_compute_region_target_https_proxy" "this" {
  description      = var.description
  name             = var.name
  project          = var.project
  region           = var.region
  ssl_certificates = var.ssl_certificates

gilyas/infracost

resource "google_compute_region_target_https_proxy" "default" {
  name             = "proxy"
  ssl_certificates = ["123.123.123.123]"]
  url_map          = "fake"
}

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_id optional computed - number

The unique identifier for the resource.

• region optional computed - string

The Region in which the created target https proxy should reside. If it is not provided, the provider region is used.

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

A list of RegionSslCertificate resources that are used to authenticate connections between users and the load balancer. Currently, exactly one SSL certificate must be specified.

• url_map required - string

A reference to the RegionUrlMap resource that defines the mapping from URL to the RegionBackendService.

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

Explanation in Terraform Registry

Represents a RegionTargetHttpsProxy resource, which is used by one or more forwarding rules to route incoming HTTPS requests to a URL map. To get more information about RegionTargetHttpsProxy, 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.