aws-sdk-batch 1.123.0 → 1.125.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: c560cb648777e2156384c922b49c36f15ffdbb8b0548d09909a291463ecd6655
-  data.tar.gz: 50cfe6589e5020909ace1268fb3d3fb5b9eaf4cb81a401e7cf7b1d7f4060c5f2
+  metadata.gz: f3a86b542489f35f255b75c20e94c52954681f6a846e308818639a9917f2dcf8
+  data.tar.gz: 6d7d4dce21fd84db93c9bc408b6178423b0187e2b37c014b8fac63cec8a4fa97
 SHA512:
-  metadata.gz: 8f10e106c1bafd0ef4dc2ce87c893defd8a0a76130cbc5274545138feeebe1c5d7513620d5b9d00028ea75bad7e07925d1858e81a15846907994c2f1c44e2373
-  data.tar.gz: dd33d7cbd53f6e351e0bf2d9b89e76781ca9ae29d09eb0a23c8e1604ddd3fcbcaf990ad2374a651c65ef2b574742681144fc932ba93ba2c1ebf05439ca20d4d9
+  metadata.gz: 3d77f9fc9e24d5bbcadbf65b1d5d588fccbbf0601bb8d1844f2a200f56b5a01ac773d527c0005b246119ba83cea6cc6211830b03f42391ed2ec387cef459dd1e
+  data.tar.gz: f73dfe5ba44f036b492dc70946c0d97d8167e4e4c2e6665bc031f98234b57b4679be126b2553fb9cdbae707aee1637f33a8d9e85fcec621463cadb42d64546e0

data/CHANGELOG.md

@@ -1,6 +1,16 @@
 Unreleased Changes
 ------------------
 
+1.125.0 (2025-09-22)
+------------------
+
+* Feature - Starting in JAN 2026, AWS Batch will change the default AMI for new Amazon ECS compute environments from Amazon Linux 2 to Amazon Linux 2023. We recommend migrating AWS Batch Amazon ECS compute environments to Amazon Linux 2023 to maintain optimal performance and security.
+
+1.124.0 (2025-08-27)
+------------------
+
+* Feature - Added ECS_AL2023_NVIDIA as an option for Ec2Configuration.imageType.
+
 1.123.0 (2025-08-26)
 ------------------
 

data/VERSION

@@ -1 +1 @@
-1.123.0
+1.125.0

data/lib/aws-sdk-batch/client.rb

@@ -552,10 +552,6 @@ module Aws::Batch
     # price so that Spot Instances only launch when the Spot Instance price
     # is less than a specified percentage of the On-Demand price.
     #
-    # <note markdown="1"> Multi-node parallel jobs aren't supported on Spot Instances.
-    #
-    #  </note>
-    #
     # In an unmanaged compute environment, you can manage your own EC2
     # compute resources and have flexibility with how you configure your
     # compute resources. For example, you can use custom AMIs. However, you
@@ -569,69 +565,10 @@ module Aws::Batch
     # [Launching an Amazon ECS container instance][3] in the *Amazon Elastic
     # Container Service Developer Guide*.
     #
-    # <note markdown="1"> To create a compute environment that uses EKS resources, the caller
-    # must have permissions to call `eks:DescribeCluster`.
-    #
-    #  </note>
-    #
     # <note markdown="1"> Batch doesn't automatically upgrade the AMIs in a compute environment
-    # after it's created. For example, it also doesn't update the AMIs in
-    # your compute environment when a newer version of the Amazon ECS
-    # optimized AMI is available. You're responsible for the management of
-    # the guest operating system. This includes any updates and security
-    # patches. You're also responsible for any additional application
-    # software or utilities that you install on the compute resources. There
-    # are two ways to use a new AMI for your Batch jobs. The original method
-    # is to complete these steps:
-    #
-    #  1.  Create a new compute environment with the new AMI.
-    #
-    # 2.  Add the compute environment to an existing job queue.
-    #
-    # 3.  Remove the earlier compute environment from your job queue.
-    #
-    # 4.  Delete the earlier compute environment.
-    #
-    #  In April 2022, Batch added enhanced support for updating compute
-    # environments. For more information, see [Updating compute
-    # environments][4]. To use the enhanced updating of compute environments
-    # to update AMIs, follow these rules:
-    #
-    #  * Either don't set the service role (`serviceRole`) parameter or set
-    #   it to the **AWSBatchServiceRole** service-linked role.
-    #
-    # * Set the allocation strategy (`allocationStrategy`) parameter to
-    #   `BEST_FIT_PROGRESSIVE`, `SPOT_CAPACITY_OPTIMIZED`, or
-    #   `SPOT_PRICE_CAPACITY_OPTIMIZED`.
-    #
-    # * Set the update to latest image version
-    #   (`updateToLatestImageVersion`) parameter to `true`. The
-    #   `updateToLatestImageVersion` parameter is used when you update a
-    #   compute environment. This parameter is ignored when you create a
-    #   compute environment.
-    #
-    # * Don't specify an AMI ID in `imageId`, `imageIdOverride` (in [
-    #   `ec2Configuration` ][5]), or in the launch template
-    #   (`launchTemplate`). In that case, Batch selects the latest Amazon
-    #   ECS optimized AMI that's supported by Batch at the time the
-    #   infrastructure update is initiated. Alternatively, you can specify
-    #   the AMI ID in the `imageId` or `imageIdOverride` parameters, or the
-    #   launch template identified by the `LaunchTemplate` properties.
-    #   Changing any of these properties starts an infrastructure update. If
-    #   the AMI ID is specified in the launch template, it can't be
-    #   replaced by specifying an AMI ID in either the `imageId` or
-    #   `imageIdOverride` parameters. It can only be replaced by specifying
-    #   a different launch template, or if the launch template version is
-    #   set to `$Default` or `$Latest`, by setting either a new default
-    #   version for the launch template (if `$Default`) or by adding a new
-    #   version to the launch template (if `$Latest`).
-    #
-    #  If these rules are followed, any update that starts an infrastructure
-    # update causes the AMI ID to be re-selected. If the `version` setting
-    # in the launch template (`launchTemplate`) is set to `$Latest` or
-    # `$Default`, the latest or default version of the launch template is
-    # evaluated up at the time of the infrastructure update, even if the
-    # `launchTemplate` wasn't updated.
+    # after it's created. For more information on how to update a compute
+    # environment's AMI, see [Updating compute environments][4] in the
+    # *Batch User Guide*.
     #
     #  </note>
     #
@@ -641,7 +578,6 @@ module Aws::Batch
     # [2]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/container_instance_AMIs.html
     # [3]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/launch_container_instance.html
     # [4]: https://docs.aws.amazon.com/batch/latest/userguide/updating-compute-environments.html
-    # [5]: https://docs.aws.amazon.com/batch/latest/APIReference/API_Ec2Configuration.html
     #
     # @option params [required, String] :compute_environment_name
     #   The name for your compute environment. It can be up to 128 characters
@@ -764,6 +700,11 @@ module Aws::Batch
     #   The details for the Amazon EKS cluster that supports the compute
     #   environment.
     #
+    #   <note markdown="1"> To create a compute environment that uses EKS resources, the caller
+    #   must have permissions to call `eks:DescribeCluster`.
+    #
+    #    </note>
+    #
     # @option params [String] :context
     #   Reserved.
     #
@@ -5433,7 +5374,7 @@ module Aws::Batch
     #
     # @option params [String] :share_identifier
     #   The share identifier for the service job. Don't specify this
-    #   parameter if the job queue doesn't have a fair- share scheduling
+    #   parameter if the job queue doesn't have a fair-share scheduling
     #   policy. If the job queue has a fair-share scheduling policy, then this
     #   parameter must be specified.
     #
@@ -6189,7 +6130,7 @@ module Aws::Batch
         tracer: tracer
       )
       context[:gem_name] = 'aws-sdk-batch'
-      context[:gem_version] = '1.123.0'
+      context[:gem_version] = '1.125.0'
       Seahorse::Client::Request.new(handlers, context)
     end
 

data/lib/aws-sdk-batch/types.rb

@@ -504,6 +504,10 @@ module Aws::Batch
     #   role with the `spotIamFleetRole` parameter. For more information,
     #   see [Amazon EC2 spot fleet role][2] in the *Batch User Guide*.
     #
+    #   <note markdown="1"> Multi-node parallel jobs aren't supported on Spot Instances.
+    #
+    #    </note>
+    #
     #
     #
     #   [1]: https://docs.aws.amazon.com/batch/latest/userguide/compute_environments.html
@@ -2415,6 +2419,11 @@ module Aws::Batch
     # @!attribute [rw] eks_configuration
     #   The details for the Amazon EKS cluster that supports the compute
     #   environment.
+    #
+    #   <note markdown="1"> To create a compute environment that uses EKS resources, the caller
+    #   must have permissions to call `eks:DescribeCluster`.
+    #
+    #    </note>
     #   @return [Types::EksConfiguration]
     #
     # @!attribute [rw] context
@@ -3562,52 +3571,82 @@ module Aws::Batch
     #     latest Amazon ECS optimized AMI for that image type that's
     #     supported by Batch is used.
     #
+    #     Amazon Web Services will end support for Amazon ECS optimized
+    #     AL2-optimized and AL2-accelerated AMIs. Starting in January 2026,
+    #     Batch will change the default AMI for new Amazon ECS compute
+    #     environments from Amazon Linux 2 to Amazon Linux 2023. We
+    #     recommend migrating Batch Amazon ECS compute environments to
+    #     Amazon Linux 2023 to maintain optimal performance and security.
+    #     For more information on upgrading from AL2 to AL2023, see [How to
+    #     migrate from ECS AL2 to ECS AL2023][2] in the *Batch User Guide*.
+    #
     #     ECS\_AL2
     #
     #     : [Amazon Linux 2][1]: Default for all non-GPU instance families.
     #
     #     ECS\_AL2\_NVIDIA
     #
-    #     : [Amazon Linux 2 (GPU)][2]: Default for all GPU instance families
+    #     : [Amazon Linux 2 (GPU)][3]: Default for all GPU instance families
     #       (for example `P4` and `G4`) and can be used for all non Amazon
     #       Web Services Graviton-based instance types.
     #
     #     ECS\_AL2023
     #
-    #     : [Amazon Linux 2023][3]: Batch supports Amazon Linux 2023.
+    #     : [Amazon Linux 2023][4]: Batch supports Amazon Linux 2023.
     #
     #       <note markdown="1"> Amazon Linux 2023 does not support `A1` instances.
     #
     #        </note>
     #
-    #     ECS\_AL1
+    #     ECS\_AL2023\_NVIDIA
+    #
+    #     : [Amazon Linux 2023 (GPU)][3]: For all GPU instance families and
+    #       can be used for all non Amazon Web Services Graviton-based
+    #       instance types.
+    #
+    #       <note markdown="1"> ECS\_AL2023\_NVIDIA doesn't support `p3` and `g3` instance
+    #       types.
     #
-    #     : [Amazon Linux][4]. Amazon Linux has reached the end-of-life of
-    #       standard support. For more information, see [Amazon Linux
-    #       AMI][5].
+    #        </note>
     #
     #   EKS
     #
     #   : If the `imageIdOverride` parameter isn't specified, then a recent
-    #     [Amazon EKS-optimized Amazon Linux AMI][6] (`EKS_AL2`) is used. If
+    #     [Amazon EKS-optimized Amazon Linux AMI][5] (`EKS_AL2`) is used. If
     #     a new image type is specified in an update, but neither an
     #     `imageId` nor a `imageIdOverride` parameter is specified, then the
     #     latest Amazon EKS optimized AMI for that image type that Batch
     #     supports is used.
     #
+    #     Starting end of October 2025 Amazon EKS optimized Amazon Linux
+    #     2023 AMIs will be the default on Batch for EKS versions prior to
+    #     1.33. Starting from Kubernetes version 1.33, EKS optimized Amazon
+    #     Linux 2023 AMIs will be the default when it becomes supported on
+    #     Batch.
+    #
+    #      Amazon Web Services will end support for Amazon EKS AL2-optimized
+    #     and AL2-accelerated AMIs, starting 11/26/25. You can continue
+    #     using Batch-provided Amazon EKS optimized Amazon Linux 2 AMIs on
+    #     your Amazon EKS compute environments beyond the 11/26/25
+    #     end-of-support date, these compute environments will no longer
+    #     receive any new software updates, security patches, or bug fixes
+    #     from Amazon Web Services. For more information on upgrading from
+    #     AL2 to AL2023, see [How to upgrade from EKS AL2 to EKS AL2023][6]
+    #     in the *Batch User Guide*.
+    #
     #     EKS\_AL2
     #
-    #     : [Amazon Linux 2][6]: Default for all non-GPU instance families.
+    #     : [Amazon Linux 2][5]: Default for all non-GPU instance families.
     #
     #     EKS\_AL2\_NVIDIA
     #
-    #     : [Amazon Linux 2 (accelerated)][6]: Default for all GPU instance
+    #     : [Amazon Linux 2 (accelerated)][5]: Default for all GPU instance
     #       families (for example, `P4` and `G4`) and can be used for all
     #       non Amazon Web Services Graviton-based instance types.
     #
     #     EKS\_AL2023
     #
-    #     : [Amazon Linux 2023][6]: Batch supports Amazon Linux 2023.
+    #     : [Amazon Linux 2023][5]: Batch supports Amazon Linux 2023.
     #
     #       <note markdown="1"> Amazon Linux 2023 does not support `A1` instances.
     #
@@ -3615,18 +3654,18 @@ module Aws::Batch
     #
     #     EKS\_AL2023\_NVIDIA
     #
-    #     : [Amazon Linux 2023 (accelerated)][6]: GPU instance families and
+    #     : [Amazon Linux 2023 (accelerated)][5]: GPU instance families and
     #       can be used for all non Amazon Web Services Graviton-based
     #       instance types.
     #
     #
     #
     #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-optimized_AMI.html#al2ami
-    #   [2]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-optimized_AMI.html#gpuami
-    #   [3]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-optimized_AMI.html
-    #   [4]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-optimized_AMI.html#alami
-    #   [5]: http://aws.amazon.com/amazon-linux-ami/
-    #   [6]: https://docs.aws.amazon.com/eks/latest/userguide/eks-optimized-ami.html
+    #   [2]: https://docs.aws.amazon.com/batch/latest/userguide/ecs-migration-2023.html
+    #   [3]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-optimized_AMI.html#gpuami
+    #   [4]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-optimized_AMI.html
+    #   [5]: https://docs.aws.amazon.com/eks/latest/userguide/eks-optimized-ami.html
+    #   [6]: https://docs.aws.amazon.com/batch/latest/userguide/eks-migration-2023.html
     #   @return [String]
     #
     # @!attribute [rw] image_id_override
@@ -3756,6 +3795,12 @@ module Aws::Batch
     #
     # @!attribute [rw] ipc_mode
     #   The IPC resource namespace to use for the containers in the task.
+    #   The valid values are `host`, `task`, or `none`. For more information
+    #   see `ipcMode` in [EcsTaskProperties][1].
+    #
+    #
+    #
+    #   [1]: https://docs.aws.amazon.com/batch/latest/APIReference/API_EcsTaskProperties.html
     #   @return [String]
     #
     # @!attribute [rw] task_role_arn
@@ -3775,7 +3820,13 @@ module Aws::Batch
     #   @return [String]
     #
     # @!attribute [rw] pid_mode
-    #   The process namespace to use for the containers in the task.
+    #   The process namespace to use for the containers in the task. The
+    #   valid values are `host`, or `task`. For more information see
+    #   `pidMode` in [EcsTaskProperties][1].
+    #
+    #
+    #
+    #   [1]: https://docs.aws.amazon.com/batch/latest/APIReference/API_EcsTaskProperties.html
     #   @return [String]
     #
     # @!attribute [rw] network_configuration
@@ -7229,8 +7280,9 @@ module Aws::Batch
     #   listed for this parameter are log drivers that the Amazon ECS
     #   container agent can communicate with by default.
     #
-    #   The supported log drivers are `awslogs`, `fluentd`, `gelf`,
-    #   `json-file`, `journald`, `logentries`, `syslog`, and `splunk`.
+    #   The supported log drivers are `awsfirelens`, `awslogs`, `fluentd`,
+    #   `gelf`, `json-file`, `journald`, `logentries`, `syslog`, and
+    #   `splunk`.
     #
     #   <note markdown="1"> Jobs that are running on Fargate resources are restricted to the
     #   `awslogs` and `splunk` log drivers.
@@ -8534,7 +8586,7 @@ module Aws::Batch
     #   for share identifiers that start with that prefix. The list of share
     #   identifiers in a fair-share policy can't overlap. For example, you
     #   can't have one that specifies a `shareIdentifier` of `UserA*` and
-    #   another that specifies a `shareIdentifier` of `UserA-1`.
+    #   another that specifies a `shareIdentifier` of `UserA1`.
     #
     #   There can be no more than 500 share identifiers active in a job
     #   queue.
@@ -8800,7 +8852,7 @@ module Aws::Batch
     #
     # @!attribute [rw] share_identifier
     #   The share identifier for the service job. Don't specify this
-    #   parameter if the job queue doesn't have a fair- share scheduling
+    #   parameter if the job queue doesn't have a fair-share scheduling
     #   policy. If the job queue has a fair-share scheduling policy, then
     #   this parameter must be specified.
     #   @return [String]

data/lib/aws-sdk-batch.rb

@@ -54,7 +54,7 @@ module Aws::Batch
   autoload :EndpointProvider, 'aws-sdk-batch/endpoint_provider'
   autoload :Endpoints, 'aws-sdk-batch/endpoints'
 
-  GEM_VERSION = '1.123.0'
+  GEM_VERSION = '1.125.0'
 
 end
 

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: aws-sdk-batch
 version: !ruby/object:Gem::Version
-  version: 1.123.0
+  version: 1.125.0
 platform: ruby
 authors:
 - Amazon Web Services