aws-sdk-batch 1.145.0 → 1.146.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: dea26924b55ce9813129cf5c4ef1a6494263b41104c662ed4711255307c65157
4
- data.tar.gz: '0808491d3d03e0506a60377338c4762ae6748b2be81958a16f0b38003eaae316'
3
+ metadata.gz: c3ddedba3974e2b5f747a4f18336fd8de83533d542fcfe290ac473dc11e942e6
4
+ data.tar.gz: 5f648d487d55890879fa37dd1ffa93212c3320183fd5926a1642d5b6ea09e521
5
5
  SHA512:
6
- metadata.gz: 91274da26408757b9e93cbed14c102698b832d541af7bc1f16c8b32a8cdcfbf6beda73da61cd7823a94356846ffa3e6fd1d441c2d9788b3e6b5512c267f2061e
7
- data.tar.gz: a850e9bf6408820b7214cdaab6f973216469624a4f7ee352123dbcc1c5d5975bb94ac6fa1160b21dad4db534243b2c5b509ecec451d47063d1fda3a3e73066b8
6
+ metadata.gz: 117ccf60dc8370146dfe38c553d738e09d2719d1d06ad24c258bdfaf379faaf2d7928e66cb8b59363d3b2c8f3ec804f022aef86dc9da1298ce207c0e7cc98f1a
7
+ data.tar.gz: 73a80b0c21847bce7970d45f4f4ad221105c57ae9083dc639efaed16c56d00ae5da7d4e17a67c10666a7b091e735d220a1b4f42e333a9201da3cdd9b27b1c30e
data/CHANGELOG.md CHANGED
@@ -1,6 +1,11 @@
1
1
  Unreleased Changes
2
2
  ------------------
3
3
 
4
+ 1.146.0 (2026-06-18)
5
+ ------------------
6
+
7
+ * Feature - Adds Support for ordered allocation strategies- BEST-FIT-PROGRESSIVE-ORDERED or SPOT-CAPACITY-OPTIMIZED-PRIORITIZED
8
+
4
9
  1.145.0 (2026-05-26)
5
10
  ------------------
6
11
 
data/VERSION CHANGED
@@ -1 +1 @@
1
- 1.145.0
1
+ 1.146.0
@@ -810,13 +810,13 @@ module Aws::Batch
810
810
  # unmanagedv_cpus: 1,
811
811
  # compute_resources: {
812
812
  # type: "EC2", # required, accepts EC2, SPOT, FARGATE, FARGATE_SPOT
813
- # allocation_strategy: "BEST_FIT", # accepts BEST_FIT, BEST_FIT_PROGRESSIVE, SPOT_CAPACITY_OPTIMIZED, SPOT_PRICE_CAPACITY_OPTIMIZED
813
+ # 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
814
814
  # minv_cpus: 1,
815
815
  # maxv_cpus: 1, # required
816
816
  # desiredv_cpus: 1,
817
817
  # instance_types: ["String"],
818
818
  # image_id: "String",
819
- # subnets: ["String"], # required
819
+ # subnets: ["String"],
820
820
  # security_group_ids: ["String"],
821
821
  # ec2_key_pair: "String",
822
822
  # instance_role: "String",
@@ -1721,7 +1721,7 @@ module Aws::Batch
1721
1721
  # resp.compute_environments[0].status #=> String, one of "CREATING", "UPDATING", "DELETING", "DELETED", "VALID", "INVALID"
1722
1722
  # resp.compute_environments[0].status_reason #=> String
1723
1723
  # resp.compute_environments[0].compute_resources.type #=> String, one of "EC2", "SPOT", "FARGATE", "FARGATE_SPOT"
1724
- # resp.compute_environments[0].compute_resources.allocation_strategy #=> String, one of "BEST_FIT", "BEST_FIT_PROGRESSIVE", "SPOT_CAPACITY_OPTIMIZED", "SPOT_PRICE_CAPACITY_OPTIMIZED"
1724
+ # 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"
1725
1725
  # resp.compute_environments[0].compute_resources.minv_cpus #=> Integer
1726
1726
  # resp.compute_environments[0].compute_resources.maxv_cpus #=> Integer
1727
1727
  # resp.compute_environments[0].compute_resources.desiredv_cpus #=> Integer
@@ -6185,7 +6185,7 @@ module Aws::Batch
6185
6185
  # desiredv_cpus: 1,
6186
6186
  # subnets: ["String"],
6187
6187
  # security_group_ids: ["String"],
6188
- # allocation_strategy: "BEST_FIT_PROGRESSIVE", # accepts BEST_FIT_PROGRESSIVE, SPOT_CAPACITY_OPTIMIZED, SPOT_PRICE_CAPACITY_OPTIMIZED
6188
+ # allocation_strategy: "BEST_FIT_PROGRESSIVE", # accepts BEST_FIT_PROGRESSIVE, BEST_FIT_PROGRESSIVE_ORDERED, SPOT_CAPACITY_OPTIMIZED, SPOT_PRICE_CAPACITY_OPTIMIZED, SPOT_CAPACITY_OPTIMIZED_PRIORITIZED
6189
6189
  # instance_types: ["String"],
6190
6190
  # ec2_key_pair: "String",
6191
6191
  # instance_role: "String",
@@ -6664,7 +6664,7 @@ module Aws::Batch
6664
6664
  tracer: tracer
6665
6665
  )
6666
6666
  context[:gem_name] = 'aws-sdk-batch'
6667
- context[:gem_version] = '1.145.0'
6667
+ context[:gem_version] = '1.146.0'
6668
6668
  Seahorse::Client::Request.new(handlers, context)
6669
6669
  end
6670
6670
 
@@ -468,7 +468,7 @@ module Aws::Batch
468
468
  ComputeResource.add_member(:desiredv_cpus, Shapes::ShapeRef.new(shape: Integer, location_name: "desiredvCpus"))
469
469
  ComputeResource.add_member(:instance_types, Shapes::ShapeRef.new(shape: StringList, location_name: "instanceTypes"))
470
470
  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."}))
471
- ComputeResource.add_member(:subnets, Shapes::ShapeRef.new(shape: StringList, required: true, location_name: "subnets"))
471
+ ComputeResource.add_member(:subnets, Shapes::ShapeRef.new(shape: StringList, location_name: "subnets"))
472
472
  ComputeResource.add_member(:security_group_ids, Shapes::ShapeRef.new(shape: StringList, location_name: "securityGroupIds"))
473
473
  ComputeResource.add_member(:ec2_key_pair, Shapes::ShapeRef.new(shape: String, location_name: "ec2KeyPair"))
474
474
  ComputeResource.add_member(:instance_role, Shapes::ShapeRef.new(shape: String, location_name: "instanceRole"))
@@ -582,6 +582,31 @@ module Aws::Batch
582
582
  # of the previously selected instance types aren't available, Batch
583
583
  # selects new instance types.
584
584
  #
585
+ # BEST\_FIT\_PROGRESSIVE\_ORDERED
586
+ #
587
+ # : This is an advanced allocation strategy only for customers who
588
+ # want to control which instance types are preferred during scaling.
589
+ #
590
+ # Placing large instance types at the top of the list may result in
591
+ # **over-provisioning** for small jobs. Placing small instance types
592
+ # at the top may cause the compute environment to reach Amazon EC2
593
+ # instance count limits before reaching `maxvCpus`.
594
+ #
595
+ # Batch selects instance types in the order they appear in the
596
+ # `instanceTypes` list. When an instance family is specified, sizes
597
+ # within that family are expanded using `BEST_FIT_PROGRESSIVE`
598
+ # logic—preferring sizes that best fit the jobs, with larger sizes
599
+ # as fallback. Instance types that cannot meet the resource
600
+ # requirements of the jobs are skipped. This strategy is only
601
+ # available for On-Demand Instance (`EC2`) compute resources.
602
+ #
603
+ # If an instance family and an explicit instance type from that
604
+ # family both appear in `instanceTypes`, the explicit type takes its
605
+ # listed position and is excluded from the family expansion. For
606
+ # example, in `["m7a.4xlarge", "m7a", "m6a"]`, `m7a.4xlarge` is
607
+ # always placed first and is excluded from the `m7a` family
608
+ # expansion.
609
+ #
585
610
  # SPOT\_CAPACITY\_OPTIMIZED
586
611
  #
587
612
  # : Batch selects one or more instance types that are large enough to
@@ -598,12 +623,32 @@ module Aws::Batch
598
623
  # This allocation strategy is only available for Spot Instance
599
624
  # compute resources.
600
625
  #
601
- # With `BEST_FIT_PROGRESSIVE`,`SPOT_CAPACITY_OPTIMIZED` and
602
- # `SPOT_PRICE_CAPACITY_OPTIMIZED` (recommended) strategies using
603
- # On-Demand or Spot Instances, and the `BEST_FIT` strategy using Spot
604
- # Instances, Batch might need to exceed `maxvCpus` to meet your
605
- # capacity requirements. In this event, Batch never exceeds `maxvCpus`
606
- # by more than a single instance.
626
+ # SPOT\_CAPACITY\_OPTIMIZED\_PRIORITIZED
627
+ #
628
+ # : This is an advanced allocation strategy for customers who want to
629
+ # influence instance type selection during scaling. This strategy
630
+ # optimizes for **capacity first**, and honors instance type
631
+ # priorities on a best-effort basis (priorities are honored when
632
+ # they do not significantly reduce available Spot capacity).
633
+ #
634
+ # Placing large instance types at the top of the list may result in
635
+ # **over-provisioning** for small jobs. Placing small instance types
636
+ # at the top may cause the compute environment to reach Amazon EC2
637
+ # instance count limits before reaching `maxvCpus`.
638
+ #
639
+ # Batch selects instance types in the order they appear in the
640
+ # `instanceTypes` list, but **optimizes for capacity first**. The
641
+ # customer-defined priority is honored on a best-effort basis. When
642
+ # Spot Instance capacity pools are similarly available, priority
643
+ # order is respected. When capacity is constrained, Batch selects
644
+ # from the most available pools regardless of priority to minimize
645
+ # the likelihood of Spot Instance interruptions. This strategy is
646
+ # only available for Spot Instance compute resources.
647
+ #
648
+ # With any allocation strategy except `BEST_FIT` using On-Demand
649
+ # (`EC2`) compute resources, Batch might need to exceed `maxvCpus` to
650
+ # meet your capacity requirements. In this event, Batch never exceeds
651
+ # `maxvCpus` by more than a single instance.
607
652
  #
608
653
  #
609
654
  #
@@ -625,12 +670,10 @@ module Aws::Batch
625
670
  # @!attribute [rw] maxv_cpus
626
671
  # The maximum number of vCPUs that a compute environment can support.
627
672
  #
628
- # <note markdown="1"> With `BEST_FIT_PROGRESSIVE`,`SPOT_CAPACITY_OPTIMIZED` and
629
- # `SPOT_PRICE_CAPACITY_OPTIMIZED` (recommended) strategies using
630
- # On-Demand or Spot Instances, and the `BEST_FIT` strategy using Spot
631
- # Instances, Batch might need to exceed `maxvCpus` to meet your
632
- # capacity requirements. In this event, Batch never exceeds `maxvCpus`
633
- # by more than a single instance.
673
+ # <note markdown="1"> With any allocation strategy except `BEST_FIT` using On-Demand
674
+ # (`EC2`) compute resources, Batch might need to exceed `maxvCpus` to
675
+ # meet your capacity requirements. In this event, Batch never exceeds
676
+ # `maxvCpus` by more than a single instance.
634
677
  #
635
678
  # </note>
636
679
  # @return [Integer]
@@ -740,7 +783,9 @@ module Aws::Batch
740
783
  # The VPC subnets where the compute resources are launched. These
741
784
  # subnets must be within the same VPC. Fargate compute resources can
742
785
  # contain up to 16 subnets. For more information, see [VPCs and
743
- # subnets][1] in the *Amazon VPC User Guide*.
786
+ # subnets][1] in the *Amazon VPC User Guide*. This parameter is
787
+ # required for compute environments using `EC2`, `SPOT`, `FARGATE`, or
788
+ # `FARGATE_SPOT` compute resources.
744
789
  #
745
790
  # <note markdown="1"> Batch on Amazon EC2 and Batch on Amazon EKS support Local Zones. For
746
791
  # more information, see [ Local Zones][2] in the *Amazon EC2 User
@@ -978,12 +1023,10 @@ module Aws::Batch
978
1023
  # The maximum number of Amazon EC2 vCPUs that an environment can
979
1024
  # reach.
980
1025
  #
981
- # <note markdown="1"> With `BEST_FIT_PROGRESSIVE`,`SPOT_CAPACITY_OPTIMIZED` and
982
- # `SPOT_PRICE_CAPACITY_OPTIMIZED` (recommended) strategies using
983
- # On-Demand or Spot Instances, and the `BEST_FIT` strategy using Spot
984
- # Instances, Batch might need to exceed `maxvCpus` to meet your
985
- # capacity requirements. In this event, Batch never exceeds `maxvCpus`
986
- # by more than a single instance.
1026
+ # <note markdown="1"> With any allocation strategy except `BEST_FIT` using On-Demand
1027
+ # (`EC2`) compute resources, Batch might need to exceed `maxvCpus` to
1028
+ # meet your capacity requirements. In this event, Batch never exceeds
1029
+ # `maxvCpus` by more than a single instance.
987
1030
  #
988
1031
  # </note>
989
1032
  # @return [Integer]
@@ -1098,6 +1141,31 @@ module Aws::Batch
1098
1141
  # of the previously selected instance types aren't available, Batch
1099
1142
  # selects new instance types.
1100
1143
  #
1144
+ # BEST\_FIT\_PROGRESSIVE\_ORDERED
1145
+ #
1146
+ # : This is an advanced allocation strategy only for customers who
1147
+ # want to control which instance types are preferred during scaling.
1148
+ #
1149
+ # Placing large instance types at the top of the list may result in
1150
+ # **over-provisioning** for small jobs. Placing small instance types
1151
+ # at the top may cause the compute environment to reach Amazon EC2
1152
+ # instance count limits before reaching `maxvCpus`.
1153
+ #
1154
+ # Batch selects instance types in the order they appear in the
1155
+ # `instanceTypes` list. When an instance family is specified, sizes
1156
+ # within that family are expanded using `BEST_FIT_PROGRESSIVE`
1157
+ # logic—preferring sizes that best fit the jobs, with larger sizes
1158
+ # as fallback. Instance types that cannot meet the resource
1159
+ # requirements of the jobs are skipped. This strategy is only
1160
+ # available for On-Demand Instance (`EC2`) compute resources.
1161
+ #
1162
+ # If an instance family and an explicit instance type from that
1163
+ # family both appear in `instanceTypes`, the explicit type takes its
1164
+ # listed position and is excluded from the family expansion. For
1165
+ # example, in `["m7a.4xlarge", "m7a", "m6a"]`, `m7a.4xlarge` is
1166
+ # always placed first and is excluded from the `m7a` family
1167
+ # expansion.
1168
+ #
1101
1169
  # SPOT\_CAPACITY\_OPTIMIZED
1102
1170
  #
1103
1171
  # : Batch selects one or more instance types that are large enough to
@@ -1114,12 +1182,32 @@ module Aws::Batch
1114
1182
  # This allocation strategy is only available for Spot Instance
1115
1183
  # compute resources.
1116
1184
  #
1117
- # With `BEST_FIT_PROGRESSIVE`,`SPOT_CAPACITY_OPTIMIZED` and
1118
- # `SPOT_PRICE_CAPACITY_OPTIMIZED` (recommended) strategies using
1119
- # On-Demand or Spot Instances, and the `BEST_FIT` strategy using Spot
1120
- # Instances, Batch might need to exceed `maxvCpus` to meet your
1121
- # capacity requirements. In this event, Batch never exceeds `maxvCpus`
1122
- # by more than a single instance.
1185
+ # SPOT\_CAPACITY\_OPTIMIZED\_PRIORITIZED
1186
+ #
1187
+ # : This is an advanced allocation strategy for customers who want to
1188
+ # influence instance type selection during scaling. This strategy
1189
+ # optimizes for **capacity first**, and honors instance type
1190
+ # priorities on a best-effort basis (priorities are honored when
1191
+ # they do not significantly reduce available Spot capacity).
1192
+ #
1193
+ # Placing large instance types at the top of the list may result in
1194
+ # **over-provisioning** for small jobs. Placing small instance types
1195
+ # at the top may cause the compute environment to reach Amazon EC2
1196
+ # instance count limits before reaching `maxvCpus`.
1197
+ #
1198
+ # Batch selects instance types in the order they appear in the
1199
+ # `instanceTypes` list, but **optimizes for capacity first**. The
1200
+ # customer-defined priority is honored on a best-effort basis. When
1201
+ # Spot Instance capacity pools are similarly available, priority
1202
+ # order is respected. When capacity is constrained, Batch selects
1203
+ # from the most available pools regardless of priority to minimize
1204
+ # the likelihood of Spot Instance interruptions. This strategy is
1205
+ # only available for Spot Instance compute resources.
1206
+ #
1207
+ # With any allocation strategy except `BEST_FIT` using On-Demand
1208
+ # (`EC2`) compute resources, Batch might need to exceed `maxvCpus` to
1209
+ # meet your capacity requirements. In this event, Batch never exceeds
1210
+ # `maxvCpus` by more than a single instance.
1123
1211
  #
1124
1212
  #
1125
1213
  #
data/lib/aws-sdk-batch.rb CHANGED
@@ -54,7 +54,7 @@ module Aws::Batch
54
54
  autoload :EndpointProvider, 'aws-sdk-batch/endpoint_provider'
55
55
  autoload :Endpoints, 'aws-sdk-batch/endpoints'
56
56
 
57
- GEM_VERSION = '1.145.0'
57
+ GEM_VERSION = '1.146.0'
58
58
 
59
59
  end
60
60
 
data/sig/client.rbs CHANGED
@@ -101,13 +101,13 @@ module Aws
101
101
  ?unmanagedv_cpus: ::Integer,
102
102
  ?compute_resources: {
103
103
  type: ("EC2" | "SPOT" | "FARGATE" | "FARGATE_SPOT"),
104
- allocation_strategy: ("BEST_FIT" | "BEST_FIT_PROGRESSIVE" | "SPOT_CAPACITY_OPTIMIZED" | "SPOT_PRICE_CAPACITY_OPTIMIZED")?,
104
+ allocation_strategy: ("BEST_FIT" | "BEST_FIT_PROGRESSIVE" | "BEST_FIT_PROGRESSIVE_ORDERED" | "SPOT_CAPACITY_OPTIMIZED" | "SPOT_PRICE_CAPACITY_OPTIMIZED" | "SPOT_CAPACITY_OPTIMIZED_PRIORITIZED")?,
105
105
  minv_cpus: ::Integer?,
106
106
  maxv_cpus: ::Integer,
107
107
  desiredv_cpus: ::Integer?,
108
108
  instance_types: Array[::String]?,
109
109
  image_id: ::String?,
110
- subnets: Array[::String],
110
+ subnets: Array[::String]?,
111
111
  security_group_ids: Array[::String]?,
112
112
  ec2_key_pair: ::String?,
113
113
  instance_role: ::String?,
@@ -790,7 +790,7 @@ module Aws
790
790
  desiredv_cpus: ::Integer?,
791
791
  subnets: Array[::String]?,
792
792
  security_group_ids: Array[::String]?,
793
- allocation_strategy: ("BEST_FIT_PROGRESSIVE" | "SPOT_CAPACITY_OPTIMIZED" | "SPOT_PRICE_CAPACITY_OPTIMIZED")?,
793
+ allocation_strategy: ("BEST_FIT_PROGRESSIVE" | "BEST_FIT_PROGRESSIVE_ORDERED" | "SPOT_CAPACITY_OPTIMIZED" | "SPOT_PRICE_CAPACITY_OPTIMIZED" | "SPOT_CAPACITY_OPTIMIZED_PRIORITIZED")?,
794
794
  instance_types: Array[::String]?,
795
795
  ec2_key_pair: ::String?,
796
796
  instance_role: ::String?,
data/sig/types.rbs CHANGED
@@ -112,7 +112,7 @@ module Aws::Batch
112
112
 
113
113
  class ComputeResource
114
114
  attr_accessor type: ("EC2" | "SPOT" | "FARGATE" | "FARGATE_SPOT")
115
- attr_accessor allocation_strategy: ("BEST_FIT" | "BEST_FIT_PROGRESSIVE" | "SPOT_CAPACITY_OPTIMIZED" | "SPOT_PRICE_CAPACITY_OPTIMIZED")
115
+ attr_accessor allocation_strategy: ("BEST_FIT" | "BEST_FIT_PROGRESSIVE" | "BEST_FIT_PROGRESSIVE_ORDERED" | "SPOT_CAPACITY_OPTIMIZED" | "SPOT_PRICE_CAPACITY_OPTIMIZED" | "SPOT_CAPACITY_OPTIMIZED_PRIORITIZED")
116
116
  attr_accessor minv_cpus: ::Integer
117
117
  attr_accessor maxv_cpus: ::Integer
118
118
  attr_accessor desiredv_cpus: ::Integer
@@ -138,7 +138,7 @@ module Aws::Batch
138
138
  attr_accessor desiredv_cpus: ::Integer
139
139
  attr_accessor subnets: ::Array[::String]
140
140
  attr_accessor security_group_ids: ::Array[::String]
141
- attr_accessor allocation_strategy: ("BEST_FIT_PROGRESSIVE" | "SPOT_CAPACITY_OPTIMIZED" | "SPOT_PRICE_CAPACITY_OPTIMIZED")
141
+ attr_accessor allocation_strategy: ("BEST_FIT_PROGRESSIVE" | "BEST_FIT_PROGRESSIVE_ORDERED" | "SPOT_CAPACITY_OPTIMIZED" | "SPOT_PRICE_CAPACITY_OPTIMIZED" | "SPOT_CAPACITY_OPTIMIZED_PRIORITIZED")
142
142
  attr_accessor instance_types: ::Array[::String]
143
143
  attr_accessor ec2_key_pair: ::String
144
144
  attr_accessor instance_role: ::String
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: aws-sdk-batch
3
3
  version: !ruby/object:Gem::Version
4
- version: 1.145.0
4
+ version: 1.146.0
5
5
  platform: ruby
6
6
  authors:
7
7
  - Amazon Web Services