AWS batch documentation change
Summary
Expanded documentation for allowed instance types, added new default_x86_64 and default_arm64 options, updated guidance about instance family selection logic, and announced future behavior change for 'optimal' instance type selection.
Security assessment
The changes focus on instance type selection logic, default bundles, and operational guidance for compute environments. There is no mention of security vulnerabilities, access controls, or encryption. The updates are related to resource management and cost optimization rather than security mechanisms.
Diff
diff --git a/batch/latest/userguide/create-compute-environment-managed-eks.md b/batch/latest/userguide/create-compute-environment-managed-eks.md index 330cb41f4..9545a7aad 100644 --- a//batch/latest/userguide/create-compute-environment-managed-eks.md +++ b//batch/latest/userguide/create-compute-environment-managed-eks.md @@ -49 +49,9 @@ This role is required if the allocation strategy is set to `BEST_FIT` or not spe - 17. For **Allowed instance types** , choose the Amazon EC2 instance types that can be launched. You can specify instance families to launch any instance type within those families (for example, `c5`, `c5n`, or `p3`). Or, you can specify specific sizes within a family (for example, `c5.8xlarge`). Metal instance types aren't in the instance families. For example, `c5` doesn't include `c5.metal`. You can also choose `optimal` to select instance types (from the C4, M4, and R4 instance families) because you need that match the demand of your job queues. + 17. For **Allowed instance types** , choose the Amazon EC2 instance types that can be launched. You can specify instance families to launch any instance type within those families (for example, `c5`, `c5n`, or `p3`). Or, you can specify specific sizes within a family (such as `c5.8xlarge`). Metal instance types aren't in the instance families. For example, `c5` doesn't include `c5.metal`. + +AWS Batch can select the instance type for you if you choose one of the following: + + * `optimal` to select instance types (from the `c4`, `m4`, `r4`, `c5`, `m5`, and `r5` instance families) that match the demand of your job queues. + + * `default_x86_64` to choose x86 based instance types (from the m6i, c6i, r6i, and c7i instance families) that matches the resource demands of the job queue. + + * `default_arm64` to choose x86 based instance types (from the m6g, c6g, r6g, and c7g instance families) that matches the resource demands of the job queue. @@ -53 +61 @@ This role is required if the allocation strategy is set to `BEST_FIT` or not spe -When you create a compute environment, the instance types that you select for the compute environment must share the same architecture. For example, you can't mix x86 and ARM instances in the same compute environment. +Starting on 11/01/2025 the behavior of `optimal` is going to be changed to match `default_x86_64`. During the change your instance families could be updated to a newer generation. You do not need to perform any actions for the upgrade to happen. For more information about change, see [Optimal instance type configuration to receive automatic instance family updates](./optimal-default-instance-troubleshooting.html). @@ -57 +65,9 @@ When you create a compute environment, the instance types that you select for th -AWS Batch scales GPUs based on the required amount in your job queues. To use GPU scheduling, the compute environment must include instance types from the `p3`, `p4`, `p5`, `p6`, `g3`, `g3s`, `g4`, `g5`, or `g6` families. + * Instance family availability varies by AWS Region. For example, some AWS Regions may not have any fourth generation instance families but have fifth and sixth generation instance families. + + * When using `default_x86_64` or `default_arm64` instance bundles, AWS Batch selects instance families based on a balance of cost-effectiveness and performance. While newer generation instances often provide better price-performance, AWS Batch may choose an earlier generation instance family if it provides the optimal combination of availability, cost, and performance for your workload. For example, in an AWS Region where both c6i and c7i instances are available, AWS Batch might select c6i instances if they offer better cost-effectiveness for your specific job requirements. For more information on AWS Batch instance types and AWS Region availability, see [Instance type compute table](./instance-type-compute-table.html#instance-type-compute-table.title). + + * AWS Batch periodically updates your instances in default bundles to newer, more cost-effective options. Updates happen automatically without requiring any action from you. Your workloads continue running during updates with no interruption + +###### Note + +When you create a compute environment, the instance types that you select for the compute environment must share the same architecture. For example, you can't mix x86 and ARM instances in the same compute environment. @@ -61 +77 @@ AWS Batch scales GPUs based on the required amount in your job queues. To use GP -Currently, `optimal` uses instance types from the C4, M4, and R4 instance families. In AWS Regions that don't have instance types from those instance families, instance types from the C5, M5, and R5 instance families are used. +AWS Batch will scale GPUs based on the required amount in your job queues. To use GPU scheduling, the compute environment must include instance types from the `p3`, `p4`, `p5`, `p6`, `g3`, `g3s`, `g4`, `g5`, or `g6` families.