The gcp:compute/regionDiskIamBinding:RegionDiskIamBinding resource, part of the Pulumi GCP provider, manages IAM role bindings for regional disks. It grants a specific role to a list of members and is authoritative for that role, meaning it replaces all existing members for the role while preserving other roles on the disk. This guide focuses on two capabilities: granting roles to multiple members and adding individual members to roles.
This resource references existing regional disks by name, project, and region. The examples are intentionally small. Combine them with your own disk resources and identity management workflows.
Grant a role to multiple members
Teams managing regional disk access typically grant the same role to multiple users or service accounts at once, such as giving viewer access to an operations team.
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 IAM role to grant (e.g., “roles/viewer”). The members array lists all identities that should have this role. This resource is authoritative for the specified role, replacing any existing members for that role while preserving other role assignments on the disk. The name, region, and project properties identify which regional disk to configure.
Add a single member to a role
When onboarding individual users or granting access to specific service accounts, teams add members one at a time without affecting existing role assignments.
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 RegionDiskIamMember resource (shown in this example) adds a single member to a role non-authoritatively, preserving other members who already have that role. This differs from RegionDiskIamBinding, which replaces all members for a role. Use member (singular) instead of members (array) to specify the identity. The member property accepts the same identity formats: users, service accounts, groups, domains, and federated identities.
Beyond these examples
These snippets focus on specific IAM binding features: role-based access control and member management (bulk and incremental). They’re intentionally minimal rather than full access control configurations.
The examples reference pre-existing infrastructure such as regional disks (by name, project, and region). 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 FREEFrequently Asked Questions
Resource Selection & Conflicts
RegionDiskIamPolicy is fully authoritative and replaces the entire IAM policy. RegionDiskIamBinding is authoritative for a specific role, managing all members for that role while preserving other roles. RegionDiskIamMember is non-authoritative, adding individual members without affecting other members or roles.RegionDiskIamPolicy with RegionDiskIamBinding or RegionDiskIamMember, as they will conflict. You can use RegionDiskIamBinding and RegionDiskIamMember together, but only if they manage different roles.Configuration & Identity Formats
members property accepts multiple formats: user:{email}, serviceAccount:{email}, group:{email}, domain:{domain}, allUsers, allAuthenticatedUsers, projectOwner:{projectid}, projectEditor:{projectid}, projectViewer:{projectid}, and federated identities like principal://iam.googleapis.com/....[projects|organizations]/{parent-name}/roles/{role-name}. For example, projects/my-project/roles/my-custom-role or organizations/my-org/roles/my-custom-role.