allocationStrategy property
The allocation strategy to use for the compute resource if not enough instances of the best fitting instance type can be allocated. This might be because of availability of the instance type in the Region or Amazon EC2 service limits. For more information, see Allocation Strategies in the AWS Batch User Guide.
- BEST_FIT (default)
-
AWS Batch selects an instance type that best fits the needs of the jobs with
a preference for the lowest-cost instance type. If additional instances of
the selected instance type aren't available, AWS Batch will wait for the
additional instances to be available. If there are not enough instances
available, or if the user is hitting Amazon
EC2 service limits then additional jobs aren't run until currently
running jobs have completed. This allocation strategy keeps costs lower but
can limit scaling. If you are using Spot Fleets with
BEST_FITthen the Spot Fleet IAM Role must be specified. - BEST_FIT_PROGRESSIVE
- AWS Batch will select additional instance types that are large enough to meet the requirements of the jobs in the queue, with a preference for instance types with a lower cost per unit vCPU. If additional instances of the previously selected instance types aren't available, AWS Batch will select new instance types.
- SPOT_CAPACITY_OPTIMIZED
- AWS Batch will select one or more instance types that are large enough to meet the requirements of the jobs in the queue, with a preference for instance types that are less likely to be interrupted. This allocation strategy is only available for Spot Instance compute resources.
BEST_FIT_PROGRESSIVE and
SPOT_CAPACITY_OPTIMIZED strategies, AWS Batch might need to go
above maxvCpus to meet your capacity requirements. In this
event, AWS Batch never exceeds maxvCpus by more than a single
instance.
Implementation
final CRAllocationStrategy? allocationStrategy;