AWS batch documentation change
Summary
Added two new allocation strategies (BEST_FIT_PROGRESSIVE_ORDERED, SPOT_CAPACITY_OPTIMIZED_PRIORITIZED) to infrastructure update requirements
Security assessment
Expands feature compatibility without security implications. No vulnerabilities or security features mentioned in the change.
Diff
diff --git a/batch/latest/userguide/infrastructure-updates.md b/batch/latest/userguide/infrastructure-updates.md index d3e3f65f5..521542806 100644 --- a//batch/latest/userguide/infrastructure-updates.md +++ b//batch/latest/userguide/infrastructure-updates.md @@ -15 +15 @@ Infrastructure updates replace the instances in your compute environment with ne -Infrastructure updates require the _AWSServiceRoleForBatch_ service-linked role and an allocation strategy of `BEST_FIT_PROGRESSIVE`, `SPOT_CAPACITY_OPTIMIZED`, or `SPOT_PRICE_CAPACITY_OPTIMIZED`. If your environment doesn't meet these requirements, use blue/green updates instead. +Infrastructure updates require the _AWSServiceRoleForBatch_ service-linked role and an allocation strategy of `BEST_FIT_PROGRESSIVE`, `BEST_FIT_PROGRESSIVE_ORDERED`, `SPOT_CAPACITY_OPTIMIZED`, `SPOT_PRICE_CAPACITY_OPTIMIZED`, or `SPOT_CAPACITY_OPTIMIZED_PRIORITIZED`. If your environment doesn't meet these requirements, use blue/green updates instead.