Manage GCP Dataproc Metastore Federation IAM Access

The gcp:dataproc/metastoreFederationIamMember:MetastoreFederationIamMember resource, part of the Pulumi GCP provider, manages IAM access grants for Dataproc Metastore Federation instances. This guide focuses on three approaches: non-authoritative member grants, authoritative role bindings, and complete policy replacement.

These resources reference existing Dataproc Metastore Federation instances and require appropriate IAM permissions. The examples are intentionally small. Combine them with your own federation infrastructure and identity management strategy.

Grant a role to a single member non-authoritatively

When you need to add one user or service account without affecting other members who already have access, the non-authoritative member resource preserves existing grants.

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

const member = new gcp.dataproc.MetastoreFederationIamMember("member", {
    project: _default.project,
    location: _default.location,
    federationId: _default.federationId,
    role: "roles/viewer",
    member: "user:jane@example.com",
});
import pulumi
import pulumi_gcp as gcp

member = gcp.dataproc.MetastoreFederationIamMember("member",
    project=default["project"],
    location=default["location"],
    federation_id=default["federationId"],
    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.NewMetastoreFederationIamMember(ctx, "member", &dataproc.MetastoreFederationIamMemberArgs{
			Project:      pulumi.Any(_default.Project),
			Location:     pulumi.Any(_default.Location),
			FederationId: pulumi.Any(_default.FederationId),
			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.MetastoreFederationIamMember("member", new()
    {
        Project = @default.Project,
        Location = @default.Location,
        FederationId = @default.FederationId,
        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.MetastoreFederationIamMember;
import com.pulumi.gcp.dataproc.MetastoreFederationIamMemberArgs;
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 MetastoreFederationIamMember("member", MetastoreFederationIamMemberArgs.builder()
            .project(default_.project())
            .location(default_.location())
            .federationId(default_.federationId())
            .role("roles/viewer")
            .member("user:jane@example.com")
            .build());

    }
}
resources:
  member:
    type: gcp:dataproc:MetastoreFederationIamMember
    properties:
      project: ${default.project}
      location: ${default.location}
      federationId: ${default.federationId}
      role: roles/viewer
      member: user:jane@example.com

The member property specifies a single identity using formats like “user:jane@example.com” or “serviceAccount:app@project.iam.gserviceaccount.com”. The role property defines what permissions that identity receives. This resource adds the member without removing others who already have the same role, making it safe to use alongside other IAM grants.

Grant a role to multiple members authoritatively

When you need to define the complete list of members for a specific role, the binding resource replaces any existing members for that role while preserving other roles.

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

const binding = new gcp.dataproc.MetastoreFederationIamBinding("binding", {
    project: _default.project,
    location: _default.location,
    federationId: _default.federationId,
    role: "roles/viewer",
    members: ["user:jane@example.com"],
});
import pulumi
import pulumi_gcp as gcp

binding = gcp.dataproc.MetastoreFederationIamBinding("binding",
    project=default["project"],
    location=default["location"],
    federation_id=default["federationId"],
    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.NewMetastoreFederationIamBinding(ctx, "binding", &dataproc.MetastoreFederationIamBindingArgs{
			Project:      pulumi.Any(_default.Project),
			Location:     pulumi.Any(_default.Location),
			FederationId: pulumi.Any(_default.FederationId),
			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.MetastoreFederationIamBinding("binding", new()
    {
        Project = @default.Project,
        Location = @default.Location,
        FederationId = @default.FederationId,
        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.MetastoreFederationIamBinding;
import com.pulumi.gcp.dataproc.MetastoreFederationIamBindingArgs;
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 MetastoreFederationIamBinding("binding", MetastoreFederationIamBindingArgs.builder()
            .project(default_.project())
            .location(default_.location())
            .federationId(default_.federationId())
            .role("roles/viewer")
            .members("user:jane@example.com")
            .build());

    }
}
resources:
  binding:
    type: gcp:dataproc:MetastoreFederationIamBinding
    properties:
      project: ${default.project}
      location: ${default.location}
      federationId: ${default.federationId}
      role: roles/viewer
      members:
        - user:jane@example.com

The members property takes a list of identities that will have the specified role. This resource is authoritative for the role: it replaces any existing members for that role but leaves other roles untouched. You can combine multiple binding resources as long as they manage different roles.

Replace the entire IAM policy authoritatively

When you need complete control over all roles and members, the policy resource 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.MetastoreFederationIamPolicy("policy", {
    project: _default.project,
    location: _default.location,
    federationId: _default.federationId,
    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.MetastoreFederationIamPolicy("policy",
    project=default["project"],
    location=default["location"],
    federation_id=default["federationId"],
    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.NewMetastoreFederationIamPolicy(ctx, "policy", &dataproc.MetastoreFederationIamPolicyArgs{
			Project:      pulumi.Any(_default.Project),
			Location:     pulumi.Any(_default.Location),
			FederationId: pulumi.Any(_default.FederationId),
			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.MetastoreFederationIamPolicy("policy", new()
    {
        Project = @default.Project,
        Location = @default.Location,
        FederationId = @default.FederationId,
        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.MetastoreFederationIamPolicy;
import com.pulumi.gcp.dataproc.MetastoreFederationIamPolicyArgs;
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 MetastoreFederationIamPolicy("policy", MetastoreFederationIamPolicyArgs.builder()
            .project(default_.project())
            .location(default_.location())
            .federationId(default_.federationId())
            .policyData(admin.policyData())
            .build());

    }
}
resources:
  policy:
    type: gcp:dataproc:MetastoreFederationIamPolicy
    properties:
      project: ${default.project}
      location: ${default.location}
      federationId: ${default.federationId}
      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 all roles. This resource is fully authoritative: it replaces the entire policy, removing any grants not explicitly listed. It cannot be used with MetastoreFederationIamBinding or MetastoreFederationIamMember resources because they would conflict over policy state.

Beyond these examples

These snippets focus on specific IAM management features: non-authoritative member grants, authoritative role bindings, and complete policy replacement. They’re intentionally minimal rather than full access control configurations.

The examples reference pre-existing infrastructure such as Dataproc Metastore Federation instances and GCP projects with appropriate IAM permissions. They focus on configuring access grants rather than provisioning the federation itself.

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

  • Conditional IAM bindings (condition property)
  • Custom role definitions and formatting
  • Federated identity principals and workload identity
  • Policy conflict resolution between resource types

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 Federation IAM Member resource reference for all available configuration options.

Let's manage GCP Dataproc Metastore Federation 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 Conflicts & Errors
Can I use these IAM resources together?
MetastoreFederationIamPolicy cannot be used with MetastoreFederationIamBinding or MetastoreFederationIamMember as they will conflict. However, MetastoreFederationIamBinding and MetastoreFederationIamMember can be used together if they don’t grant the same role.
Why am I seeing IAM policy conflicts?
Mixing MetastoreFederationIamPolicy (authoritative) with MetastoreFederationIamBinding or MetastoreFederationIamMember causes them to fight over the policy. Use IamPolicy alone, or use IamBinding/IamMember together for different roles.
IAM Configuration
How do I choose between IamPolicy, IamBinding, and IamMember?
Use MetastoreFederationIamPolicy for full control (replaces entire policy), MetastoreFederationIamBinding to manage all members for a specific role (preserves other roles), or MetastoreFederationIamMember to add individual members without affecting others (non-authoritative).
What identity formats can I use for the member parameter?
Supported formats include allUsers, allAuthenticatedUsers, user:{email}, serviceAccount:{email}, group:{email}, domain:{domain}, projectOwner/Editor/Viewer:{projectid}, and federated identities like principal://iam.googleapis.com/....
How do I format custom roles?
Custom roles must use the format [projects|organizations]/{parent-name}/roles/{role-name}, for example projects/my-project/roles/my-custom-role.
What properties can't be changed after creation?
All main properties are immutable: federationId, location, member, project, and role. Changes to these require resource replacement.
Import & Migration
What formats can I use when importing?
You can import using the full path (projects/{project}/locations/{location}/federations/{federation_id}), partial paths, or just {federation_id}. Missing values are taken from the provider configuration.

Using a different cloud?

Explore security guides for other cloud providers: