Google Compute Engine Target SSL Proxy

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

google_compute_target_ssl_proxy (Terraform)

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

Example Usage from GitHub

network-electrs.tf#L64
resource "google_compute_target_ssl_proxy" "mainnet-electrs-tls-proxy" {
  name             = "explorer-mainnet-electrs-tls-proxy"
  backend_service  = data.terraform_remote_state.bitcoin-mainnet.outputs.daemon_backend_service_electrs["bitcoin-mainnet"]
  ssl_certificates = [var.ssl_certs[2]]

  count = local.create_main
network-electrs.tf#L84
resource "google_compute_target_ssl_proxy" "mainnet-electrs-tls-proxy" {
  name             = "explorer-mainnet-electrs-tls-proxy"
  backend_service  = data.terraform_remote_state.bitcoin-mainnet.outputs.daemon_backend_service_electrs["bitcoin-mainnet"]
  ssl_certificates = [var.ssl_certs[2]]

  count = local.create_main
network-electrs.tf#L64
resource "google_compute_target_ssl_proxy" "mainnet-electrs-tls-proxy" {
  name             = "explorer-mainnet-electrs-tls-proxy"
  backend_service  = data.terraform_remote_state.bitcoin-mainnet.outputs.daemon_backend_service_electrs["bitcoin-mainnet"]
  ssl_certificates = [var.ssl_certs[2]]

  count = local.create_main
network-electrs.tf#L64
resource "google_compute_target_ssl_proxy" "mainnet-electrs-tls-proxy" {
  name             = "explorer-mainnet-electrs-tls-proxy"
  backend_service  = data.terraform_remote_state.bitcoin-mainnet.outputs.daemon_backend_service_electrs["bitcoin-mainnet"]
  ssl_certificates = [var.ssl_certs[2]]

  count = local.create_main
network-electrs.tf#L64
resource "google_compute_target_ssl_proxy" "mainnet-electrs-tls-proxy" {
  name             = "explorer-mainnet-electrs-tls-proxy"
  backend_service  = data.terraform_remote_state.bitcoin-mainnet.outputs.daemon_backend_service_electrs["bitcoin-mainnet"]
  ssl_certificates = [var.ssl_certs[2]]

  count = local.create_main

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).

Parameters

A reference to the BackendService resource.

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.

Specifies the type of proxy header to append before sending data to the backend. Default value: "NONE" Possible values: ["NONE", "PROXY_V1"]

The unique identifier for the resource.

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 TargetSslProxy resource. If not set, the TargetSslProxy resource will not have any SSL policy configured.

Explanation in Terraform Registry

Represents a TargetSslProxy resource, which is used by one or more global forwarding rule to route incoming SSL requests to a backend service. To get more information about TargetSslProxy, 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.

risk-label

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.

risk-label

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.

risk-label

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.

risk-label

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.

risk-label

google_compute_ssl_policy

Ensure to use modern TLS protocols

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

risk-label

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.

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 SSL Proxy?

Google Compute Engine Target SSL 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 SSL Proxy?

For Terraform, the PoWx-Org/obtc-esplora, Blockstream/esplora and BlockBucket/Esplora_Docker source code examples are useful. See the Terraform Example section for further details.

security-icon

Automate config file reviews on your commits

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