Google Compute Engine Region Disk Resource Policy Attachment

This page shows how to write Terraform for Compute Engine Region Disk Resource Policy Attachment and write them securely.

google_compute_region_disk_resource_policy_attachment (Terraform)

The Region Disk Resource Policy Attachment in Compute Engine can be configured in Terraform with the resource name google_compute_region_disk_resource_policy_attachment. The following sections describe 2 examples of how to use the resource and its parameters.

Example Usage from GitHub

main.tf#L7
resource "google_compute_region_disk_resource_policy_attachment" "this" {
  disk    = var.disk
  name    = var.name
  project = var.project
  region  = var.region

resource_policy.tf#L74
resource "google_compute_region_disk_resource_policy_attachment" "backup" {
  provider = google-beta
  count    = var.resource_policy_enabled && var.regional_disks ? var.replicas : 0

  name   = google_compute_resource_policy.backup[0].name
  disk   = google_compute_region_disk.disk[count.index].name

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

The name of the regional disk in which the resource policies are attached to.

  • id optional computed - string
  • name required - string

The resource policy to be attached to the disk for scheduling snapshot creation. Do not specify the self link.

A reference to the region where the disk resides.

Explanation in Terraform Registry

Adds existing resource policies to a disk. You can only add one policy which will be applied to this disk for scheduling snapshot creation.

Note: This resource does not support zonal disks (google_compute_disk). For zonal disks, please refer to google_compute_disk_resource_policy_attachment

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 Region Disk Resource Policy Attachment?

Google Compute Engine Region Disk Resource Policy Attachment 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 Region Disk Resource Policy Attachment?

For Terraform, the niveklabs/google and basisai/terraform-google-sts-csi-disks source code examples are useful. See the Terraform Example section for further details.