Manage GCP Vertex AI Feature Store IAM Bindings

The gcp:vertex/aiFeatureOnlineStoreFeatureviewIamBinding:AiFeatureOnlineStoreFeatureviewIamBinding resource, part of the Pulumi GCP provider, manages IAM role bindings for Vertex AI Feature Online Store feature views, controlling which identities can access feature data. This guide focuses on two capabilities: authoritative role bindings for multiple members and non-authoritative single-member grants.

IAM bindings reference existing feature views within Feature Online Stores. The examples are intentionally small. Combine them with your own feature store infrastructure and identity management strategy.

Grant a role to multiple members at once

When onboarding a data science team, you 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.vertex.AiFeatureOnlineStoreFeatureviewIamBinding("binding", {
    region: featureview.region,
    featureOnlineStore: featureview.featureOnlineStore,
    featureView: featureview.name,
    role: "roles/viewer",
    members: ["user:jane@example.com"],
});
import pulumi
import pulumi_gcp as gcp

binding = gcp.vertex.AiFeatureOnlineStoreFeatureviewIamBinding("binding",
    region=featureview["region"],
    feature_online_store=featureview["featureOnlineStore"],
    feature_view=featureview["name"],
    role="roles/viewer",
    members=["user:jane@example.com"])
package main

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

func main() {
	pulumi.Run(func(ctx *pulumi.Context) error {
		_, err := vertex.NewAiFeatureOnlineStoreFeatureviewIamBinding(ctx, "binding", &vertex.AiFeatureOnlineStoreFeatureviewIamBindingArgs{
			Region:             pulumi.Any(featureview.Region),
			FeatureOnlineStore: pulumi.Any(featureview.FeatureOnlineStore),
			FeatureView:        pulumi.Any(featureview.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.Vertex.AiFeatureOnlineStoreFeatureviewIamBinding("binding", new()
    {
        Region = featureview.Region,
        FeatureOnlineStore = featureview.FeatureOnlineStore,
        FeatureView = featureview.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.vertex.AiFeatureOnlineStoreFeatureviewIamBinding;
import com.pulumi.gcp.vertex.AiFeatureOnlineStoreFeatureviewIamBindingArgs;
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 AiFeatureOnlineStoreFeatureviewIamBinding("binding", AiFeatureOnlineStoreFeatureviewIamBindingArgs.builder()
            .region(featureview.region())
            .featureOnlineStore(featureview.featureOnlineStore())
            .featureView(featureview.name())
            .role("roles/viewer")
            .members("user:jane@example.com")
            .build());

    }
}
resources:
  binding:
    type: gcp:vertex:AiFeatureOnlineStoreFeatureviewIamBinding
    properties:
      region: ${featureview.region}
      featureOnlineStore: ${featureview.featureOnlineStore}
      featureView: ${featureview.name}
      role: roles/viewer
      members:
        - user:jane@example.com

The binding resource is authoritative for the specified role: it replaces all members for that role on the feature view. The members array accepts various identity formats including user emails, service accounts, groups, and federated identities. The featureView and featureOnlineStore properties identify which feature view to grant access to.

Add a single member to an existing role

When you need to grant access to one additional user without affecting other members, the non-authoritative member resource preserves existing assignments.

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

const member = new gcp.vertex.AiFeatureOnlineStoreFeatureviewIamMember("member", {
    region: featureview.region,
    featureOnlineStore: featureview.featureOnlineStore,
    featureView: featureview.name,
    role: "roles/viewer",
    member: "user:jane@example.com",
});
import pulumi
import pulumi_gcp as gcp

member = gcp.vertex.AiFeatureOnlineStoreFeatureviewIamMember("member",
    region=featureview["region"],
    feature_online_store=featureview["featureOnlineStore"],
    feature_view=featureview["name"],
    role="roles/viewer",
    member="user:jane@example.com")
package main

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

func main() {
	pulumi.Run(func(ctx *pulumi.Context) error {
		_, err := vertex.NewAiFeatureOnlineStoreFeatureviewIamMember(ctx, "member", &vertex.AiFeatureOnlineStoreFeatureviewIamMemberArgs{
			Region:             pulumi.Any(featureview.Region),
			FeatureOnlineStore: pulumi.Any(featureview.FeatureOnlineStore),
			FeatureView:        pulumi.Any(featureview.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.Vertex.AiFeatureOnlineStoreFeatureviewIamMember("member", new()
    {
        Region = featureview.Region,
        FeatureOnlineStore = featureview.FeatureOnlineStore,
        FeatureView = featureview.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.vertex.AiFeatureOnlineStoreFeatureviewIamMember;
import com.pulumi.gcp.vertex.AiFeatureOnlineStoreFeatureviewIamMemberArgs;
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 AiFeatureOnlineStoreFeatureviewIamMember("member", AiFeatureOnlineStoreFeatureviewIamMemberArgs.builder()
            .region(featureview.region())
            .featureOnlineStore(featureview.featureOnlineStore())
            .featureView(featureview.name())
            .role("roles/viewer")
            .member("user:jane@example.com")
            .build());

    }
}
resources:
  member:
    type: gcp:vertex:AiFeatureOnlineStoreFeatureviewIamMember
    properties:
      region: ${featureview.region}
      featureOnlineStore: ${featureview.featureOnlineStore}
      featureView: ${featureview.name}
      role: roles/viewer
      member: user:jane@example.com

The member resource adds a single identity to a role without replacing other members. This is useful for incremental access grants where you don’t want to manage the complete member list. Unlike the binding resource, multiple member resources can target the same role without conflict.

Beyond these examples

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

The examples reference pre-existing infrastructure such as Vertex AI Feature Online Stores and feature views within the store. They focus on configuring IAM bindings rather than provisioning the underlying feature store resources.

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

  • Conditional IAM bindings (condition property)
  • Project and region specification (uses defaults from parent resource)
  • Policy-level management (AiFeatureOnlineStoreFeatureviewIamPolicy)
  • Custom role definitions

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

Let's manage GCP Vertex AI Feature Store 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 & Compatibility
What's the difference between IamPolicy, IamBinding, and IamMember?
AiFeatureOnlineStoreFeatureviewIamPolicy is authoritative and replaces the entire IAM policy. AiFeatureOnlineStoreFeatureviewIamBinding is authoritative for a specific role, preserving other roles. AiFeatureOnlineStoreFeatureviewIamMember is non-authoritative and adds individual members without affecting other members for the same role.
Can I use IamPolicy with IamBinding or IamMember?
No, AiFeatureOnlineStoreFeatureviewIamPolicy cannot be used with AiFeatureOnlineStoreFeatureviewIamBinding or AiFeatureOnlineStoreFeatureviewIamMember because they will 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 will cause conflicts.
IAM Configuration
What format do custom roles need?
Custom roles must use the format [projects|organizations]/{parent-name}/roles/{role-name}.
What member identity formats are supported?
Supported formats include allUsers, allAuthenticatedUsers, user:{email}, serviceAccount:{email}, group:{email}, domain:{domain}, projectOwner:{projectid}, projectEditor:{projectid}, projectViewer:{projectid}, and federated identities like principal://iam.googleapis.com/....
Beta & Stability
Is this resource production-ready?
This resource is in beta and requires the terraform-provider-google-beta provider.

Using a different cloud?

Explore security guides for other cloud providers: