Google Compute Engine Disk Resource Policy Attachment

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

google_compute_disk_resource_policy_attachment (Terraform)

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

Example Usage from GitHub
resource "google_compute_disk_resource_policy_attachment" "vm-attached" {
  count = length(var.attached_disks) == 0 ? 0 : length(google_compute_disk.vm)
  name  = google_compute_disk.vm[count.index].labels["vss"] ? :
  disk  = google_compute_disk.vm[count.index].name
  zone  = google_compute_disk.vm[count.index].zone
resource "google_compute_disk_resource_policy_attachment" "attachment_schedule" {
  name =
  disk =
resource "google_compute_disk_resource_policy_attachment" "snapshots" {
  name    = var.policy_name
  disk    = var.disk_name
  project = var.project_id
  zone    =
resource "google_compute_disk_resource_policy_attachment" "this" {
  disk    = var.disk
  name    =
  project = var.project
  zone    =

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


The name of the 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.

  • project optional computed - string
  • zone optional computed - string

A reference to the zone 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 regional disks (google_compute_region_disk). For regional disks, please refer to google_compute_region_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.



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.



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.



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.



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.



Ensure to use modern TLS protocols

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



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

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

For Terraform, the jonathanrboniface/terraform-standards, RouxAntoine/gcp-kube-master-tf and clementous92/ops-terraform-modules-resources2 source code examples are useful. See the Terraform Example section for further details.