Google Compute Engine Backend Bucket
This page shows how to write Terraform for Compute Engine Backend Bucket and write them securely.
google_compute_backend_bucket (Terraform)
The Backend Bucket in Compute Engine can be configured in Terraform with the resource name google_compute_backend_bucket
. The following sections describe 2 examples of how to use the resource and its parameters.
Example Usage from GitHub
resource "google_compute_backend_bucket" "backend_bucket" {
name = var.backend_bucket_name
bucket_name = var.bucket_name
enable_cdn = true
}
resource "google_compute_backend_bucket" "image-773-cdn" {
bucket_name = google_storage_bucket.app_name-bucket.name
name = "backend-773-bucket"
enable_cdn = true
description = "Contains 773images"
}
Parameters
-
bucket_name
required - string
Cloud Storage bucket name.
-
creation_timestamp
optional computed - string
Creation timestamp in RFC3339 text format.
-
description
optional - string
An optional textual description of the resource; provided by the client when the resource is created.
-
enable_cdn
optional - bool
If true, enable Cloud CDN for this BackendBucket.
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 -
self_link
optional computed - string -
cdn_policy
list block-
signed_url_cache_max_age_sec
optional - number
Maximum number of seconds the response to a signed URL request will be considered fresh. After this time period, the response will be revalidated before being served. When serving responses to signed URL requests, Cloud CDN will internally behave as though all responses from this backend had a "Cache-Control: public, max-age=[TTL]" header, regardless of any existing Cache-Control header. The actual headers served in responses will not be altered.
-
-
timeouts
single block
Explanation in Terraform Registry
Backend buckets allow you to use Google Cloud Storage buckets with HTTP(S) load balancing. An HTTP(S) load balancer can direct traffic to specified URLs to a backend bucket rather than a backend service. It can send requests for static content to a Cloud Storage bucket and requests for dynamic content to a virtual machine instance. To get more information about BackendBucket, 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.
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.
Frequently asked questions
What is Google Compute Engine Backend Bucket?
Google Compute Engine Backend Bucket 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 Backend Bucket?
For Terraform, the zealsoftmedicoadmin/nagendra-terraform-ansible and takehanKosuke/go-gin-init source code examples are useful. See the Terraform Example section for further details.