aws-sdk-batch 1.144.0 → 1.146.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 6e1769208c8e8bc916b45290e42bebf9e59ccec70353136bc3d4698c1a711470
-  data.tar.gz: 46e8f337808ac430dcdcb7a2d3cfb8a5dbe0b649e9f0d9d573e9c59842886dcb
+  metadata.gz: c3ddedba3974e2b5f747a4f18336fd8de83533d542fcfe290ac473dc11e942e6
+  data.tar.gz: 5f648d487d55890879fa37dd1ffa93212c3320183fd5926a1642d5b6ea09e521
 SHA512:
-  metadata.gz: 1563f29b6bcc2f97537573a881169c0684ad8566661459dc88b2074e7b436c4738c8d75248477d0c21488dc40698e68dd18835b8838b71f5fdb6ef1ae1e4c651
-  data.tar.gz: 2990fa9c0bdcdfcdb75b902c6bd2d64d07e037715e41e336a6786763ceb5a248278004626ea1166eeb74055b1bba23aa144d91851fc9df0f4fb1a827043c4bc4
+  metadata.gz: 117ccf60dc8370146dfe38c553d738e09d2719d1d06ad24c258bdfaf379faaf2d7928e66cb8b59363d3b2c8f3ec804f022aef86dc9da1298ce207c0e7cc98f1a
+  data.tar.gz: 73a80b0c21847bce7970d45f4f4ad221105c57ae9083dc639efaed16c56d00ae5da7d4e17a67c10666a7b091e735d220a1b4f42e333a9201da3cdd9b27b1c30e

data/CHANGELOG.md

@@ -1,6 +1,16 @@
 Unreleased Changes
 ------------------
 
+1.146.0 (2026-06-18)
+------------------
+
+* Feature - Adds Support for ordered allocation strategies- BEST-FIT-PROGRESSIVE-ORDERED or SPOT-CAPACITY-OPTIMIZED-PRIORITIZED
+
+1.145.0 (2026-05-26)
+------------------
+
+* Feature - Increase the maximum value of jobExecutionTimeoutMinutes to support longer job timeouts during compute environment infrastructure updates.
+
 1.144.0 (2026-05-21)
 ------------------
 

data/VERSION

@@ -1 +1 @@
-1.144.0
+1.146.0

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

@@ -810,13 +810,13 @@ module Aws::Batch
     #     unmanagedv_cpus: 1,
     #     compute_resources: {
     #       type: "EC2", # required, accepts EC2, SPOT, FARGATE, FARGATE_SPOT
-    #       allocation_strategy: "BEST_FIT", # accepts BEST_FIT, BEST_FIT_PROGRESSIVE, SPOT_CAPACITY_OPTIMIZED, SPOT_PRICE_CAPACITY_OPTIMIZED
+    #       allocation_strategy: "BEST_FIT", # accepts BEST_FIT, BEST_FIT_PROGRESSIVE, BEST_FIT_PROGRESSIVE_ORDERED, SPOT_CAPACITY_OPTIMIZED, SPOT_PRICE_CAPACITY_OPTIMIZED, SPOT_CAPACITY_OPTIMIZED_PRIORITIZED
     #       minv_cpus: 1,
     #       maxv_cpus: 1, # required
     #       desiredv_cpus: 1,
     #       instance_types: ["String"],
     #       image_id: "String",
-    #       subnets: ["String"], # required
+    #       subnets: ["String"],
     #       security_group_ids: ["String"],
     #       ec2_key_pair: "String",
     #       instance_role: "String",
@@ -1721,7 +1721,7 @@ module Aws::Batch
     #   resp.compute_environments[0].status #=> String, one of "CREATING", "UPDATING", "DELETING", "DELETED", "VALID", "INVALID"
     #   resp.compute_environments[0].status_reason #=> String
     #   resp.compute_environments[0].compute_resources.type #=> String, one of "EC2", "SPOT", "FARGATE", "FARGATE_SPOT"
-    #   resp.compute_environments[0].compute_resources.allocation_strategy #=> String, one of "BEST_FIT", "BEST_FIT_PROGRESSIVE", "SPOT_CAPACITY_OPTIMIZED", "SPOT_PRICE_CAPACITY_OPTIMIZED"
+    #   resp.compute_environments[0].compute_resources.allocation_strategy #=> String, one of "BEST_FIT", "BEST_FIT_PROGRESSIVE", "BEST_FIT_PROGRESSIVE_ORDERED", "SPOT_CAPACITY_OPTIMIZED", "SPOT_PRICE_CAPACITY_OPTIMIZED", "SPOT_CAPACITY_OPTIMIZED_PRIORITIZED"
     #   resp.compute_environments[0].compute_resources.minv_cpus #=> Integer
     #   resp.compute_environments[0].compute_resources.maxv_cpus #=> Integer
     #   resp.compute_environments[0].compute_resources.desiredv_cpus #=> Integer
@@ -6185,7 +6185,7 @@ module Aws::Batch
     #       desiredv_cpus: 1,
     #       subnets: ["String"],
     #       security_group_ids: ["String"],
-    #       allocation_strategy: "BEST_FIT_PROGRESSIVE", # accepts BEST_FIT_PROGRESSIVE, SPOT_CAPACITY_OPTIMIZED, SPOT_PRICE_CAPACITY_OPTIMIZED
+    #       allocation_strategy: "BEST_FIT_PROGRESSIVE", # accepts BEST_FIT_PROGRESSIVE, BEST_FIT_PROGRESSIVE_ORDERED, SPOT_CAPACITY_OPTIMIZED, SPOT_PRICE_CAPACITY_OPTIMIZED, SPOT_CAPACITY_OPTIMIZED_PRIORITIZED
     #       instance_types: ["String"],
     #       ec2_key_pair: "String",
     #       instance_role: "String",
@@ -6664,7 +6664,7 @@ module Aws::Batch
         tracer: tracer
       )
       context[:gem_name] = 'aws-sdk-batch'
-      context[:gem_version] = '1.144.0'
+      context[:gem_version] = '1.146.0'
       Seahorse::Client::Request.new(handlers, context)
     end
 

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

@@ -468,7 +468,7 @@ module Aws::Batch
     ComputeResource.add_member(:desiredv_cpus, Shapes::ShapeRef.new(shape: Integer, location_name: "desiredvCpus"))
     ComputeResource.add_member(:instance_types, Shapes::ShapeRef.new(shape: StringList, location_name: "instanceTypes"))
     ComputeResource.add_member(:image_id, Shapes::ShapeRef.new(shape: String, deprecated: true, location_name: "imageId", metadata: {"deprecatedMessage" => "This field is deprecated, use ec2Configuration[].imageIdOverride instead."}))
-    ComputeResource.add_member(:subnets, Shapes::ShapeRef.new(shape: StringList, required: true, location_name: "subnets"))
+    ComputeResource.add_member(:subnets, Shapes::ShapeRef.new(shape: StringList, location_name: "subnets"))
     ComputeResource.add_member(:security_group_ids, Shapes::ShapeRef.new(shape: StringList, location_name: "securityGroupIds"))
     ComputeResource.add_member(:ec2_key_pair, Shapes::ShapeRef.new(shape: String, location_name: "ec2KeyPair"))
     ComputeResource.add_member(:instance_role, Shapes::ShapeRef.new(shape: String, location_name: "instanceRole"))

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

@@ -582,6 +582,31 @@ module Aws::Batch
     #     of the previously selected instance types aren't available, Batch
     #     selects new instance types.
     #
+    #   BEST\_FIT\_PROGRESSIVE\_ORDERED
+    #
+    #   : This is an advanced allocation strategy only for customers who
+    #     want to control which instance types are preferred during scaling.
+    #
+    #      Placing large instance types at the top of the list may result in
+    #     **over-provisioning** for small jobs. Placing small instance types
+    #     at the top may cause the compute environment to reach Amazon EC2
+    #     instance count limits before reaching `maxvCpus`.
+    #
+    #     Batch selects instance types in the order they appear in the
+    #     `instanceTypes` list. When an instance family is specified, sizes
+    #     within that family are expanded using `BEST_FIT_PROGRESSIVE`
+    #     logic—preferring sizes that best fit the jobs, with larger sizes
+    #     as fallback. Instance types that cannot meet the resource
+    #     requirements of the jobs are skipped. This strategy is only
+    #     available for On-Demand Instance (`EC2`) compute resources.
+    #
+    #     If an instance family and an explicit instance type from that
+    #     family both appear in `instanceTypes`, the explicit type takes its
+    #     listed position and is excluded from the family expansion. For
+    #     example, in `["m7a.4xlarge", "m7a", "m6a"]`, `m7a.4xlarge` is
+    #     always placed first and is excluded from the `m7a` family
+    #     expansion.
+    #
     #   SPOT\_CAPACITY\_OPTIMIZED
     #
     #   : Batch selects one or more instance types that are large enough to
@@ -598,12 +623,32 @@ module Aws::Batch
     #     This allocation strategy is only available for Spot Instance
     #     compute resources.
     #
-    #   With `BEST_FIT_PROGRESSIVE`,`SPOT_CAPACITY_OPTIMIZED` and
-    #   `SPOT_PRICE_CAPACITY_OPTIMIZED` (recommended) strategies using
-    #   On-Demand or Spot Instances, and the `BEST_FIT` strategy using Spot
-    #   Instances, Batch might need to exceed `maxvCpus` to meet your
-    #   capacity requirements. In this event, Batch never exceeds `maxvCpus`
-    #   by more than a single instance.
+    #   SPOT\_CAPACITY\_OPTIMIZED\_PRIORITIZED
+    #
+    #   : This is an advanced allocation strategy for customers who want to
+    #     influence instance type selection during scaling. This strategy
+    #     optimizes for **capacity first**, and honors instance type
+    #     priorities on a best-effort basis (priorities are honored when
+    #     they do not significantly reduce available Spot capacity).
+    #
+    #      Placing large instance types at the top of the list may result in
+    #     **over-provisioning** for small jobs. Placing small instance types
+    #     at the top may cause the compute environment to reach Amazon EC2
+    #     instance count limits before reaching `maxvCpus`.
+    #
+    #     Batch selects instance types in the order they appear in the
+    #     `instanceTypes` list, but **optimizes for capacity first**. The
+    #     customer-defined priority is honored on a best-effort basis. When
+    #     Spot Instance capacity pools are similarly available, priority
+    #     order is respected. When capacity is constrained, Batch selects
+    #     from the most available pools regardless of priority to minimize
+    #     the likelihood of Spot Instance interruptions. This strategy is
+    #     only available for Spot Instance compute resources.
+    #
+    #   With any allocation strategy except `BEST_FIT` using On-Demand
+    #   (`EC2`) compute resources, Batch might need to exceed `maxvCpus` to
+    #   meet your capacity requirements. In this event, Batch never exceeds
+    #   `maxvCpus` by more than a single instance.
     #
     #
     #
@@ -625,12 +670,10 @@ module Aws::Batch
     # @!attribute [rw] maxv_cpus
     #   The maximum number of vCPUs that a compute environment can support.
     #
-    #   <note markdown="1"> With `BEST_FIT_PROGRESSIVE`,`SPOT_CAPACITY_OPTIMIZED` and
-    #   `SPOT_PRICE_CAPACITY_OPTIMIZED` (recommended) strategies using
-    #   On-Demand or Spot Instances, and the `BEST_FIT` strategy using Spot
-    #   Instances, Batch might need to exceed `maxvCpus` to meet your
-    #   capacity requirements. In this event, Batch never exceeds `maxvCpus`
-    #   by more than a single instance.
+    #   <note markdown="1"> With any allocation strategy except `BEST_FIT` using On-Demand
+    #   (`EC2`) compute resources, Batch might need to exceed `maxvCpus` to
+    #   meet your capacity requirements. In this event, Batch never exceeds
+    #   `maxvCpus` by more than a single instance.
     #
     #    </note>
     #   @return [Integer]
@@ -655,10 +698,6 @@ module Aws::Batch
     #   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.
@@ -667,14 +706,9 @@ module Aws::Batch
     #     `m6g`, `c6g`, `r6g`, and `c7g` instance families) that matches the
     #     resource demands of the job queue.
     #
-    #   <note markdown="1"> 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][1].
-    #
-    #    </note>
+    #   * `optimal` Semantically equivalent to `default_x86_64`, see
+    #     [Optimal instance type configuration to receive automatic instance
+    #     family updates][1] for details.
     #
     #   <note markdown="1"> Instance family availability varies by Amazon Web Services Region.
     #   For example, some Amazon Web Services Regions may not have any
@@ -749,7 +783,9 @@ module Aws::Batch
     #   The VPC subnets where the compute resources are launched. These
     #   subnets must be within the same VPC. Fargate compute resources can
     #   contain up to 16 subnets. For more information, see [VPCs and
-    #   subnets][1] in the *Amazon VPC User Guide*.
+    #   subnets][1] in the *Amazon VPC User Guide*. This parameter is
+    #   required for compute environments using `EC2`, `SPOT`, `FARGATE`, or
+    #   `FARGATE_SPOT` compute resources.
     #
     #   <note markdown="1"> Batch on Amazon EC2 and Batch on Amazon EKS support Local Zones. For
     #   more information, see [ Local Zones][2] in the *Amazon EC2 User
@@ -987,12 +1023,10 @@ module Aws::Batch
     #   The maximum number of Amazon EC2 vCPUs that an environment can
     #   reach.
     #
-    #   <note markdown="1"> With `BEST_FIT_PROGRESSIVE`,`SPOT_CAPACITY_OPTIMIZED` and
-    #   `SPOT_PRICE_CAPACITY_OPTIMIZED` (recommended) strategies using
-    #   On-Demand or Spot Instances, and the `BEST_FIT` strategy using Spot
-    #   Instances, Batch might need to exceed `maxvCpus` to meet your
-    #   capacity requirements. In this event, Batch never exceeds `maxvCpus`
-    #   by more than a single instance.
+    #   <note markdown="1"> With any allocation strategy except `BEST_FIT` using On-Demand
+    #   (`EC2`) compute resources, Batch might need to exceed `maxvCpus` to
+    #   meet your capacity requirements. In this event, Batch never exceeds
+    #   `maxvCpus` by more than a single instance.
     #
     #    </note>
     #   @return [Integer]
@@ -1107,6 +1141,31 @@ module Aws::Batch
     #     of the previously selected instance types aren't available, Batch
     #     selects new instance types.
     #
+    #   BEST\_FIT\_PROGRESSIVE\_ORDERED
+    #
+    #   : This is an advanced allocation strategy only for customers who
+    #     want to control which instance types are preferred during scaling.
+    #
+    #      Placing large instance types at the top of the list may result in
+    #     **over-provisioning** for small jobs. Placing small instance types
+    #     at the top may cause the compute environment to reach Amazon EC2
+    #     instance count limits before reaching `maxvCpus`.
+    #
+    #     Batch selects instance types in the order they appear in the
+    #     `instanceTypes` list. When an instance family is specified, sizes
+    #     within that family are expanded using `BEST_FIT_PROGRESSIVE`
+    #     logic—preferring sizes that best fit the jobs, with larger sizes
+    #     as fallback. Instance types that cannot meet the resource
+    #     requirements of the jobs are skipped. This strategy is only
+    #     available for On-Demand Instance (`EC2`) compute resources.
+    #
+    #     If an instance family and an explicit instance type from that
+    #     family both appear in `instanceTypes`, the explicit type takes its
+    #     listed position and is excluded from the family expansion. For
+    #     example, in `["m7a.4xlarge", "m7a", "m6a"]`, `m7a.4xlarge` is
+    #     always placed first and is excluded from the `m7a` family
+    #     expansion.
+    #
     #   SPOT\_CAPACITY\_OPTIMIZED
     #
     #   : Batch selects one or more instance types that are large enough to
@@ -1123,12 +1182,32 @@ module Aws::Batch
     #     This allocation strategy is only available for Spot Instance
     #     compute resources.
     #
-    #   With `BEST_FIT_PROGRESSIVE`,`SPOT_CAPACITY_OPTIMIZED` and
-    #   `SPOT_PRICE_CAPACITY_OPTIMIZED` (recommended) strategies using
-    #   On-Demand or Spot Instances, and the `BEST_FIT` strategy using Spot
-    #   Instances, Batch might need to exceed `maxvCpus` to meet your
-    #   capacity requirements. In this event, Batch never exceeds `maxvCpus`
-    #   by more than a single instance.
+    #   SPOT\_CAPACITY\_OPTIMIZED\_PRIORITIZED
+    #
+    #   : This is an advanced allocation strategy for customers who want to
+    #     influence instance type selection during scaling. This strategy
+    #     optimizes for **capacity first**, and honors instance type
+    #     priorities on a best-effort basis (priorities are honored when
+    #     they do not significantly reduce available Spot capacity).
+    #
+    #      Placing large instance types at the top of the list may result in
+    #     **over-provisioning** for small jobs. Placing small instance types
+    #     at the top may cause the compute environment to reach Amazon EC2
+    #     instance count limits before reaching `maxvCpus`.
+    #
+    #     Batch selects instance types in the order they appear in the
+    #     `instanceTypes` list, but **optimizes for capacity first**. The
+    #     customer-defined priority is honored on a best-effort basis. When
+    #     Spot Instance capacity pools are similarly available, priority
+    #     order is respected. When capacity is constrained, Batch selects
+    #     from the most available pools regardless of priority to minimize
+    #     the likelihood of Spot Instance interruptions. This strategy is
+    #     only available for Spot Instance compute resources.
+    #
+    #   With any allocation strategy except `BEST_FIT` using On-Demand
+    #   (`EC2`) compute resources, Batch might need to exceed `maxvCpus` to
+    #   meet your capacity requirements. In this event, Batch never exceeds
+    #   `maxvCpus` by more than a single instance.
     #
     #
     #
@@ -11282,7 +11361,16 @@ module Aws::Batch
     #
     # @!attribute [rw] job_execution_timeout_minutes
     #   Specifies the job timeout (in minutes) when the compute environment
-    #   infrastructure is updated. The default value is 30.
+    #   infrastructure is updated. The default value is 30. The maximum
+    #   value is 7200.
+    #
+    #   <note markdown="1"> Increasing `jobExecutionTimeoutMinutes` during infrastructure
+    #   updates delays the replacement of instances with new instances that
+    #   include updates such as security patches, but provides more time for
+    #   jobs to execute. Consider the security implications of this tradeoff
+    #   when setting timeout values.
+    #
+    #    </note>
     #   @return [Integer]
     #
     # @see http://docs.aws.amazon.com/goto/WebAPI/batch-2016-08-10/UpdatePolicy AWS API Documentation

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.144.0'
+  GEM_VERSION = '1.146.0'
 
 end
 

data/sig/client.rbs

@@ -101,13 +101,13 @@ module Aws
                                         ?unmanagedv_cpus: ::Integer,
                                         ?compute_resources: {
                                           type: ("EC2" | "SPOT" | "FARGATE" | "FARGATE_SPOT"),
-                                          allocation_strategy: ("BEST_FIT" | "BEST_FIT_PROGRESSIVE" | "SPOT_CAPACITY_OPTIMIZED" | "SPOT_PRICE_CAPACITY_OPTIMIZED")?,
+                                          allocation_strategy: ("BEST_FIT" | "BEST_FIT_PROGRESSIVE" | "BEST_FIT_PROGRESSIVE_ORDERED" | "SPOT_CAPACITY_OPTIMIZED" | "SPOT_PRICE_CAPACITY_OPTIMIZED" | "SPOT_CAPACITY_OPTIMIZED_PRIORITIZED")?,
                                           minv_cpus: ::Integer?,
                                           maxv_cpus: ::Integer,
                                           desiredv_cpus: ::Integer?,
                                           instance_types: Array[::String]?,
                                           image_id: ::String?,
-                                          subnets: Array[::String],
+                                          subnets: Array[::String]?,
                                           security_group_ids: Array[::String]?,
                                           ec2_key_pair: ::String?,
                                           instance_role: ::String?,
@@ -790,7 +790,7 @@ module Aws
                                           desiredv_cpus: ::Integer?,
                                           subnets: Array[::String]?,
                                           security_group_ids: Array[::String]?,
-                                          allocation_strategy: ("BEST_FIT_PROGRESSIVE" | "SPOT_CAPACITY_OPTIMIZED" | "SPOT_PRICE_CAPACITY_OPTIMIZED")?,
+                                          allocation_strategy: ("BEST_FIT_PROGRESSIVE" | "BEST_FIT_PROGRESSIVE_ORDERED" | "SPOT_CAPACITY_OPTIMIZED" | "SPOT_PRICE_CAPACITY_OPTIMIZED" | "SPOT_CAPACITY_OPTIMIZED_PRIORITIZED")?,
                                           instance_types: Array[::String]?,
                                           ec2_key_pair: ::String?,
                                           instance_role: ::String?,

data/sig/types.rbs

@@ -112,7 +112,7 @@ module Aws::Batch
 
     class ComputeResource
       attr_accessor type: ("EC2" | "SPOT" | "FARGATE" | "FARGATE_SPOT")
-      attr_accessor allocation_strategy: ("BEST_FIT" | "BEST_FIT_PROGRESSIVE" | "SPOT_CAPACITY_OPTIMIZED" | "SPOT_PRICE_CAPACITY_OPTIMIZED")
+      attr_accessor allocation_strategy: ("BEST_FIT" | "BEST_FIT_PROGRESSIVE" | "BEST_FIT_PROGRESSIVE_ORDERED" | "SPOT_CAPACITY_OPTIMIZED" | "SPOT_PRICE_CAPACITY_OPTIMIZED" | "SPOT_CAPACITY_OPTIMIZED_PRIORITIZED")
       attr_accessor minv_cpus: ::Integer
       attr_accessor maxv_cpus: ::Integer
       attr_accessor desiredv_cpus: ::Integer
@@ -138,7 +138,7 @@ module Aws::Batch
       attr_accessor desiredv_cpus: ::Integer
       attr_accessor subnets: ::Array[::String]
       attr_accessor security_group_ids: ::Array[::String]
-      attr_accessor allocation_strategy: ("BEST_FIT_PROGRESSIVE" | "SPOT_CAPACITY_OPTIMIZED" | "SPOT_PRICE_CAPACITY_OPTIMIZED")
+      attr_accessor allocation_strategy: ("BEST_FIT_PROGRESSIVE" | "BEST_FIT_PROGRESSIVE_ORDERED" | "SPOT_CAPACITY_OPTIMIZED" | "SPOT_PRICE_CAPACITY_OPTIMIZED" | "SPOT_CAPACITY_OPTIMIZED_PRIORITIZED")
       attr_accessor instance_types: ::Array[::String]
       attr_accessor ec2_key_pair: ::String
       attr_accessor instance_role: ::String

metadata

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