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
ReadonlynameRequired unique name for organization. May map to an OU name.
Optional ReadonlynamespaceDefaults to team name prefixed by "team-"
Optional ReadonlynamespaceAnnotations such as necessary for GitOps engine.
Optional ReadonlynamespaceOptional, but highly recommended setting to ensure predictable demands.
Optional ReadonlynamespaceLabels such as necessary for AWS AppMesh
Optional ReadonlyserviceService Account Name
Optional ReadonlyserviceIf specified, the IRSA account will be created for with the IRSA role having the specified managed policies.
Optional ReadonlyteamOptional, directory where a team's manifests are stored
Optional ReadonlyteamTeam Secrets
Optional ReadonlyuserOptions existing role that should be used for cluster access. If userRole and users are not provided, then no IAM setup is performed.
Optional ReadonlyusersTeam members who need to get access to the cluster
OptionalextensionOptional, Use this function to add infrastructure or workloads deploymentto the team
Interface to define an AWS Batch on EKS team