The gcp:compute/diskIamBinding:DiskIamBinding resource, part of the Pulumi GCP provider, manages IAM role bindings for Compute Engine disks. It grants a specific role to a list of members while preserving other roles on the disk. This guide focuses on two capabilities: authoritative role binding for multiple members and its relationship to DiskIamMember and DiskIamPolicy.
DiskIamBinding references existing Compute Engine disks and cannot be used alongside DiskIamPolicy (they conflict over policy ownership). It can coexist with DiskIamMember only if they manage different roles. The examples are intentionally small. Combine them with your own disk resources and identity management.
Grant a role to multiple members at once
Teams managing disk access often need to grant the same role to multiple users or service accounts simultaneously.
import * as pulumi from "@pulumi/pulumi";
import * as gcp from "@pulumi/gcp";
const binding = new gcp.compute.DiskIamBinding("binding", {
project: _default.project,
zone: _default.zone,
name: _default.name,
role: "roles/viewer",
members: ["user:jane@example.com"],
});
import pulumi
import pulumi_gcp as gcp
binding = gcp.compute.DiskIamBinding("binding",
project=default["project"],
zone=default["zone"],
name=default["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.NewDiskIamBinding(ctx, "binding", &compute.DiskIamBindingArgs{
Project: pulumi.Any(_default.Project),
Zone: pulumi.Any(_default.Zone),
Name: pulumi.Any(_default.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.DiskIamBinding("binding", new()
{
Project = @default.Project,
Zone = @default.Zone,
Name = @default.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.DiskIamBinding;
import com.pulumi.gcp.compute.DiskIamBindingArgs;
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 DiskIamBinding("binding", DiskIamBindingArgs.builder()
.project(default_.project())
.zone(default_.zone())
.name(default_.name())
.role("roles/viewer")
.members("user:jane@example.com")
.build());
}
}
resources:
binding:
type: gcp:compute:DiskIamBinding
properties:
project: ${default.project}
zone: ${default.zone}
name: ${default.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 receive this role; DiskIamBinding is authoritative for this role, meaning it replaces any existing members for that role. The name, zone, and project properties identify which disk to bind permissions to.
Add a single member to a role incrementally
When you need to grant access to one identity without affecting other members who already have the same role, use DiskIamMember for non-authoritative updates.
import * as pulumi from "@pulumi/pulumi";
import * as gcp from "@pulumi/gcp";
const member = new gcp.compute.DiskIamMember("member", {
project: _default.project,
zone: _default.zone,
name: _default.name,
role: "roles/viewer",
member: "user:jane@example.com",
});
import pulumi
import pulumi_gcp as gcp
member = gcp.compute.DiskIamMember("member",
project=default["project"],
zone=default["zone"],
name=default["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.NewDiskIamMember(ctx, "member", &compute.DiskIamMemberArgs{
Project: pulumi.Any(_default.Project),
Zone: pulumi.Any(_default.Zone),
Name: pulumi.Any(_default.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.DiskIamMember("member", new()
{
Project = @default.Project,
Zone = @default.Zone,
Name = @default.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.DiskIamMember;
import com.pulumi.gcp.compute.DiskIamMemberArgs;
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 DiskIamMember("member", DiskIamMemberArgs.builder()
.project(default_.project())
.zone(default_.zone())
.name(default_.name())
.role("roles/viewer")
.member("user:jane@example.com")
.build());
}
}
resources:
member:
type: gcp:compute:DiskIamMember
properties:
project: ${default.project}
zone: ${default.zone}
name: ${default.name}
role: roles/viewer
member: user:jane@example.com
The member property (singular) specifies one identity to add to the role. Unlike DiskIamBinding, DiskIamMember preserves existing members for the same role. This lets you incrementally add access without managing the full member list.
Beyond these examples
These snippets focus on specific disk IAM features: role binding for multiple members and incremental member addition. They’re intentionally minimal rather than full access control configurations.
The examples reference pre-existing infrastructure such as Compute Engine disks in specified zones and a GCP project with appropriate IAM permissions. They focus on configuring IAM bindings rather than provisioning disks or managing the full IAM policy.
To keep things focused, common disk IAM patterns are omitted, including:
- Conditional IAM bindings (condition property)
- Full policy replacement (DiskIamPolicy resource)
- Custom role definitions
- Federated identity configuration
These omissions are intentional: the goal is to illustrate how disk IAM bindings are wired, not provide drop-in access control modules. See the Compute Disk IAM Binding resource reference for all available configuration options.
Let's manage GCP Compute 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
gcp.compute.DiskIamPolicy is authoritative and replaces the entire policy, gcp.compute.DiskIamBinding is authoritative for a single role while preserving other roles, and gcp.compute.DiskIamMember is non-authoritative and adds individual members to a role.gcp.compute.DiskIamPolicy cannot be used with gcp.compute.DiskIamBinding or gcp.compute.DiskIamMember because they will conflict over the policy state.gcp.compute.DiskIamBinding and gcp.compute.DiskIamMember for the same role will cause conflicts.Configuration & Immutability
role, name, project, zone, and condition properties are immutable and cannot be changed after creation.[projects|organizations]/{parent-name}/roles/{role-name}.Member Identities
allUsers, allAuthenticatedUsers, user:{email}, serviceAccount:{email}, group:{email}, domain:{domain}, projectOwner/Editor/Viewer:{projectid}, and federated identities like principal://iam.googleapis.com/....