Google Compute Engine Attached Disk
This page shows how to write Terraform for Compute Engine Attached Disk and write them securely.
The Attached Disk in Compute Engine can be configured in Terraform with the resource name
google_compute_attached_disk. The following sections describe how to use the resource and its parameters.
Example Usage from GitHub
An example could not be found in GitHub.
device_nameoptional computed - string
Specifies a unique device name of your choice that is reflected into the /dev/disk/by-id/google-* tree of a Linux operating system running within the instance. This name can be used to reference the device for mounting, resizing, and so on, from within the instance. If not specified, the server chooses a default device name to apply to this disk, in the form persistent-disks-x, where x is a number assigned by Google Compute Engine.
diskrequired - string
name or self_link of the disk that will be attached.
name or self_link of the compute instance that the disk will be attached to. If the self_link is provided then zone and project are extracted from the self link. If only the name is used then zone and project must be defined as properties on the resource or provider.
modeoptional - string
The mode in which to attach this disk, either READ_WRITE or READ_ONLY. If not specified, the default is to attach the disk in READ_WRITE mode.
projectoptional computed - string
The project that the referenced compute instance is a part of. If instance is referenced by its self_link the project defined in the link will take precedence.
zoneoptional computed - string
The zone that the referenced compute instance is located within. If instance is referenced by its self_link the zone defined in the link will take precedence.
Explanation in Terraform Registry
Persistent disks can be attached to a compute instance using the
attached_disksection within the compute instance configuration. However there may be situations where managing the attached disks via the compute instance config isn't preferable or possible, such as attaching dynamic numbers of disks using the
countvariable. To get more information about attaching disks, see:
- API documentation
- Resource: google_compute_disk
- How-to Guides
- Adding a persistent disk > Note: When using
google_compute_attached_diskyou must use
lifecycle.ignore_changes = ["attached_disk"]on the
google_compute_instanceresource that has the disks attached. Otherwise the two resources will fight for control of the attached disk block.
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.