Google Compute Engine Disk IAM
This page shows how to write Terraform for Compute Engine Disk IAM and write them securely.
The Disk IAM in Compute Engine can be configured in Terraform with the resource name
google_compute_disk_iam. The following sections describe how to use the resource and its parameters.
Example Usage from GitHub
An example could not be found in GitHub.
The following arguments are supported:
name- (Required) Used to find the parent resource to bind the IAM policy to
zone- (Optional) A reference to the zone where the disk resides. Used to find the parent resource to bind the IAM policy to. If not specified, the value will be parsed from the identifier of the parent resource. If no zone is provided in the parent identifier and no zone is specified, it is taken from the provider configuration.
project- (Optional) The ID of the project in which the resource belongs. If it is not provided, the project will be parsed from the identifier of the parent resource. If no project is provided in the parent identifier and no project is specified, the provider project is used.
member/members- (Required) Identities that will be granted the privilege in
role. Each entry can have one of the following values:
- allUsers: A special identifier that represents anyone who is on the internet; with or without a Google account.
- allAuthenticatedUsers: A special identifier that represents anyone who is authenticated with a Google account or a service account.
- user:[emailid]: An email address that represents a specific Google account. For example, email@example.com or firstname.lastname@example.org.
- serviceAccount:[emailid]: An email address that represents a service account. For example, email@example.com.
- group:[emailid]: An email address that represents a Google group. For example, firstname.lastname@example.org.
- domain:[domain]: A G Suite domain (primary, instead of alias) name that represents all the users of that domain. For example, google.com or example.com.
- projectOwner:projectid: Owners of the given project. For example, "projectOwner:my-example-project"
- projectEditor:projectid: Editors of the given project. For example, "projectEditor:my-example-project"
- projectViewer:projectid: Viewers of the given project. For example, "projectViewer:my-example-project"
role- (Required) The role that should be applied. Only one
google_compute_disk_iam_bindingcan be used per role. Note that custom roles must be of the format
policy_data- (Required only by
google_compute_disk_iam_policy) The policy data generated by a
In addition to the arguments listed above, the following computed attributes are exported:
etag- (Computed) The etag of the IAM policy.
Explanation in Terraform Registry
Three different resources help you manage your IAM policy for Compute Engine Disk. Each of these resources serves a different use case:
google_compute_disk_iam_policy: Authoritative. Sets the IAM policy for the disk and replaces any existing policy already attached.
google_compute_disk_iam_binding: Authoritative for a given role. Updates the IAM policy to grant a role to a list of members. Other roles within the IAM policy for the disk are preserved.
google_compute_disk_iam_member: Non-authoritative. Updates the IAM policy to grant a role to a new member. Other members for the role for the disk are preserved.
google_compute_disk_iam_policycannot be used in conjunction with
google_compute_disk_iam_memberor they will fight over what your policy should be.
google_compute_disk_iam_bindingresources can be used in conjunction with
google_compute_disk_iam_memberresources only if they do not grant privilege to the same role.
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.