Google Cloud Platform Project IAM
This page shows how to write Terraform for Cloud Platform Project IAM and write them securely.
The Project IAM in Cloud Platform can be configured in Terraform with the resource name
google_project_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:
member/members- (Required except for google_project_iam_audit_config) Identities that will be granted the privilege in
role. Each entry can have one of the following values:
- user:[emailid]: An email address that represents a specific Google account. For example, firstname.lastname@example.org or email@example.com.
- serviceAccount:[emailid]: An email address that represents a service account. For example, firstname.lastname@example.org.
- group:[emailid]: An email address that represents a Google group. For example, email@example.com.
- 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.
role- (Required except for google_project_iam_audit_config) The role that should be applied. Only one
google_project_iam_bindingcan be used per role. Note that custom roles must be of the format
policy_data- (Required only by
google_iam_policydata source that represents the IAM policy that will be applied to the project. The policy will be merged with any existing policy applied to the project.
Changing this updates the policy.
Deleting this removes all policies from the project, locking out users without organization-level access.
project- (Required) The project id of the target project. This is not inferred from the provider.
service- (Required only by google_project_iam_audit_config) Service which will be enabled for audit logging. The special value
allServicescovers all services. Note that if there are google_project_iam_audit_config resources covering both
allServicesand a specific service then the union of the two AuditConfigs is used for that service: the
log_typesspecified in each
audit_log_configare enabled, and the
audit_log_config- (Required only by google_project_iam_audit_config) The configuration for logging of each type of permission. This can be specified multiple times. Structure is documented below.
audit_log_config block supports:
log_type- (Required) Permission type for which logging is to be configured. Must be one of
exempted_members- (Optional) Identities that do not cause logging for this type of permission. The format is the same as that for
condition block supports:
expression- (Required) Textual representation of an expression in Common Expression Language syntax.
title- (Required) A title for the expression, i.e. a short string describing its purpose.
description- (Optional) An optional description of the expression. This is a longer text which describes the expression, e.g. when hovered over it in a UI.
Warning: Terraform considers the
roleand condition contents (
expression) as the identifier for the binding. This means that if any part of the condition is changed out-of-band, Terraform will consider it to be an entirely different resource and will treat it as such.
In addition to the arguments listed above, the following computed attributes are exported:
etag- (Computed) The etag of the project's IAM policy.
Explanation in Terraform Registry
Four different resources help you manage your IAM policy for a project. Each of these resources serves a different use case:
google_project_iam_policy: Authoritative. Sets the IAM policy for the project and replaces any existing policy already attached.
google_project_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 project are preserved.
google_project_iam_member: Non-authoritative. Updates the IAM policy to grant a role to a new member. Other members for the role for the project are preserved.
google_project_iam_audit_config: Authoritative for a given service. Updates the IAM policy to enable audit logging for the given service.
google_project_iam_policycannot be used in conjunction with
google_project_iam_audit_configor they will fight over what your policy should be.
google_project_iam_bindingresources can be used in conjunction with
google_project_iam_memberresources only if they do not grant privilege to the same role.
Note: The underlying API method
projects.setIamPolicyhas a lot of constraints which are documented here. In addition to these constraints, IAM Conditions cannot be used with Basic Roles such as Owner. Violating these constraints will result in the API returning 400 error code so please review these if you encounter errors with this resource.
Tips: Best Practices for The Other Google Cloud Platform Resources
In addition to the google_project, Google Cloud Platform has the other resources that should be configured for security reasons. Please check some examples of those resources and precautions.
Ensure project-level default network creation is disabled
It is better to disable the auto-creation of default networks. The default network for a GCP project is usually configured coarsely, leaving the risk of unwanted access to resources in the network.