Google Cloud Platform Organization IAM

google_organization_iam (Terraform)

The Organization IAM in Cloud Platform can be configured in Terraform with the resource name google_organization_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.

Parameters

The following arguments are supported:

• member/members - (Required except for google_organization_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, alice@gmail.com or joe@example.com.
  • serviceAccount:[emailid]: An email address that represents a service account. For example, my-other-app@appspot.gserviceaccount.com.
  • group:[emailid]: An email address that represents a Google group. For example, admins@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_organization_iam_audit_config) The role that should be applied. Only one google_organization_iam_binding can be used per role. Note that custom roles must be of the format organizations/[[org_id]]/roles/[[role_id]].

• policy_data - (Required only by google_organization_iam_policy) The google_iam_policy data source that represents the IAM policy that will be applied to the organization. The policy will be merged with any existing policy applied to the organization.

  Changing this updates the policy.

  Deleting this removes all policies from the organization, locking out users without organization-level access.

• org_id - (Optional) The organization ID. If not specified for google_organization_iam_binding, google_organization_iam_member, or google_organization_iam_audit_config, uses the ID of the organization configured with the provider. Required for google_organization_iam_policy - you must explicitly set the organization, and it will not be inferred from the provider.

• service - (Required only by google_organization_iam_audit_config) Service which will be enabled for audit logging. The special value allServices covers all services. Note that if there are google_organization_iam_audit_config resources covering both allServices and a specific service then the union of the two AuditConfigs is used for that service: the log_types specified in each audit_log_config are enabled, and the exempted_members in each audit_log_config are exempted.

• audit_log_config - (Required only by google_organization_iam_audit_config) The configuration for logging of each type of permission. This can be specified multiple times. Structure is documented below.

• condition - (Optional) An IAM Condition for a given binding. Structure is documented below.

The audit_log_config block supports:

• log_type - (Required) Permission type for which logging is to be configured. Must be one of DATA_READ, DATA_WRITE, or ADMIN_READ.

• exempted_members - (Optional) Identities that do not cause logging for this type of permission. The format is the same as that for members.

The 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 role and condition contents (title+description+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 organization's IAM policy.

Explanation in Terraform Registry

Four different resources help you manage your IAM policy for a organization. Each of these resources serves a different use case:

• google_organization_iam_policy: Authoritative. Sets the IAM policy for the organization and replaces any existing policy already attached.
• google_organization_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 organization are preserved.
• google_organization_iam_member: Non-authoritative. Updates the IAM policy to grant a role to a new member. Other members for the role for the organization are preserved.
• google_organization_iam_audit_config: Authoritative for a given service. Updates the IAM policy to enable audit logging for the given service.

  Note: google_organization_iam_policy cannot be used in conjunction with google_organization_iam_binding, google_organization_iam_member, or google_organization_iam_audit_config or they will fight over what your policy should be.

  Note: google_organization_iam_binding resources can be used in conjunction with google_organization_iam_member resources only if they do not grant privilege to the same role.

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.

google_project

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.