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 additions.
IAM bindings reference existing Feature Views within Feature Online Stores and require valid GCP identities. The examples are intentionally small. Combine them with your own Feature Store infrastructure and identity management.
Grant a role to multiple members at once
Teams managing feature store access often need to grant the same role to multiple users or service accounts simultaneously, such as when onboarding a team or configuring service integrations.
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 any existing members for that role on the Feature View. The members array accepts various identity formats including users, service accounts, groups, and federated identities. The featureView, featureOnlineStore, and region properties identify which Feature View to bind the policy to.
Add a single member to an existing role
When you need to grant access to one additional user without affecting other members who already have the same role, the non-authoritative member resource preserves existing bindings.
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 (AiFeatureOnlineStoreFeatureviewIamMember) is non-authoritative: it adds one identity to a role without removing others. This allows multiple member resources to grant the same role to different identities. Use this when you need incremental access grants rather than replacing the entire member list.
Beyond these examples
These snippets focus on specific IAM binding features: role-based access control and authoritative vs non-authoritative bindings. They’re intentionally minimal rather than full access management solutions.
The examples reference pre-existing infrastructure such as Vertex AI Feature Online Store and Feature View resources. They focus on configuring IAM bindings rather than provisioning the underlying feature store infrastructure.
To keep things focused, common IAM patterns are omitted, including:
- Conditional IAM bindings (condition property)
- Complete policy replacement (IamPolicy resource)
- Custom role definitions
- Cross-project or cross-organization access
These omissions are intentional: the goal is to illustrate how IAM bindings are wired to Feature Views, not provide drop-in access management 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 FREEFrequently Asked Questions
Resource Selection & Conflicts
AiFeatureOnlineStoreFeatureviewIamPolicy is authoritative and replaces the entire IAM policy. AiFeatureOnlineStoreFeatureviewIamBinding is authoritative for a specific role, preserving other roles. AiFeatureOnlineStoreFeatureviewIamMember is non-authoritative, adding individual members without affecting other members for the same role.AiFeatureOnlineStoreFeatureviewIamPolicy cannot be used with AiFeatureOnlineStoreFeatureviewIamBinding or AiFeatureOnlineStoreFeatureviewIamMember because they will conflict over the policy configuration.AiFeatureOnlineStoreFeatureviewIamBinding and AiFeatureOnlineStoreFeatureviewIamMember for the same role causes conflicts.AiFeatureOnlineStoreFeatureviewIamBinding can be used per role. For adding multiple members to a role, include them all in the members array of a single binding, or use AiFeatureOnlineStoreFeatureviewIamMember resources.Identity & Role Configuration
members array supports: allUsers, allAuthenticatedUsers, user:{email}, serviceAccount:{email}, group:{email}, domain:{domain}, projectOwner/Editor/Viewer:{projectid}, and federated identities like principal://iam.googleapis.com/....[projects|organizations]/{parent-name}/roles/{role-name}. For example, projects/my-project/roles/my-custom-role.Regional & Project Configuration
region should match the featureonlinestore region. If not specified, it’s parsed from the parent resource identifier or taken from the provider configuration.project isn’t provided, it’s parsed from the parent resource identifier. If no project is in the parent identifier, the provider project is used.