Manage GCP Compute Regional Disk IAM Bindings

The gcp:compute/regionDiskIamBinding:RegionDiskIamBinding resource, part of the Pulumi GCP provider, manages IAM role bindings for Compute Engine regional disks. This resource provides authoritative control over which identities have a specific role, replacing any existing members for that role. This guide focuses on two capabilities: granting roles to multiple members and adding individual members non-authoritatively.

IAM bindings reference existing regional disks and work alongside two related resources: RegionDiskIamPolicy (full policy replacement) and RegionDiskIamMember (non-authoritative member additions). The examples are intentionally small. Combine them with your own disk resources and identity management strategy.

Grant a role to multiple members

Teams managing disk access often need to grant the same role to multiple users or service accounts at once.

import * as pulumi from "@pulumi/pulumi";
import * as gcp from "@pulumi/gcp";

const binding = new gcp.compute.RegionDiskIamBinding("binding", {
    project: regiondisk.project,
    region: regiondisk.region,
    name: regiondisk.name,
    role: "roles/viewer",
    members: ["user:jane@example.com"],
});

import pulumi
import pulumi_gcp as gcp

binding = gcp.compute.RegionDiskIamBinding("binding",
    project=regiondisk["project"],
    region=regiondisk["region"],
    name=regiondisk["name"],
    role="roles/viewer",
    members=["user:jane@example.com"])

package main

import (
	"github.com/pulumi/pulumi-gcp/sdk/v9/go/gcp/compute"
	"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)

func main() {
	pulumi.Run(func(ctx *pulumi.Context) error {
		_, err := compute.NewRegionDiskIamBinding(ctx, "binding", &compute.RegionDiskIamBindingArgs{
			Project: pulumi.Any(regiondisk.Project),
			Region:  pulumi.Any(regiondisk.Region),
			Name:    pulumi.Any(regiondisk.Name),
			Role:    pulumi.String("roles/viewer"),
			Members: pulumi.StringArray{
				pulumi.String("user:jane@example.com"),
			},
		})
		if err != nil {
			return err
		}
		return nil
	})
}

using System.Collections.Generic;
using System.Linq;
using Pulumi;
using Gcp = Pulumi.Gcp;

return await Deployment.RunAsync(() => 
{
    var binding = new Gcp.Compute.RegionDiskIamBinding("binding", new()
    {
        Project = regiondisk.Project,
        Region = regiondisk.Region,
        Name = regiondisk.Name,
        Role = "roles/viewer",
        Members = new[]
        {
            "user:jane@example.com",
        },
    });

});

package generated_program;

import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.gcp.compute.RegionDiskIamBinding;
import com.pulumi.gcp.compute.RegionDiskIamBindingArgs;
import java.util.List;
import java.util.ArrayList;
import java.util.Map;
import java.io.File;
import java.nio.file.Files;
import java.nio.file.Paths;

public class App {
    public static void main(String[] args) {
        Pulumi.run(App::stack);
    }

    public static void stack(Context ctx) {
        var binding = new RegionDiskIamBinding("binding", RegionDiskIamBindingArgs.builder()
            .project(regiondisk.project())
            .region(regiondisk.region())
            .name(regiondisk.name())
            .role("roles/viewer")
            .members("user:jane@example.com")
            .build());

    }
}

resources:
  binding:
    type: gcp:compute:RegionDiskIamBinding
    properties:
      project: ${regiondisk.project}
      region: ${regiondisk.region}
      name: ${regiondisk.name}
      role: roles/viewer
      members:
        - user:jane@example.com

The role property specifies which permission set to grant (e.g., “roles/viewer”). The members array lists all identities that should have this role; this resource authoritatively controls the member list, removing any members not included. Each member uses a prefix format: “user:” for Google accounts, “serviceAccount:” for service accounts, “group:” for Google groups.

Add a single member to a role

When you need to grant access to one additional user without affecting existing members, use RegionDiskIamMember for non-authoritative updates.

import * as pulumi from "@pulumi/pulumi";
import * as gcp from "@pulumi/gcp";

const member = new gcp.compute.RegionDiskIamMember("member", {
    project: regiondisk.project,
    region: regiondisk.region,
    name: regiondisk.name,
    role: "roles/viewer",
    member: "user:jane@example.com",
});

import pulumi
import pulumi_gcp as gcp

member = gcp.compute.RegionDiskIamMember("member",
    project=regiondisk["project"],
    region=regiondisk["region"],
    name=regiondisk["name"],
    role="roles/viewer",
    member="user:jane@example.com")

package main

import (
	"github.com/pulumi/pulumi-gcp/sdk/v9/go/gcp/compute"
	"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)

func main() {
	pulumi.Run(func(ctx *pulumi.Context) error {
		_, err := compute.NewRegionDiskIamMember(ctx, "member", &compute.RegionDiskIamMemberArgs{
			Project: pulumi.Any(regiondisk.Project),
			Region:  pulumi.Any(regiondisk.Region),
			Name:    pulumi.Any(regiondisk.Name),
			Role:    pulumi.String("roles/viewer"),
			Member:  pulumi.String("user:jane@example.com"),
		})
		if err != nil {
			return err
		}
		return nil
	})
}

using System.Collections.Generic;
using System.Linq;
using Pulumi;
using Gcp = Pulumi.Gcp;

return await Deployment.RunAsync(() => 
{
    var member = new Gcp.Compute.RegionDiskIamMember("member", new()
    {
        Project = regiondisk.Project,
        Region = regiondisk.Region,
        Name = regiondisk.Name,
        Role = "roles/viewer",
        Member = "user:jane@example.com",
    });

});

package generated_program;

import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.gcp.compute.RegionDiskIamMember;
import com.pulumi.gcp.compute.RegionDiskIamMemberArgs;
import java.util.List;
import java.util.ArrayList;
import java.util.Map;
import java.io.File;
import java.nio.file.Files;
import java.nio.file.Paths;

public class App {
    public static void main(String[] args) {
        Pulumi.run(App::stack);
    }

    public static void stack(Context ctx) {
        var member = new RegionDiskIamMember("member", RegionDiskIamMemberArgs.builder()
            .project(regiondisk.project())
            .region(regiondisk.region())
            .name(regiondisk.name())
            .role("roles/viewer")
            .member("user:jane@example.com")
            .build());

    }
}

resources:
  member:
    type: gcp:compute:RegionDiskIamMember
    properties:
      project: ${regiondisk.project}
      region: ${regiondisk.region}
      name: ${regiondisk.name}
      role: roles/viewer
      member: user:jane@example.com

The member property specifies a single identity to add. Unlike RegionDiskIamBinding, this resource preserves other members who already have the role. You can use multiple RegionDiskIamMember resources for the same role, or combine them with RegionDiskIamBinding resources for different roles.

Beyond these examples

These snippets focus on specific IAM binding features: role-based access control and authoritative vs non-authoritative member management. They’re intentionally minimal rather than full access control configurations.

The examples reference pre-existing infrastructure such as regional disks (by name, region, and project). They focus on configuring IAM bindings rather than provisioning the disks themselves.

To keep things focused, common IAM patterns are omitted, including:

Conditional IAM bindings (condition property)
Full policy replacement (RegionDiskIamPolicy resource)
Custom role definitions
Federated identity configuration

These omissions are intentional: the goal is to illustrate how IAM bindings are wired, not provide drop-in access control modules. See the RegionDiskIamBinding resource reference for all available configuration options.

Let's manage GCP Compute Regional Disk IAM Bindings

Get started with Pulumi Cloud, then follow our quick setup guide to deploy this infrastructure.

Try Pulumi Cloud for FREE

Frequently Asked Questions

Resource Selection & Conflicts

Can I use RegionDiskIamPolicy with RegionDiskIamBinding or RegionDiskIamMember?

No, gcp.compute.RegionDiskIamPolicy cannot be used with gcp.compute.RegionDiskIamBinding or gcp.compute.RegionDiskIamMember because they will conflict over the policy configuration.

Can I use RegionDiskIamBinding and RegionDiskIamMember together?

Yes, but only if they don’t grant privileges to the same role. If both resources target the same role, they will conflict.

What's the difference between RegionDiskIamPolicy, RegionDiskIamBinding, and RegionDiskIamMember?

gcp.compute.RegionDiskIamPolicy is authoritative and replaces the entire IAM policy. gcp.compute.RegionDiskIamBinding is authoritative for a specific role but preserves other roles. gcp.compute.RegionDiskIamMember is non-authoritative and adds a single member while preserving other members for that role.

Configuration & Identity Management

What member identity formats are supported?

The members property supports multiple formats: allUsers, allAuthenticatedUsers, user:{email}, serviceAccount:{email}, group:{email}, domain:{domain}, projectOwner:{projectid}, projectEditor:{projectid}, projectViewer:{projectid}, and federated identities like principal://iam.googleapis.com/....

How do I specify a custom IAM role?

Custom roles must use the format [projects|organizations]/{parent-name}/roles/{role-name}, for example projects/my-project/roles/my-custom-role or organizations/my-org/roles/my-custom-role.

Resource Properties

What properties can't be changed after creating a RegionDiskIamBinding?

The name, project, region, and role properties are immutable and cannot be changed after resource creation.

Can I use multiple RegionDiskIamBinding resources for the same disk?

Yes, but only one gcp.compute.RegionDiskIamBinding can be used per role. You can have multiple bindings for different roles on the same disk.

Using a different cloud?

Explore security guides for other cloud providers:

AWS Guides Azure Guides