The gcp:vertex/aiFeatureOnlineStoreIamBinding:AiFeatureOnlineStoreIamBinding resource, part of the Pulumi GCP provider, manages IAM role bindings for Vertex AI Feature Online Store instances. This guide focuses on two capabilities: granting roles to multiple members and adding individual members non-authoritatively.
IAM bindings reference existing Feature Online Store instances and require appropriate GCP project and region configuration. The examples are intentionally small. Combine them with your own feature stores and identity management strategy.
Grant a role to multiple members at once
When onboarding teams or configuring cross-project access, you often need to assign 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.AiFeatureOnlineStoreIamBinding("binding", {
region: featureOnlineStore.region,
featureOnlineStore: featureOnlineStore.name,
role: "roles/viewer",
members: ["user:jane@example.com"],
});
import pulumi
import pulumi_gcp as gcp
binding = gcp.vertex.AiFeatureOnlineStoreIamBinding("binding",
region=feature_online_store["region"],
feature_online_store=feature_online_store["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.NewAiFeatureOnlineStoreIamBinding(ctx, "binding", &vertex.AiFeatureOnlineStoreIamBindingArgs{
Region: pulumi.Any(featureOnlineStore.Region),
FeatureOnlineStore: pulumi.Any(featureOnlineStore.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.AiFeatureOnlineStoreIamBinding("binding", new()
{
Region = featureOnlineStore.Region,
FeatureOnlineStore = featureOnlineStore.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.AiFeatureOnlineStoreIamBinding;
import com.pulumi.gcp.vertex.AiFeatureOnlineStoreIamBindingArgs;
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 AiFeatureOnlineStoreIamBinding("binding", AiFeatureOnlineStoreIamBindingArgs.builder()
.region(featureOnlineStore.region())
.featureOnlineStore(featureOnlineStore.name())
.role("roles/viewer")
.members("user:jane@example.com")
.build());
}
}
resources:
binding:
type: gcp:vertex:AiFeatureOnlineStoreIamBinding
properties:
region: ${featureOnlineStore.region}
featureOnlineStore: ${featureOnlineStore.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 store. The members array accepts various identity formats including user emails, service accounts, groups, and federated identities. The role property specifies which permissions to grant; the featureOnlineStore and region properties identify the target resource.
Add a single member to an existing role
To grant access to one additional user without affecting other members, use the non-authoritative member resource.
import * as pulumi from "@pulumi/pulumi";
import * as gcp from "@pulumi/gcp";
const member = new gcp.vertex.AiFeatureOnlineStoreIamMember("member", {
region: featureOnlineStore.region,
featureOnlineStore: featureOnlineStore.name,
role: "roles/viewer",
member: "user:jane@example.com",
});
import pulumi
import pulumi_gcp as gcp
member = gcp.vertex.AiFeatureOnlineStoreIamMember("member",
region=feature_online_store["region"],
feature_online_store=feature_online_store["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.NewAiFeatureOnlineStoreIamMember(ctx, "member", &vertex.AiFeatureOnlineStoreIamMemberArgs{
Region: pulumi.Any(featureOnlineStore.Region),
FeatureOnlineStore: pulumi.Any(featureOnlineStore.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.AiFeatureOnlineStoreIamMember("member", new()
{
Region = featureOnlineStore.Region,
FeatureOnlineStore = featureOnlineStore.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.AiFeatureOnlineStoreIamMember;
import com.pulumi.gcp.vertex.AiFeatureOnlineStoreIamMemberArgs;
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 AiFeatureOnlineStoreIamMember("member", AiFeatureOnlineStoreIamMemberArgs.builder()
.region(featureOnlineStore.region())
.featureOnlineStore(featureOnlineStore.name())
.role("roles/viewer")
.member("user:jane@example.com")
.build());
}
}
resources:
member:
type: gcp:vertex:AiFeatureOnlineStoreIamMember
properties:
region: ${featureOnlineStore.region}
featureOnlineStore: ${featureOnlineStore.name}
role: roles/viewer
member: user:jane@example.com
Unlike the binding resource, the member resource preserves existing role assignments. It adds one identity to the specified role without removing others. This approach works well when multiple teams manage access independently, as each can add members without coordinating changes.
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 Store instances and GCP project with appropriate region configuration. They focus on configuring IAM bindings rather than provisioning the feature stores themselves.
To keep things focused, common IAM patterns are omitted, including:
- Conditional IAM bindings (condition property)
- Custom role definitions and formatting
- Policy-level management (AiFeatureOnlineStoreIamPolicy)
- Cross-project access patterns
These omissions are intentional: the goal is to illustrate how each IAM binding feature is wired, not provide drop-in access control modules. See the AiFeatureOnlineStoreIamBinding 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 & Compatibility
AiFeatureOnlineStoreIamPolicy cannot be used with AiFeatureOnlineStoreIamBinding or AiFeatureOnlineStoreIamMember because they will conflict over policy management. Choose one approach: use Policy for full control, or use Binding/Member for granular management.AiFeatureOnlineStoreIamPolicy for full authoritative control (replaces entire policy), AiFeatureOnlineStoreIamBinding for authoritative per-role management (preserves other roles), or AiFeatureOnlineStoreIamMember for non-authoritative management (preserves other members for the role).Configuration & Identity Management
user:{email}, serviceAccount:{email}, group:{email}, domain:{domain}, allUsers, allAuthenticatedUsers, project-based identities like projectOwner:projectid, and federated identities (see Principal identifiers documentation for examples).[projects|organizations]/{parent-name}/roles/{role-name}. For example, projects/my-project/roles/my-custom-role.featureOnlineStore, role, region, project, and condition properties are immutable and cannot be changed after creation.