Compute Environment compute resources
Allocation strategies for EKS Compute environment - see enum Allocation for options.
Compute Environment resources Type - see enum BatchEnvType for options
List of instance types - can be a list that contains Instance Type family (i.e. "m5") or a specific Type (i.e. "m5.4xlarge")
The maximum number of Amazon EC2 vCPUs that an environment can reach.
The minimum number of Amazon EC2 vCPUs that an environment should maintain.
Priority of the job queue - priority is set in descending order
Compute Environment name
Name of the Job Queue
Readonly
nameRequired unique name for organization. May map to an OU name.
Optional
Readonly
namespaceDefaults to team name prefixed by "team-"
Optional
Readonly
namespaceAnnotations such as necessary for GitOps engine.
Optional
Readonly
namespaceOptional, but highly recommended setting to ensure predictable demands.
Optional
Readonly
namespaceLabels such as necessary for AWS AppMesh
Optional
Readonly
serviceService Account Name
Optional
Readonly
serviceIf specified, the IRSA account will be created for with the IRSA role having the specified managed policies.
Optional
Readonly
teamOptional, directory where a team's manifests are stored
Optional
Readonly
teamTeam Secrets
Optional
Readonly
userOptions existing role that should be used for cluster access. If userRole and users are not provided, then no IAM setup is performed.
Optional
Readonly
usersTeam members who need to get access to the cluster
Optional
extensionOptional, Use this function to add infrastructure or workloads deploymentto the team
Interface to define an AWS Batch on EKS team