Google Compute Engine Backend Service Signed URL Key

google_compute_backend_service_signed_url_key (Terraform)

The Backend Service Signed URL Key in Compute Engine can be configured in Terraform with the resource name google_compute_backend_service_signed_url_key. The following sections describe how to use the resource and its parameters.

Example Usage from GitHub

An example could not be found in GitHub.

Parameters

• backend_service required - string

The backend service this signed URL key belongs.

• id optional computed - string
• key_value required - string

128-bit key value used for signing the URL. The key value must be a valid RFC 4648 Section 5 base64url encoded string.

• name required - string

Name of the signed URL key.

• project optional computed - string
• timeouts single block
  • create optional - string
  • delete optional - string

Explanation in Terraform Registry

A key for signing Cloud CDN signed URLs for Backend Services. To get more information about BackendServiceSignedUrlKey, see:

• API documentation
• How-to Guides
  • Using Signed URLs

    Warning: All arguments including key_value will be stored in the raw state as plain-text. Read more about sensitive data in state.

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.