Manage GCP Dataproc Metastore Database IAM Bindings

The gcp:dataproc/metastoreDatabaseIamBinding:MetastoreDatabaseIamBinding resource, part of the Pulumi GCP provider, grants IAM roles to members for a specific Dataproc Metastore database, controlling who can access and manage database metadata. This guide focuses on two capabilities: granting roles to multiple members simultaneously and adding individual members to existing roles.

This resource references an existing Metastore service and database. The examples are intentionally small. Combine them with your own Metastore infrastructure and identity management.

Grant a role to multiple members at once

Teams managing Metastore databases often need to grant the same role to multiple users or service accounts simultaneously, such as giving viewer access to an entire team.

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

const binding = new gcp.dataproc.MetastoreDatabaseIamBinding("binding", {
    project: dpmsService.project,
    location: dpmsService.location,
    serviceId: dpmsService.serviceId,
    database: hive.hiveConfig[0].properties.database,
    role: "roles/viewer",
    members: ["user:jane@example.com"],
});

import pulumi
import pulumi_gcp as gcp

binding = gcp.dataproc.MetastoreDatabaseIamBinding("binding",
    project=dpms_service["project"],
    location=dpms_service["location"],
    service_id=dpms_service["serviceId"],
    database=hive["hiveConfig"][0]["properties"]["database"],
    role="roles/viewer",
    members=["user:jane@example.com"])

package main

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

func main() {
	pulumi.Run(func(ctx *pulumi.Context) error {
		_, err := dataproc.NewMetastoreDatabaseIamBinding(ctx, "binding", &dataproc.MetastoreDatabaseIamBindingArgs{
			Project:   pulumi.Any(dpmsService.Project),
			Location:  pulumi.Any(dpmsService.Location),
			ServiceId: pulumi.Any(dpmsService.ServiceId),
			Database:  pulumi.Any(hive.HiveConfig[0].Properties.Database),
			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.Dataproc.MetastoreDatabaseIamBinding("binding", new()
    {
        Project = dpmsService.Project,
        Location = dpmsService.Location,
        ServiceId = dpmsService.ServiceId,
        Database = hive.HiveConfig[0].Properties.Database,
        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.dataproc.MetastoreDatabaseIamBinding;
import com.pulumi.gcp.dataproc.MetastoreDatabaseIamBindingArgs;
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 MetastoreDatabaseIamBinding("binding", MetastoreDatabaseIamBindingArgs.builder()
            .project(dpmsService.project())
            .location(dpmsService.location())
            .serviceId(dpmsService.serviceId())
            .database(hive.hiveConfig()[0].properties().database())
            .role("roles/viewer")
            .members("user:jane@example.com")
            .build());

    }
}

resources:
  binding:
    type: gcp:dataproc:MetastoreDatabaseIamBinding
    properties:
      project: ${dpmsService.project}
      location: ${dpmsService.location}
      serviceId: ${dpmsService.serviceId}
      database: ${hive.hiveConfig[0].properties.database}
      role: roles/viewer
      members:
        - user:jane@example.com

The members array lists all identities that receive the specified role. Each member uses a prefix format: user: for Google accounts, serviceAccount: for service accounts, group: for Google groups, or domain: for G Suite domains. The binding is authoritative for this role, meaning it replaces any existing member list for the role while preserving other roles on the database.

Add a single member to a role incrementally

When onboarding individual users or service accounts, you can add them one at a time without affecting existing members who already have the role.

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

const member = new gcp.dataproc.MetastoreDatabaseIamMember("member", {
    project: dpmsService.project,
    location: dpmsService.location,
    serviceId: dpmsService.serviceId,
    database: hive.hiveConfig[0].properties.database,
    role: "roles/viewer",
    member: "user:jane@example.com",
});

import pulumi
import pulumi_gcp as gcp

member = gcp.dataproc.MetastoreDatabaseIamMember("member",
    project=dpms_service["project"],
    location=dpms_service["location"],
    service_id=dpms_service["serviceId"],
    database=hive["hiveConfig"][0]["properties"]["database"],
    role="roles/viewer",
    member="user:jane@example.com")

package main

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

func main() {
	pulumi.Run(func(ctx *pulumi.Context) error {
		_, err := dataproc.NewMetastoreDatabaseIamMember(ctx, "member", &dataproc.MetastoreDatabaseIamMemberArgs{
			Project:   pulumi.Any(dpmsService.Project),
			Location:  pulumi.Any(dpmsService.Location),
			ServiceId: pulumi.Any(dpmsService.ServiceId),
			Database:  pulumi.Any(hive.HiveConfig[0].Properties.Database),
			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.Dataproc.MetastoreDatabaseIamMember("member", new()
    {
        Project = dpmsService.Project,
        Location = dpmsService.Location,
        ServiceId = dpmsService.ServiceId,
        Database = hive.HiveConfig[0].Properties.Database,
        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.dataproc.MetastoreDatabaseIamMember;
import com.pulumi.gcp.dataproc.MetastoreDatabaseIamMemberArgs;
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 MetastoreDatabaseIamMember("member", MetastoreDatabaseIamMemberArgs.builder()
            .project(dpmsService.project())
            .location(dpmsService.location())
            .serviceId(dpmsService.serviceId())
            .database(hive.hiveConfig()[0].properties().database())
            .role("roles/viewer")
            .member("user:jane@example.com")
            .build());

    }
}

resources:
  member:
    type: gcp:dataproc:MetastoreDatabaseIamMember
    properties:
      project: ${dpmsService.project}
      location: ${dpmsService.location}
      serviceId: ${dpmsService.serviceId}
      database: ${hive.hiveConfig[0].properties.database}
      role: roles/viewer
      member: user:jane@example.com

The member property specifies a single identity to add. Unlike MetastoreDatabaseIamBinding, this resource is non-authoritative: it adds the member to the role without removing existing members. You can use multiple MetastoreDatabaseIamMember resources for the same role, or combine them with MetastoreDatabaseIamBinding resources as long as they target different roles.

Beyond these examples

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

The examples reference pre-existing infrastructure such as Dataproc Metastore services and Metastore databases. They focus on configuring access control rather than provisioning the underlying infrastructure.

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

Full policy replacement (MetastoreDatabaseIamPolicy)
Conditional IAM bindings (condition property)
Custom role definitions
Service account creation and management

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

Let's manage GCP Dataproc Metastore Database 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

What's the difference between IamPolicy, IamBinding, and IamMember?

MetastoreDatabaseIamPolicy is fully authoritative and replaces the entire IAM policy. MetastoreDatabaseIamBinding is authoritative for a specific role, preserving other roles. MetastoreDatabaseIamMember is non-authoritative, adding a single member to a role while preserving other members.

Can I use IamPolicy with IamBinding or IamMember?

No, MetastoreDatabaseIamPolicy cannot be used with MetastoreDatabaseIamBinding or MetastoreDatabaseIamMember as they’ll conflict over the policy.

Can I use IamBinding and IamMember together?

Yes, but only if they don’t grant privileges to the same role. Using both for the same role causes conflicts.

Configuration & Identity Formats

What member identity formats are supported?

The members property accepts multiple formats:

allUsers or allAuthenticatedUsers for public/authenticated access
user:{email}, serviceAccount:{email}, group:{email} for specific identities
domain:{domain} for G Suite domains
projectOwner/Editor/Viewer:{projectid} for project-level roles
Federated identities using principal:// format

How do I specify custom roles?

Custom roles must use the format [projects|organizations]/{parent-name}/roles/{role-name}. When importing, use the full custom role name.

Import & Operations

What import formats are supported?

Four formats are supported, from most to least specific:

projects/{{project}}/locations/{{location}}/services/{{serviceId}}/databases/{{name}}
{{project}}/{{location}}/{{serviceId}}/{{name}}
{{location}}/{{serviceId}}/{{name}}
{{name}}

Omitted values are taken from the provider configuration.

Using a different cloud?

Explore security guides for other cloud providers:

AWS Guides Azure Guides