Manage GCP Dataproc Metastore Database IAM Access

The gcp:dataproc/metastoreDatabaseIamMember:MetastoreDatabaseIamMember resource, part of the Pulumi GCP provider, manages IAM permissions for Dataproc Metastore databases. Three related resources provide different levels of control: MetastoreDatabaseIamMember adds individual grants non-authoritatively, MetastoreDatabaseIamBinding defines complete role membership authoritatively, and MetastoreDatabaseIamPolicy replaces the entire policy. This guide focuses on these three permission management approaches.

All three resources reference existing Metastore services and databases. The examples are intentionally small. Combine them with your own Metastore infrastructure and identity management.

Grant a role to a single member non-authoritatively

When you need to add one person or service account without affecting other permissions, MetastoreDatabaseIamMember adds that single grant while preserving everything else.

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 identifies who receives access using formats like “user:jane@example.com” or “serviceAccount:app@project.iam.gserviceaccount.com”. The role property specifies what they can do. This resource is non-authoritative: it adds one grant without removing other members who have the same role. You can create multiple MetastoreDatabaseIamMember resources for the same role without conflicts.

Grant a role to multiple members authoritatively

When you need to define the complete list of who has a specific role, MetastoreDatabaseIamBinding sets all members for that role at once.

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 property takes an array of identities. This resource is authoritative for the specified role: it replaces the member list for that role but leaves other roles unchanged. You cannot use multiple MetastoreDatabaseIamBinding resources for the same role, but you can combine Binding resources for different roles with Member resources as long as they don’t target the same role.

Replace the entire IAM policy for a database

When you need complete control over all permissions, MetastoreDatabaseIamPolicy replaces the entire IAM policy.

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

const admin = gcp.organizations.getIAMPolicy({
    bindings: [{
        role: "roles/viewer",
        members: ["user:jane@example.com"],
    }],
});
const policy = new gcp.dataproc.MetastoreDatabaseIamPolicy("policy", {
    project: dpmsService.project,
    location: dpmsService.location,
    serviceId: dpmsService.serviceId,
    database: hive.hiveConfig[0].properties.database,
    policyData: admin.then(admin => admin.policyData),
});

import pulumi
import pulumi_gcp as gcp

admin = gcp.organizations.get_iam_policy(bindings=[{
    "role": "roles/viewer",
    "members": ["user:jane@example.com"],
}])
policy = gcp.dataproc.MetastoreDatabaseIamPolicy("policy",
    project=dpms_service["project"],
    location=dpms_service["location"],
    service_id=dpms_service["serviceId"],
    database=hive["hiveConfig"][0]["properties"]["database"],
    policy_data=admin.policy_data)

package main

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

func main() {
	pulumi.Run(func(ctx *pulumi.Context) error {
		admin, err := organizations.LookupIAMPolicy(ctx, &organizations.LookupIAMPolicyArgs{
			Bindings: []organizations.GetIAMPolicyBinding{
				{
					Role: "roles/viewer",
					Members: []string{
						"user:jane@example.com",
					},
				},
			},
		}, nil)
		if err != nil {
			return err
		}
		_, err = dataproc.NewMetastoreDatabaseIamPolicy(ctx, "policy", &dataproc.MetastoreDatabaseIamPolicyArgs{
			Project:    pulumi.Any(dpmsService.Project),
			Location:   pulumi.Any(dpmsService.Location),
			ServiceId:  pulumi.Any(dpmsService.ServiceId),
			Database:   pulumi.Any(hive.HiveConfig[0].Properties.Database),
			PolicyData: pulumi.String(admin.PolicyData),
		})
		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 admin = Gcp.Organizations.GetIAMPolicy.Invoke(new()
    {
        Bindings = new[]
        {
            new Gcp.Organizations.Inputs.GetIAMPolicyBindingInputArgs
            {
                Role = "roles/viewer",
                Members = new[]
                {
                    "user:jane@example.com",
                },
            },
        },
    });

    var policy = new Gcp.Dataproc.MetastoreDatabaseIamPolicy("policy", new()
    {
        Project = dpmsService.Project,
        Location = dpmsService.Location,
        ServiceId = dpmsService.ServiceId,
        Database = hive.HiveConfig[0].Properties.Database,
        PolicyData = admin.Apply(getIAMPolicyResult => getIAMPolicyResult.PolicyData),
    });

});

package generated_program;

import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.gcp.organizations.OrganizationsFunctions;
import com.pulumi.gcp.organizations.inputs.GetIAMPolicyArgs;
import com.pulumi.gcp.dataproc.MetastoreDatabaseIamPolicy;
import com.pulumi.gcp.dataproc.MetastoreDatabaseIamPolicyArgs;
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) {
        final var admin = OrganizationsFunctions.getIAMPolicy(GetIAMPolicyArgs.builder()
            .bindings(GetIAMPolicyBindingArgs.builder()
                .role("roles/viewer")
                .members("user:jane@example.com")
                .build())
            .build());

        var policy = new MetastoreDatabaseIamPolicy("policy", MetastoreDatabaseIamPolicyArgs.builder()
            .project(dpmsService.project())
            .location(dpmsService.location())
            .serviceId(dpmsService.serviceId())
            .database(hive.hiveConfig()[0].properties().database())
            .policyData(admin.policyData())
            .build());

    }
}

resources:
  policy:
    type: gcp:dataproc:MetastoreDatabaseIamPolicy
    properties:
      project: ${dpmsService.project}
      location: ${dpmsService.location}
      serviceId: ${dpmsService.serviceId}
      database: ${hive.hiveConfig[0].properties.database}
      policyData: ${admin.policyData}
variables:
  admin:
    fn::invoke:
      function: gcp:organizations:getIAMPolicy
      arguments:
        bindings:
          - role: roles/viewer
            members:
              - user:jane@example.com

The policyData property comes from the getIAMPolicy data source, which defines bindings for multiple roles. This resource is fully authoritative: it replaces all IAM permissions on the database. You cannot use MetastoreDatabaseIamPolicy alongside MetastoreDatabaseIamBinding or MetastoreDatabaseIamMember resources for the same database, as they will conflict over policy ownership.

Beyond these examples

These snippets focus on specific IAM management features: incremental permission grants, role-level membership management, and complete policy replacement. They’re intentionally minimal rather than full access control solutions.

The examples reference pre-existing infrastructure such as Dataproc Metastore services and databases within those services. They focus on permission configuration rather than provisioning the underlying Metastore resources.

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

  • Conditional IAM bindings (condition property)
  • Custom role definitions
  • Service account creation and management
  • Metastore service and database provisioning

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

Let's manage GCP Dataproc Metastore Database IAM Access

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 MetastoreDatabaseIamPolicy together with MetastoreDatabaseIamBinding or MetastoreDatabaseIamMember?
No, MetastoreDatabaseIamPolicy cannot be used with MetastoreDatabaseIamBinding or MetastoreDatabaseIamMember because they will conflict over the policy. However, you can use MetastoreDatabaseIamBinding and MetastoreDatabaseIamMember together as long as they don’t grant the same role.
What's the difference between MetastoreDatabaseIamPolicy, Binding, and Member resources?
MetastoreDatabaseIamPolicy is fully authoritative and replaces the entire IAM policy. MetastoreDatabaseIamBinding is authoritative for a specific role, replacing all members for that role while preserving other roles. MetastoreDatabaseIamMember is non-authoritative, adding a single member to a role without affecting other members.
IAM Configuration
What identity formats can I use for the member parameter?

The member parameter supports multiple formats:

  • Public access: allUsers, allAuthenticatedUsers
  • Individual accounts: user:{email}, serviceAccount:{email}
  • Groups: group:{email}, domain:{domain}
  • Project roles: projectOwner:{projectid}, projectEditor:{projectid}, projectViewer:{projectid}
  • Federated identities: principal://iam.googleapis.com/... (see Principal identifiers documentation)
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 Management
Can I change the database, role, or member after creating the resource?
No, all properties (database, location, member, project, role, serviceId) are immutable and cannot be changed after creation. You must recreate the resource to modify these values.
What identifier formats can I use when importing this resource?
You can use several formats: the full path projects/{{project}}/locations/{{location}}/services/{{serviceId}}/databases/{{name}}, shortened forms like {{location}}/{{serviceId}}/{{name}}, or just {{name}}. For IAM member imports, use space-delimited format: resource identifier, role, and member identity.

Using a different cloud?

Explore security guides for other cloud providers:

AWS Guides Azure Guides