@aws-quickstart/eks-blueprints
    Preparing search index...

    Interface BedrockTeamProps

    Interface to define a GenAI on EKS team

    interface BedrockTeamProps {
        createNamespace?: boolean;
        name: string;
        namespace?: string;
        namespaceAnnotations?: { [key: string]: any };
        namespaceHardLimits?: Values;
        namespaceLabels?: { [key: string]: any };
        serviceAccountName?: string;
        serviceAccountPolicies?: IManagedPolicy[];
        teamManifestDir?: string;
        teamSecrets?: CsiSecretProps[];
        userRoleArn?: string;
        users?: ArnPrincipal[];
        extensionFunction?(team: ApplicationTeam, clusterInfo: ClusterInfo): void;
    }

    Hierarchy (View Summary)

    Index

    Properties

    createNamespace? name namespace? namespaceAnnotations? namespaceHardLimits? namespaceLabels? serviceAccountName? serviceAccountPolicies? teamManifestDir? teamSecrets? userRoleArn? users?

    Methods

    extensionFunction?

    Properties

    createNamespace?: boolean

    Create Namespace with the provided one.

    name: string

    Required unique name for organization. May map to an OU name.

    namespace?: string

    Name of the service account namespace.

    namespaceAnnotations?: { [key: string]: any } = ...

    Annotations such as necessary for GitOps engine.

    namespaceHardLimits?: Values = ...

    Optional, but highly recommended setting to ensure predictable demands.

    namespaceLabels?: { [key: string]: any }

    Labels such as necessary for AWS AppMesh

    serviceAccountName?: string

    Name of the service account for Bedrock.

    serviceAccountPolicies?: IManagedPolicy[]

    If specified, the IRSA account will be created for with the IRSA role having the specified managed policies.

    serviceAccountPolicies: [ManagedPolicy.fromAwsManagedPolicyName("")]
    teamManifestDir?: string

    Optional, directory where a team's manifests are stored

    teamSecrets?: CsiSecretProps[]

    Team Secrets

    userRoleArn?: string

    Options existing role that should be used for cluster access. If userRole and users are not provided, then no IAM setup is performed.

    users?: ArnPrincipal[]

    Team members who need to get access to the cluster

    Methods

    Settings

    Member Visibility

    On This Page

    Properties
    Methods