AWS Batch now supports default instance type options

As of today, AWS Batch has introduced two new instance type options for allowed instance types in Compute Environment default-x86_64 (default) and default-arm64. These new options will automatically select the most cost-effective instance type across different generations, based on your job queue requirements, where AWS Batch previously supported only optimal instance type. This makes it easier to run your Batch workloads with newer generation EC2 instance families and can provide better performance at a lower cost. As new instance types become available in a region, they’ll be automatically added to the corresponding default pool.

To get started, you can select default-x86_64 or default-arm64 in the instanceType parameter for managed compute environments. There is no need to create a new compute environment—the existing ‘optimal’ option (which applies to M, C, and R EC2 instance familes) will continue to be supported and is not being deprecated, no action is needed. However, please be aware that only ENABLED and VALID Compute Environments (CEs) will be automatically updated with new instance types. If you have any DISABLED or INVALID CEs, they will receive updates once they are re-enabled and set to a VALID state.

This capability is now available for AWS Batch in all commercial and the AWS GovCloud (US) Regions. To learn more, see our launch blog, visit Batch’s documentation page or the Batch troubleshooting User Guide.

Categories: general:products/aws-batch,marketing:marchitecture/compute,marketing:marchitecture/containers

Source: Amazon Web Services

Latest Posts