The gcp:vertex/aiFeatureGroupIamMember:AiFeatureGroupIamMember resource, part of the Pulumi GCP provider, manages IAM permissions for Vertex AI feature groups by adding individual members to roles without affecting other role bindings. This guide focuses on three IAM management approaches: single-member grants, multi-member role bindings, and full policy replacement.
GCP provides three related resources for managing feature group IAM: AiFeatureGroupIamMember (non-authoritative, adds one member), AiFeatureGroupIamBinding (authoritative per role, sets all members for a role), and AiFeatureGroupIamPolicy (authoritative, replaces entire policy). The examples are intentionally small. Choose the resource that matches your IAM management strategy and combine it with your existing feature groups.
Grant a single user access to a feature group
Most IAM configurations add individual users or service accounts to resources without disrupting existing permissions.
import * as pulumi from "@pulumi/pulumi";
import * as gcp from "@pulumi/gcp";
const member = new gcp.vertex.AiFeatureGroupIamMember("member", {
region: featureGroup.region,
featureGroup: featureGroup.name,
role: "roles/viewer",
member: "user:jane@example.com",
});
import pulumi
import pulumi_gcp as gcp
member = gcp.vertex.AiFeatureGroupIamMember("member",
region=feature_group["region"],
feature_group=feature_group["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.NewAiFeatureGroupIamMember(ctx, "member", &vertex.AiFeatureGroupIamMemberArgs{
Region: pulumi.Any(featureGroup.Region),
FeatureGroup: pulumi.Any(featureGroup.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.AiFeatureGroupIamMember("member", new()
{
Region = featureGroup.Region,
FeatureGroup = featureGroup.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.AiFeatureGroupIamMember;
import com.pulumi.gcp.vertex.AiFeatureGroupIamMemberArgs;
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 AiFeatureGroupIamMember("member", AiFeatureGroupIamMemberArgs.builder()
.region(featureGroup.region())
.featureGroup(featureGroup.name())
.role("roles/viewer")
.member("user:jane@example.com")
.build());
}
}
resources:
member:
type: gcp:vertex:AiFeatureGroupIamMember
properties:
region: ${featureGroup.region}
featureGroup: ${featureGroup.name}
role: roles/viewer
member: user:jane@example.com
The member property specifies the identity to grant access (format: “user:email”, “serviceAccount:email”, “group:email”). The role property defines the permission level. This resource is non-authoritative: it adds the member without removing other members from the same role or affecting other roles on the feature group.
Grant a role to multiple members at once
When multiple identities need the same access level, binding a role to a list is more efficient than individual member resources.
import * as pulumi from "@pulumi/pulumi";
import * as gcp from "@pulumi/gcp";
const binding = new gcp.vertex.AiFeatureGroupIamBinding("binding", {
region: featureGroup.region,
featureGroup: featureGroup.name,
role: "roles/viewer",
members: ["user:jane@example.com"],
});
import pulumi
import pulumi_gcp as gcp
binding = gcp.vertex.AiFeatureGroupIamBinding("binding",
region=feature_group["region"],
feature_group=feature_group["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.NewAiFeatureGroupIamBinding(ctx, "binding", &vertex.AiFeatureGroupIamBindingArgs{
Region: pulumi.Any(featureGroup.Region),
FeatureGroup: pulumi.Any(featureGroup.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.AiFeatureGroupIamBinding("binding", new()
{
Region = featureGroup.Region,
FeatureGroup = featureGroup.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.AiFeatureGroupIamBinding;
import com.pulumi.gcp.vertex.AiFeatureGroupIamBindingArgs;
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 AiFeatureGroupIamBinding("binding", AiFeatureGroupIamBindingArgs.builder()
.region(featureGroup.region())
.featureGroup(featureGroup.name())
.role("roles/viewer")
.members("user:jane@example.com")
.build());
}
}
resources:
binding:
type: gcp:vertex:AiFeatureGroupIamBinding
properties:
region: ${featureGroup.region}
featureGroup: ${featureGroup.name}
role: roles/viewer
members:
- user:jane@example.com
The members property accepts an array of identities. AiFeatureGroupIamBinding is authoritative for the specified role: it sets exactly which members have that role, removing any members not in the list. Other roles on the feature group remain unchanged. You can use AiFeatureGroupIamBinding and AiFeatureGroupIamMember together as long as they don’t grant the same role.
Replace the entire IAM policy for a feature group
Organizations managing IAM centrally often set the complete policy in one operation.
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.vertex.AiFeatureGroupIamPolicy("policy", {
region: featureGroup.region,
featureGroup: featureGroup.name,
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.vertex.AiFeatureGroupIamPolicy("policy",
region=feature_group["region"],
feature_group=feature_group["name"],
policy_data=admin.policy_data)
package main
import (
"github.com/pulumi/pulumi-gcp/sdk/v9/go/gcp/organizations"
"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 {
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 = vertex.NewAiFeatureGroupIamPolicy(ctx, "policy", &vertex.AiFeatureGroupIamPolicyArgs{
Region: pulumi.Any(featureGroup.Region),
FeatureGroup: pulumi.Any(featureGroup.Name),
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.Vertex.AiFeatureGroupIamPolicy("policy", new()
{
Region = featureGroup.Region,
FeatureGroup = featureGroup.Name,
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.vertex.AiFeatureGroupIamPolicy;
import com.pulumi.gcp.vertex.AiFeatureGroupIamPolicyArgs;
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 AiFeatureGroupIamPolicy("policy", AiFeatureGroupIamPolicyArgs.builder()
.region(featureGroup.region())
.featureGroup(featureGroup.name())
.policyData(admin.policyData())
.build());
}
}
resources:
policy:
type: gcp:vertex:AiFeatureGroupIamPolicy
properties:
region: ${featureGroup.region}
featureGroup: ${featureGroup.name}
policyData: ${admin.policyData}
variables:
admin:
fn::invoke:
function: gcp:organizations:getIAMPolicy
arguments:
bindings:
- role: roles/viewer
members:
- user:jane@example.com
The policyData property accepts a complete IAM policy document, typically from the getIAMPolicy data source. AiFeatureGroupIamPolicy is fully authoritative: it replaces all existing bindings on the feature group. This resource cannot be used with AiFeatureGroupIamBinding or AiFeatureGroupIamMember, as they would conflict over policy ownership.
Beyond these examples
These snippets focus on specific IAM management patterns: single-member grants, multi-member role bindings, and full policy replacement. They’re intentionally minimal rather than complete access control configurations.
The examples reference pre-existing infrastructure such as Vertex AI feature groups (by name and region). They focus on IAM binding configuration rather than provisioning the feature groups themselves.
To keep things focused, common IAM patterns are omitted, including:
- Conditional IAM bindings (condition property)
- Custom role definitions
- Cross-project IAM grants (project property)
- Federated identity principals
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 Vertex AI Feature Group IAM Member resource reference for all available configuration options.
Let's manage GCP Vertex AI FeatureGroup IAM Access
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
AiFeatureGroupIamPolicy is authoritative and replaces the entire IAM policy. AiFeatureGroupIamBinding is authoritative for a specific role, preserving other roles. AiFeatureGroupIamMember is non-authoritative, adding individual members while preserving existing members for that role.AiFeatureGroupIamPolicy cannot be used with AiFeatureGroupIamBinding or AiFeatureGroupIamMember as they will conflict. However, AiFeatureGroupIamBinding and AiFeatureGroupIamMember can be used together only if they don’t grant privileges to the same role.featureGroup, member, role, project, region, condition) are immutable and cannot be changed after creation.Configuration & Identity Management
allUsers, allAuthenticatedUsers, user:{email}, serviceAccount:{email}, group:{email}, domain:{domain}, projectOwner/Editor/Viewer:{projectid}, and federated identities (e.g., principal://iam.googleapis.com/...).[projects|organizations]/{parent-name}/roles/{role-name} (e.g., projects/my-project/roles/customRole).Beta & Stability
terraform-provider-google-beta provider. Consider stability requirements before using in production.