aws-sdk-ec2 1.348.0 → 1.349.0

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 37db807519ef1bc8f94dd175ed5bbf762184c9ca0adb9732a1f3cac57d2b8bce
4
- data.tar.gz: 2783afd109ff31f486950f1a8eb79e7be56c0c5e79551903f216b87d5ade21e2
3
+ metadata.gz: bfcf334f96306b62b0cf8d8c0fcd1fdd03297bef34acc16517caf7e382361682
4
+ data.tar.gz: 394acca3282f8247d29596e702360b6b6c3ef803d79164c4d1be2ec4052e07c2
5
5
  SHA512:
6
- metadata.gz: 524a8f68f4c2a9c10be9db53da141975e4d0e19ac2b8e84b5fb5a0a5c642ff6e669069de22f38b5a05cc2ec269ed19f03a8ff35ffaa34a93516b6b46edb5c674
7
- data.tar.gz: a53459c502df5b22a9610ff3786b8302f3b665c267472710337b548fdfe597e5a09d8d909f05a29ac9c0e7c97394339c097da50bff3a6a0acc7d59863596112e
6
+ metadata.gz: a411b555002a85b22e62aefc8a5c2f069d9ee00d5633befb4599d6bbb4c2543dca055701f96b0cc4ea4ddc2d3bb8cffb3be0ee12b5038168360a5a3708363215
7
+ data.tar.gz: cfc030a085c74f3c660487de6c332c9c90960ea3a909997c2e1a9e0d8f76e88033a1e728b19e1a17ae7ac16243924af7943c03cc44a6888ba80b958bf41c2b90
data/CHANGELOG.md CHANGED
@@ -1,6 +1,11 @@
1
1
  Unreleased Changes
2
2
  ------------------
3
3
 
4
+ 1.349.0 (2022-11-10)
5
+ ------------------
6
+
7
+ * Feature - This release adds a new price capacity optimized allocation strategy for Spot Instances to help customers optimize provisioning of Spot Instances via EC2 Auto Scaling, EC2 Fleet, and Spot Fleet. It allocates Spot Instances based on both spare capacity availability and Spot Instance price.
8
+
4
9
  1.348.0 (2022-11-09)
5
10
  ------------------
6
11
 
data/VERSION CHANGED
@@ -1 +1 @@
1
- 1.348.0
1
+ 1.349.0
@@ -5928,7 +5928,7 @@ module Aws::EC2
5928
5928
  # dry_run: false,
5929
5929
  # client_token: "String",
5930
5930
  # spot_options: {
5931
- # allocation_strategy: "lowest-price", # accepts lowest-price, diversified, capacity-optimized, capacity-optimized-prioritized
5931
+ # allocation_strategy: "lowest-price", # accepts lowest-price, diversified, capacity-optimized, capacity-optimized-prioritized, price-capacity-optimized
5932
5932
  # maintenance_strategies: {
5933
5933
  # capacity_rebalance: {
5934
5934
  # replacement_strategy: "launch", # accepts launch, launch-before-terminate
@@ -20379,7 +20379,7 @@ module Aws::EC2
20379
20379
  # resp.fleets[0].valid_from #=> Time
20380
20380
  # resp.fleets[0].valid_until #=> Time
20381
20381
  # resp.fleets[0].replace_unhealthy_instances #=> Boolean
20382
- # resp.fleets[0].spot_options.allocation_strategy #=> String, one of "lowest-price", "diversified", "capacity-optimized", "capacity-optimized-prioritized"
20382
+ # resp.fleets[0].spot_options.allocation_strategy #=> String, one of "lowest-price", "diversified", "capacity-optimized", "capacity-optimized-prioritized", "price-capacity-optimized"
20383
20383
  # resp.fleets[0].spot_options.maintenance_strategies.capacity_rebalance.replacement_strategy #=> String, one of "launch", "launch-before-terminate"
20384
20384
  # resp.fleets[0].spot_options.maintenance_strategies.capacity_rebalance.termination_delay #=> Integer
20385
20385
  # resp.fleets[0].spot_options.instance_interruption_behavior #=> String, one of "hibernate", "stop", "terminate"
@@ -29694,7 +29694,7 @@ module Aws::EC2
29694
29694
  # resp.spot_fleet_request_configs #=> Array
29695
29695
  # resp.spot_fleet_request_configs[0].activity_status #=> String, one of "error", "pending_fulfillment", "pending_termination", "fulfilled"
29696
29696
  # resp.spot_fleet_request_configs[0].create_time #=> Time
29697
- # resp.spot_fleet_request_configs[0].spot_fleet_request_config.allocation_strategy #=> String, one of "lowestPrice", "diversified", "capacityOptimized", "capacityOptimizedPrioritized"
29697
+ # resp.spot_fleet_request_configs[0].spot_fleet_request_config.allocation_strategy #=> String, one of "lowestPrice", "diversified", "capacityOptimized", "capacityOptimizedPrioritized", "priceCapacityOptimized"
29698
29698
  # resp.spot_fleet_request_configs[0].spot_fleet_request_config.on_demand_allocation_strategy #=> String, one of "lowestPrice", "prioritized"
29699
29699
  # resp.spot_fleet_request_configs[0].spot_fleet_request_config.spot_maintenance_strategies.capacity_rebalance.replacement_strategy #=> String, one of "launch", "launch-before-terminate"
29700
29700
  # resp.spot_fleet_request_configs[0].spot_fleet_request_config.spot_maintenance_strategies.capacity_rebalance.termination_delay #=> Integer
@@ -47845,7 +47845,7 @@ module Aws::EC2
47845
47845
  # resp = client.request_spot_fleet({
47846
47846
  # dry_run: false,
47847
47847
  # spot_fleet_request_config: { # required
47848
- # allocation_strategy: "lowestPrice", # accepts lowestPrice, diversified, capacityOptimized, capacityOptimizedPrioritized
47848
+ # allocation_strategy: "lowestPrice", # accepts lowestPrice, diversified, capacityOptimized, capacityOptimizedPrioritized, priceCapacityOptimized
47849
47849
  # on_demand_allocation_strategy: "lowestPrice", # accepts lowestPrice, prioritized
47850
47850
  # spot_maintenance_strategies: {
47851
47851
  # capacity_rebalance: {
@@ -52578,7 +52578,7 @@ module Aws::EC2
52578
52578
  params: params,
52579
52579
  config: config)
52580
52580
  context[:gem_name] = 'aws-sdk-ec2'
52581
- context[:gem_version] = '1.348.0'
52581
+ context[:gem_version] = '1.349.0'
52582
52582
  Seahorse::Client::Request.new(handlers, context)
52583
52583
  end
52584
52584
 
@@ -8193,7 +8193,7 @@ module Aws::EC2
8193
8193
  # dry_run: false,
8194
8194
  # client_token: "String",
8195
8195
  # spot_options: {
8196
- # allocation_strategy: "lowest-price", # accepts lowest-price, diversified, capacity-optimized, capacity-optimized-prioritized
8196
+ # allocation_strategy: "lowest-price", # accepts lowest-price, diversified, capacity-optimized, capacity-optimized-prioritized, price-capacity-optimized
8197
8197
  # maintenance_strategies: {
8198
8198
  # capacity_rebalance: {
8199
8199
  # replacement_strategy: "launch", # accepts launch, launch-before-terminate
@@ -59095,7 +59095,7 @@ module Aws::EC2
59095
59095
  # {
59096
59096
  # dry_run: false,
59097
59097
  # spot_fleet_request_config: { # required
59098
- # allocation_strategy: "lowestPrice", # accepts lowestPrice, diversified, capacityOptimized, capacityOptimizedPrioritized
59098
+ # allocation_strategy: "lowestPrice", # accepts lowestPrice, diversified, capacityOptimized, capacityOptimizedPrioritized, priceCapacityOptimized
59099
59099
  # on_demand_allocation_strategy: "lowestPrice", # accepts lowestPrice, prioritized
59100
59100
  # spot_maintenance_strategies: {
59101
59101
  # capacity_rebalance: {
@@ -65424,7 +65424,7 @@ module Aws::EC2
65424
65424
  # data as a hash:
65425
65425
  #
65426
65426
  # {
65427
- # allocation_strategy: "lowestPrice", # accepts lowestPrice, diversified, capacityOptimized, capacityOptimizedPrioritized
65427
+ # allocation_strategy: "lowestPrice", # accepts lowestPrice, diversified, capacityOptimized, capacityOptimizedPrioritized, priceCapacityOptimized
65428
65428
  # on_demand_allocation_strategy: "lowestPrice", # accepts lowestPrice, prioritized
65429
65429
  # spot_maintenance_strategies: {
65430
65430
  # capacity_rebalance: {
@@ -65712,31 +65712,49 @@ module Aws::EC2
65712
65712
  # [Allocation strategies for Spot Instances][1] in the *Amazon EC2
65713
65713
  # User Guide*.
65714
65714
  #
65715
- # `lowestPrice` - Spot Fleet launches instances from the lowest-price
65716
- # Spot Instance pool that has available capacity. If the cheapest pool
65717
- # doesn't have available capacity, the Spot Instances come from the
65718
- # next cheapest pool that has available capacity. If a pool runs out
65719
- # of capacity before fulfilling your desired capacity, Spot Fleet will
65720
- # continue to fulfill your request by drawing from the next cheapest
65721
- # pool. To ensure that your desired capacity is met, you might receive
65722
- # Spot Instances from several pools.
65723
- #
65724
- # `diversified` - Spot Fleet launches instances from all of the Spot
65725
- # Instance pools that you specify.
65726
- #
65727
- # `capacityOptimized` (recommended) - Spot Fleet launches instances
65728
- # from Spot Instance pools with optimal capacity for the number of
65729
- # instances that are launching. To give certain instance types a
65730
- # higher chance of launching first, use
65731
- # `capacityOptimizedPrioritized`. Set a priority for each instance
65732
- # type by using the `Priority` parameter for
65733
- # `LaunchTemplateOverrides`. You can assign the same priority to
65734
- # different `LaunchTemplateOverrides`. EC2 implements the priorities
65735
- # on a best-effort basis, but optimizes for capacity first.
65736
- # `capacityOptimizedPrioritized` is supported only if your Spot Fleet
65737
- # uses a launch template. Note that if the
65738
- # `OnDemandAllocationStrategy` is set to `prioritized`, the same
65739
- # priority is applied when fulfilling On-Demand capacity.
65715
+ # priceCapacityOptimized (recommended)
65716
+ #
65717
+ # : Spot Fleet identifies the pools with the highest capacity
65718
+ # availability for the number of instances that are launching. This
65719
+ # means that we will request Spot Instances from the pools that we
65720
+ # believe have the lowest chance of interruption in the near term.
65721
+ # Spot Fleet then requests Spot Instances from the lowest priced of
65722
+ # these pools.
65723
+ #
65724
+ # capacityOptimized
65725
+ #
65726
+ # : Spot Fleet identifies the pools with the highest capacity
65727
+ # availability for the number of instances that are launching. This
65728
+ # means that we will request Spot Instances from the pools that we
65729
+ # believe have the lowest chance of interruption in the near term.
65730
+ # To give certain instance types a higher chance of launching first,
65731
+ # use `capacityOptimizedPrioritized`. Set a priority for each
65732
+ # instance type by using the `Priority` parameter for
65733
+ # `LaunchTemplateOverrides`. You can assign the same priority to
65734
+ # different `LaunchTemplateOverrides`. EC2 implements the priorities
65735
+ # on a best-effort basis, but optimizes for capacity first.
65736
+ # `capacityOptimizedPrioritized` is supported only if your Spot
65737
+ # Fleet uses a launch template. Note that if the
65738
+ # `OnDemandAllocationStrategy` is set to `prioritized`, the same
65739
+ # priority is applied when fulfilling On-Demand capacity.
65740
+ #
65741
+ # diversified
65742
+ #
65743
+ # : Spot Fleet requests instances from all of the Spot Instance pools
65744
+ # that you specify.
65745
+ #
65746
+ # lowestPrice
65747
+ #
65748
+ # : Spot Fleet requests instances from the lowest priced Spot Instance
65749
+ # pool that has available capacity. If the lowest priced pool
65750
+ # doesn't have available capacity, the Spot Instances come from the
65751
+ # next lowest priced pool that has available capacity. If a pool
65752
+ # runs out of capacity before fulfilling your desired capacity, Spot
65753
+ # Fleet will continue to fulfill your request by drawing from the
65754
+ # next lowest priced pool. To ensure that your desired capacity is
65755
+ # met, you might receive Spot Instances from several pools. Because
65756
+ # this strategy only considers instance price and not capacity
65757
+ # availability, it might lead to high interruption rates.
65740
65758
  #
65741
65759
  # Default: `lowestPrice`
65742
65760
  #
@@ -66323,31 +66341,49 @@ module Aws::EC2
66323
66341
  # [Allocation strategies for Spot Instances][1] in the *Amazon EC2
66324
66342
  # User Guide*.
66325
66343
  #
66326
- # `lowest-price` - EC2 Fleet launches instances from the lowest-price
66327
- # Spot Instance pool that has available capacity. If the cheapest pool
66328
- # doesn't have available capacity, the Spot Instances come from the
66329
- # next cheapest pool that has available capacity. If a pool runs out
66330
- # of capacity before fulfilling your desired capacity, EC2 Fleet will
66331
- # continue to fulfill your request by drawing from the next cheapest
66332
- # pool. To ensure that your desired capacity is met, you might receive
66333
- # Spot Instances from several pools.
66334
- #
66335
- # `diversified` - EC2 Fleet launches instances from all of the Spot
66336
- # Instance pools that you specify.
66337
- #
66338
- # `capacity-optimized` (recommended) - EC2 Fleet launches instances
66339
- # from Spot Instance pools with optimal capacity for the number of
66340
- # instances that are launching. To give certain instance types a
66341
- # higher chance of launching first, use
66342
- # `capacity-optimized-prioritized`. Set a priority for each instance
66343
- # type by using the `Priority` parameter for
66344
- # `LaunchTemplateOverrides`. You can assign the same priority to
66345
- # different `LaunchTemplateOverrides`. EC2 implements the priorities
66346
- # on a best-effort basis, but optimizes for capacity first.
66347
- # `capacity-optimized-prioritized` is supported only if your fleet
66348
- # uses a launch template. Note that if the On-Demand
66349
- # `AllocationStrategy` is set to `prioritized`, the same priority is
66350
- # applied when fulfilling On-Demand capacity.
66344
+ # price-capacity-optimized (recommended)
66345
+ #
66346
+ # : EC2 Fleet identifies the pools with the highest capacity
66347
+ # availability for the number of instances that are launching. This
66348
+ # means that we will request Spot Instances from the pools that we
66349
+ # believe have the lowest chance of interruption in the near term.
66350
+ # EC2 Fleet then requests Spot Instances from the lowest priced of
66351
+ # these pools.
66352
+ #
66353
+ # capacity-optimized
66354
+ #
66355
+ # : EC2 Fleet identifies the pools with the highest capacity
66356
+ # availability for the number of instances that are launching. This
66357
+ # means that we will request Spot Instances from the pools that we
66358
+ # believe have the lowest chance of interruption in the near term.
66359
+ # To give certain instance types a higher chance of launching first,
66360
+ # use `capacity-optimized-prioritized`. Set a priority for each
66361
+ # instance type by using the `Priority` parameter for
66362
+ # `LaunchTemplateOverrides`. You can assign the same priority to
66363
+ # different `LaunchTemplateOverrides`. EC2 implements the priorities
66364
+ # on a best-effort basis, but optimizes for capacity first.
66365
+ # `capacity-optimized-prioritized` is supported only if your EC2
66366
+ # Fleet uses a launch template. Note that if the On-Demand
66367
+ # `AllocationStrategy` is set to `prioritized`, the same priority is
66368
+ # applied when fulfilling On-Demand capacity.
66369
+ #
66370
+ # diversified
66371
+ #
66372
+ # : EC2 Fleet requests instances from all of the Spot Instance pools
66373
+ # that you specify.
66374
+ #
66375
+ # lowest-price
66376
+ #
66377
+ # : EC2 Fleet requests instances from the lowest priced Spot Instance
66378
+ # pool that has available capacity. If the lowest priced pool
66379
+ # doesn't have available capacity, the Spot Instances come from the
66380
+ # next lowest priced pool that has available capacity. If a pool
66381
+ # runs out of capacity before fulfilling your desired capacity, EC2
66382
+ # Fleet will continue to fulfill your request by drawing from the
66383
+ # next lowest priced pool. To ensure that your desired capacity is
66384
+ # met, you might receive Spot Instances from several pools. Because
66385
+ # this strategy only considers instance price and not capacity
66386
+ # availability, it might lead to high interruption rates.
66351
66387
  #
66352
66388
  # Default: `lowest-price`
66353
66389
  #
@@ -66443,7 +66479,7 @@ module Aws::EC2
66443
66479
  # data as a hash:
66444
66480
  #
66445
66481
  # {
66446
- # allocation_strategy: "lowest-price", # accepts lowest-price, diversified, capacity-optimized, capacity-optimized-prioritized
66482
+ # allocation_strategy: "lowest-price", # accepts lowest-price, diversified, capacity-optimized, capacity-optimized-prioritized, price-capacity-optimized
66447
66483
  # maintenance_strategies: {
66448
66484
  # capacity_rebalance: {
66449
66485
  # replacement_strategy: "launch", # accepts launch, launch-before-terminate
@@ -66465,31 +66501,49 @@ module Aws::EC2
66465
66501
  # [Allocation strategies for Spot Instances][1] in the *Amazon EC2
66466
66502
  # User Guide*.
66467
66503
  #
66468
- # `lowest-price` - EC2 Fleet launches instances from the lowest-price
66469
- # Spot Instance pool that has available capacity. If the cheapest pool
66470
- # doesn't have available capacity, the Spot Instances come from the
66471
- # next cheapest pool that has available capacity. If a pool runs out
66472
- # of capacity before fulfilling your desired capacity, EC2 Fleet will
66473
- # continue to fulfill your request by drawing from the next cheapest
66474
- # pool. To ensure that your desired capacity is met, you might receive
66475
- # Spot Instances from several pools.
66476
- #
66477
- # `diversified` - EC2 Fleet launches instances from all of the Spot
66478
- # Instance pools that you specify.
66479
- #
66480
- # `capacity-optimized` (recommended) - EC2 Fleet launches instances
66481
- # from Spot Instance pools with optimal capacity for the number of
66482
- # instances that are launching. To give certain instance types a
66483
- # higher chance of launching first, use
66484
- # `capacity-optimized-prioritized`. Set a priority for each instance
66485
- # type by using the `Priority` parameter for
66486
- # `LaunchTemplateOverrides`. You can assign the same priority to
66487
- # different `LaunchTemplateOverrides`. EC2 implements the priorities
66488
- # on a best-effort basis, but optimizes for capacity first.
66489
- # `capacity-optimized-prioritized` is supported only if your fleet
66490
- # uses a launch template. Note that if the On-Demand
66491
- # `AllocationStrategy` is set to `prioritized`, the same priority is
66492
- # applied when fulfilling On-Demand capacity.
66504
+ # price-capacity-optimized (recommended)
66505
+ #
66506
+ # : EC2 Fleet identifies the pools with the highest capacity
66507
+ # availability for the number of instances that are launching. This
66508
+ # means that we will request Spot Instances from the pools that we
66509
+ # believe have the lowest chance of interruption in the near term.
66510
+ # EC2 Fleet then requests Spot Instances from the lowest priced of
66511
+ # these pools.
66512
+ #
66513
+ # capacity-optimized
66514
+ #
66515
+ # : EC2 Fleet identifies the pools with the highest capacity
66516
+ # availability for the number of instances that are launching. This
66517
+ # means that we will request Spot Instances from the pools that we
66518
+ # believe have the lowest chance of interruption in the near term.
66519
+ # To give certain instance types a higher chance of launching first,
66520
+ # use `capacity-optimized-prioritized`. Set a priority for each
66521
+ # instance type by using the `Priority` parameter for
66522
+ # `LaunchTemplateOverrides`. You can assign the same priority to
66523
+ # different `LaunchTemplateOverrides`. EC2 implements the priorities
66524
+ # on a best-effort basis, but optimizes for capacity first.
66525
+ # `capacity-optimized-prioritized` is supported only if your EC2
66526
+ # Fleet uses a launch template. Note that if the On-Demand
66527
+ # `AllocationStrategy` is set to `prioritized`, the same priority is
66528
+ # applied when fulfilling On-Demand capacity.
66529
+ #
66530
+ # diversified
66531
+ #
66532
+ # : EC2 Fleet requests instances from all of the Spot Instance pools
66533
+ # that you specify.
66534
+ #
66535
+ # lowest-price
66536
+ #
66537
+ # : EC2 Fleet requests instances from the lowest priced Spot Instance
66538
+ # pool that has available capacity. If the lowest priced pool
66539
+ # doesn't have available capacity, the Spot Instances come from the
66540
+ # next lowest priced pool that has available capacity. If a pool
66541
+ # runs out of capacity before fulfilling your desired capacity, EC2
66542
+ # Fleet will continue to fulfill your request by drawing from the
66543
+ # next lowest priced pool. To ensure that your desired capacity is
66544
+ # met, you might receive Spot Instances from several pools. Because
66545
+ # this strategy only considers instance price and not capacity
66546
+ # availability, it might lead to high interruption rates.
66493
66547
  #
66494
66548
  # Default: `lowest-price`
66495
66549
  #
data/lib/aws-sdk-ec2.rb CHANGED
@@ -76,6 +76,6 @@ require_relative 'aws-sdk-ec2/customizations'
76
76
  # @!group service
77
77
  module Aws::EC2
78
78
 
79
- GEM_VERSION = '1.348.0'
79
+ GEM_VERSION = '1.349.0'
80
80
 
81
81
  end
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: aws-sdk-ec2
3
3
  version: !ruby/object:Gem::Version
4
- version: 1.348.0
4
+ version: 1.349.0
5
5
  platform: ruby
6
6
  authors:
7
7
  - Amazon Web Services
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2022-11-09 00:00:00.000000000 Z
11
+ date: 2022-11-10 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: aws-sigv4