AWS batch documentation change
Summary
Updated link text from 'Updating compute environments' to 'Update a compute environment in AWS Batch'
Security assessment
Documentation link text improvement without security implications. No changes to security policies or configurations.
Diff
diff --git a/batch/latest/userguide/allocation-strategies.md b/batch/latest/userguide/allocation-strategies.md index 48893ac8e..fc6e46f47 100644 --- a//batch/latest/userguide/allocation-strategies.md +++ b//batch/latest/userguide/allocation-strategies.md @@ -12 +12 @@ When a managed compute environment is created, AWS Batch selects instance types -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 waits for the additional instances to be available. If there aren't enough instances available, or if the user is reaching the [Amazon EC2 service quotas](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-resource-limits.html), then additional jobs don't run until currently running jobs are complete. This allocation strategy keeps costs lower but can limit scaling. If you're using Spot Fleets with `BEST_FIT`, the Spot Fleet IAM Role must be specified. `BEST_FIT` isn't supported when updating compute environments. For more information, see [Updating compute environments](./updating-compute-environments.html). +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 waits for the additional instances to be available. If there aren't enough instances available, or if the user is reaching the [Amazon EC2 service quotas](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-resource-limits.html), then additional jobs don't run until currently running jobs are complete. This allocation strategy keeps costs lower but can limit scaling. If you're using Spot Fleets with `BEST_FIT`, the Spot Fleet IAM Role must be specified. `BEST_FIT` isn't supported when updating compute environments. For more information, see [Update a compute environment in AWS Batch](./updating-compute-environments.html).