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

    Interface EmrEksTeamProps

    Interface to define a EMR on EKS team

    interface EmrEksTeamProps {
        createNamespace: boolean;
        executionRoles: ExecutionRoleDefinition[];
        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[];
        virtualClusterName: string;
        virtualClusterNamespace: string;
        virtualClusterTags?: CfnTag[];
        extensionFunction(team: ApplicationTeam, clusterInfo: ClusterInfo): void;
    }

    Hierarchy (View Summary)

    Index

    Properties

    createNamespace: boolean

    To define if the namespace that team will use need to be created

    executionRoles: ExecutionRoleDefinition[]

    List of execution role to associated with the VC namespace ExecutionRoleDefinition

    name: string

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

    namespace?: string

    Defaults to team name prefixed by "team-"

    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

    Service Account Name

    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

    virtualClusterName: string
    virtualClusterNamespace: string
    virtualClusterTags?: CfnTag[]

    Tags to apply to EMR on EKS Virtual Cluster

    Methods