aws-sdk-ec2 1.348.0 → 1.349.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 37db807519ef1bc8f94dd175ed5bbf762184c9ca0adb9732a1f3cac57d2b8bce
-  data.tar.gz: 2783afd109ff31f486950f1a8eb79e7be56c0c5e79551903f216b87d5ade21e2
+  metadata.gz: bfcf334f96306b62b0cf8d8c0fcd1fdd03297bef34acc16517caf7e382361682
+  data.tar.gz: 394acca3282f8247d29596e702360b6b6c3ef803d79164c4d1be2ec4052e07c2
 SHA512:
-  metadata.gz: 524a8f68f4c2a9c10be9db53da141975e4d0e19ac2b8e84b5fb5a0a5c642ff6e669069de22f38b5a05cc2ec269ed19f03a8ff35ffaa34a93516b6b46edb5c674
-  data.tar.gz: a53459c502df5b22a9610ff3786b8302f3b665c267472710337b548fdfe597e5a09d8d909f05a29ac9c0e7c97394339c097da50bff3a6a0acc7d59863596112e
+  metadata.gz: a411b555002a85b22e62aefc8a5c2f069d9ee00d5633befb4599d6bbb4c2543dca055701f96b0cc4ea4ddc2d3bb8cffb3be0ee12b5038168360a5a3708363215
+  data.tar.gz: cfc030a085c74f3c660487de6c332c9c90960ea3a909997c2e1a9e0d8f76e88033a1e728b19e1a17ae7ac16243924af7943c03cc44a6888ba80b958bf41c2b90

data/CHANGELOG.md

@@ -1,6 +1,11 @@
 Unreleased Changes
 ------------------
 
+1.349.0 (2022-11-10)
+------------------
+
+* 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.
+
 1.348.0 (2022-11-09)
 ------------------
 

data/VERSION

@@ -1 +1 @@
-1.348.0
+1.349.0

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

@@ -5928,7 +5928,7 @@ module Aws::EC2
     #     dry_run: false,
     #     client_token: "String",
     #     spot_options: {
-    #       allocation_strategy: "lowest-price", # accepts lowest-price, diversified, capacity-optimized, capacity-optimized-prioritized
+    #       allocation_strategy: "lowest-price", # accepts lowest-price, diversified, capacity-optimized, capacity-optimized-prioritized, price-capacity-optimized
     #       maintenance_strategies: {
     #         capacity_rebalance: {
     #           replacement_strategy: "launch", # accepts launch, launch-before-terminate
@@ -20379,7 +20379,7 @@ module Aws::EC2
     #   resp.fleets[0].valid_from #=> Time
     #   resp.fleets[0].valid_until #=> Time
     #   resp.fleets[0].replace_unhealthy_instances #=> Boolean
-    #   resp.fleets[0].spot_options.allocation_strategy #=> String, one of "lowest-price", "diversified", "capacity-optimized", "capacity-optimized-prioritized"
+    #   resp.fleets[0].spot_options.allocation_strategy #=> String, one of "lowest-price", "diversified", "capacity-optimized", "capacity-optimized-prioritized", "price-capacity-optimized"
     #   resp.fleets[0].spot_options.maintenance_strategies.capacity_rebalance.replacement_strategy #=> String, one of "launch", "launch-before-terminate"
     #   resp.fleets[0].spot_options.maintenance_strategies.capacity_rebalance.termination_delay #=> Integer
     #   resp.fleets[0].spot_options.instance_interruption_behavior #=> String, one of "hibernate", "stop", "terminate"
@@ -29694,7 +29694,7 @@ module Aws::EC2
     #   resp.spot_fleet_request_configs #=> Array
     #   resp.spot_fleet_request_configs[0].activity_status #=> String, one of "error", "pending_fulfillment", "pending_termination", "fulfilled"
     #   resp.spot_fleet_request_configs[0].create_time #=> Time
-    #   resp.spot_fleet_request_configs[0].spot_fleet_request_config.allocation_strategy #=> String, one of "lowestPrice", "diversified", "capacityOptimized", "capacityOptimizedPrioritized"
+    #   resp.spot_fleet_request_configs[0].spot_fleet_request_config.allocation_strategy #=> String, one of "lowestPrice", "diversified", "capacityOptimized", "capacityOptimizedPrioritized", "priceCapacityOptimized"
     #   resp.spot_fleet_request_configs[0].spot_fleet_request_config.on_demand_allocation_strategy #=> String, one of "lowestPrice", "prioritized"
     #   resp.spot_fleet_request_configs[0].spot_fleet_request_config.spot_maintenance_strategies.capacity_rebalance.replacement_strategy #=> String, one of "launch", "launch-before-terminate"
     #   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
     #   resp = client.request_spot_fleet({
     #     dry_run: false,
     #     spot_fleet_request_config: { # required
-    #       allocation_strategy: "lowestPrice", # accepts lowestPrice, diversified, capacityOptimized, capacityOptimizedPrioritized
+    #       allocation_strategy: "lowestPrice", # accepts lowestPrice, diversified, capacityOptimized, capacityOptimizedPrioritized, priceCapacityOptimized
     #       on_demand_allocation_strategy: "lowestPrice", # accepts lowestPrice, prioritized
     #       spot_maintenance_strategies: {
     #         capacity_rebalance: {
@@ -52578,7 +52578,7 @@ module Aws::EC2
         params: params,
         config: config)
       context[:gem_name] = 'aws-sdk-ec2'
-      context[:gem_version] = '1.348.0'
+      context[:gem_version] = '1.349.0'
       Seahorse::Client::Request.new(handlers, context)
     end
 

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

@@ -8193,7 +8193,7 @@ module Aws::EC2
     #         dry_run: false,
     #         client_token: "String",
     #         spot_options: {
-    #           allocation_strategy: "lowest-price", # accepts lowest-price, diversified, capacity-optimized, capacity-optimized-prioritized
+    #           allocation_strategy: "lowest-price", # accepts lowest-price, diversified, capacity-optimized, capacity-optimized-prioritized, price-capacity-optimized
     #           maintenance_strategies: {
     #             capacity_rebalance: {
     #               replacement_strategy: "launch", # accepts launch, launch-before-terminate
@@ -59095,7 +59095,7 @@ module Aws::EC2
     #       {
     #         dry_run: false,
     #         spot_fleet_request_config: { # required
-    #           allocation_strategy: "lowestPrice", # accepts lowestPrice, diversified, capacityOptimized, capacityOptimizedPrioritized
+    #           allocation_strategy: "lowestPrice", # accepts lowestPrice, diversified, capacityOptimized, capacityOptimizedPrioritized, priceCapacityOptimized
     #           on_demand_allocation_strategy: "lowestPrice", # accepts lowestPrice, prioritized
     #           spot_maintenance_strategies: {
     #             capacity_rebalance: {
@@ -65424,7 +65424,7 @@ module Aws::EC2
     #   data as a hash:
     #
     #       {
-    #         allocation_strategy: "lowestPrice", # accepts lowestPrice, diversified, capacityOptimized, capacityOptimizedPrioritized
+    #         allocation_strategy: "lowestPrice", # accepts lowestPrice, diversified, capacityOptimized, capacityOptimizedPrioritized, priceCapacityOptimized
     #         on_demand_allocation_strategy: "lowestPrice", # accepts lowestPrice, prioritized
     #         spot_maintenance_strategies: {
     #           capacity_rebalance: {
@@ -65712,31 +65712,49 @@ module Aws::EC2
     #   [Allocation strategies for Spot Instances][1] in the *Amazon EC2
     #   User Guide*.
     #
-    #   `lowestPrice` - Spot Fleet launches instances from the lowest-price
-    #   Spot Instance pool that has available capacity. If the cheapest pool
-    #   doesn't have available capacity, the Spot Instances come from the
-    #   next cheapest pool that has available capacity. If a pool runs out
-    #   of capacity before fulfilling your desired capacity, Spot Fleet will
-    #   continue to fulfill your request by drawing from the next cheapest
-    #   pool. To ensure that your desired capacity is met, you might receive
-    #   Spot Instances from several pools.
-    #
-    #   `diversified` - Spot Fleet launches instances from all of the Spot
-    #   Instance pools that you specify.
-    #
-    #   `capacityOptimized` (recommended) - Spot Fleet launches instances
-    #   from Spot Instance pools with optimal capacity for the number of
-    #   instances that are launching. To give certain instance types a
-    #   higher chance of launching first, use
-    #   `capacityOptimizedPrioritized`. Set a priority for each instance
-    #   type by using the `Priority` parameter for
-    #   `LaunchTemplateOverrides`. You can assign the same priority to
-    #   different `LaunchTemplateOverrides`. EC2 implements the priorities
-    #   on a best-effort basis, but optimizes for capacity first.
-    #   `capacityOptimizedPrioritized` is supported only if your Spot Fleet
-    #   uses a launch template. Note that if the
-    #   `OnDemandAllocationStrategy` is set to `prioritized`, the same
-    #   priority is applied when fulfilling On-Demand capacity.
+    #   priceCapacityOptimized (recommended)
+    #
+    #   : Spot Fleet identifies the pools with the highest capacity
+    #     availability for the number of instances that are launching. This
+    #     means that we will request Spot Instances from the pools that we
+    #     believe have the lowest chance of interruption in the near term.
+    #     Spot Fleet then requests Spot Instances from the lowest priced of
+    #     these pools.
+    #
+    #   capacityOptimized
+    #
+    #   : Spot Fleet identifies the pools with the highest capacity
+    #     availability for the number of instances that are launching. This
+    #     means that we will request Spot Instances from the pools that we
+    #     believe have the lowest chance of interruption in the near term.
+    #     To give certain instance types a higher chance of launching first,
+    #     use `capacityOptimizedPrioritized`. Set a priority for each
+    #     instance type by using the `Priority` parameter for
+    #     `LaunchTemplateOverrides`. You can assign the same priority to
+    #     different `LaunchTemplateOverrides`. EC2 implements the priorities
+    #     on a best-effort basis, but optimizes for capacity first.
+    #     `capacityOptimizedPrioritized` is supported only if your Spot
+    #     Fleet uses a launch template. Note that if the
+    #     `OnDemandAllocationStrategy` is set to `prioritized`, the same
+    #     priority is applied when fulfilling On-Demand capacity.
+    #
+    #   diversified
+    #
+    #   : Spot Fleet requests instances from all of the Spot Instance pools
+    #     that you specify.
+    #
+    #   lowestPrice
+    #
+    #   : Spot Fleet requests instances from the lowest priced Spot Instance
+    #     pool that has available capacity. If the lowest priced pool
+    #     doesn't have available capacity, the Spot Instances come from the
+    #     next lowest priced pool that has available capacity. If a pool
+    #     runs out of capacity before fulfilling your desired capacity, Spot
+    #     Fleet will continue to fulfill your request by drawing from the
+    #     next lowest priced pool. To ensure that your desired capacity is
+    #     met, you might receive Spot Instances from several pools. Because
+    #     this strategy only considers instance price and not capacity
+    #     availability, it might lead to high interruption rates.
     #
     #   Default: `lowestPrice`
     #
@@ -66323,31 +66341,49 @@ module Aws::EC2
     #   [Allocation strategies for Spot Instances][1] in the *Amazon EC2
     #   User Guide*.
     #
-    #   `lowest-price` - EC2 Fleet launches instances from the lowest-price
-    #   Spot Instance pool that has available capacity. If the cheapest pool
-    #   doesn't have available capacity, the Spot Instances come from the
-    #   next cheapest pool that has available capacity. If a pool runs out
-    #   of capacity before fulfilling your desired capacity, EC2 Fleet will
-    #   continue to fulfill your request by drawing from the next cheapest
-    #   pool. To ensure that your desired capacity is met, you might receive
-    #   Spot Instances from several pools.
-    #
-    #   `diversified` - EC2 Fleet launches instances from all of the Spot
-    #   Instance pools that you specify.
-    #
-    #   `capacity-optimized` (recommended) - EC2 Fleet launches instances
-    #   from Spot Instance pools with optimal capacity for the number of
-    #   instances that are launching. To give certain instance types a
-    #   higher chance of launching first, use
-    #   `capacity-optimized-prioritized`. Set a priority for each instance
-    #   type by using the `Priority` parameter for
-    #   `LaunchTemplateOverrides`. You can assign the same priority to
-    #   different `LaunchTemplateOverrides`. EC2 implements the priorities
-    #   on a best-effort basis, but optimizes for capacity first.
-    #   `capacity-optimized-prioritized` is supported only if your fleet
-    #   uses a launch template. Note that if the On-Demand
-    #   `AllocationStrategy` is set to `prioritized`, the same priority is
-    #   applied when fulfilling On-Demand capacity.
+    #   price-capacity-optimized (recommended)
+    #
+    #   : EC2 Fleet identifies the pools with the highest capacity
+    #     availability for the number of instances that are launching. This
+    #     means that we will request Spot Instances from the pools that we
+    #     believe have the lowest chance of interruption in the near term.
+    #     EC2 Fleet then requests Spot Instances from the lowest priced of
+    #     these pools.
+    #
+    #   capacity-optimized
+    #
+    #   : EC2 Fleet identifies the pools with the highest capacity
+    #     availability for the number of instances that are launching. This
+    #     means that we will request Spot Instances from the pools that we
+    #     believe have the lowest chance of interruption in the near term.
+    #     To give certain instance types a higher chance of launching first,
+    #     use `capacity-optimized-prioritized`. Set a priority for each
+    #     instance type by using the `Priority` parameter for
+    #     `LaunchTemplateOverrides`. You can assign the same priority to
+    #     different `LaunchTemplateOverrides`. EC2 implements the priorities
+    #     on a best-effort basis, but optimizes for capacity first.
+    #     `capacity-optimized-prioritized` is supported only if your EC2
+    #     Fleet uses a launch template. Note that if the On-Demand
+    #     `AllocationStrategy` is set to `prioritized`, the same priority is
+    #     applied when fulfilling On-Demand capacity.
+    #
+    #   diversified
+    #
+    #   : EC2 Fleet requests instances from all of the Spot Instance pools
+    #     that you specify.
+    #
+    #   lowest-price
+    #
+    #   : EC2 Fleet requests instances from the lowest priced Spot Instance
+    #     pool that has available capacity. If the lowest priced pool
+    #     doesn't have available capacity, the Spot Instances come from the
+    #     next lowest priced pool that has available capacity. If a pool
+    #     runs out of capacity before fulfilling your desired capacity, EC2
+    #     Fleet will continue to fulfill your request by drawing from the
+    #     next lowest priced pool. To ensure that your desired capacity is
+    #     met, you might receive Spot Instances from several pools. Because
+    #     this strategy only considers instance price and not capacity
+    #     availability, it might lead to high interruption rates.
     #
     #   Default: `lowest-price`
     #
@@ -66443,7 +66479,7 @@ module Aws::EC2
     #   data as a hash:
     #
     #       {
-    #         allocation_strategy: "lowest-price", # accepts lowest-price, diversified, capacity-optimized, capacity-optimized-prioritized
+    #         allocation_strategy: "lowest-price", # accepts lowest-price, diversified, capacity-optimized, capacity-optimized-prioritized, price-capacity-optimized
     #         maintenance_strategies: {
     #           capacity_rebalance: {
     #             replacement_strategy: "launch", # accepts launch, launch-before-terminate
@@ -66465,31 +66501,49 @@ module Aws::EC2
     #   [Allocation strategies for Spot Instances][1] in the *Amazon EC2
     #   User Guide*.
     #
-    #   `lowest-price` - EC2 Fleet launches instances from the lowest-price
-    #   Spot Instance pool that has available capacity. If the cheapest pool
-    #   doesn't have available capacity, the Spot Instances come from the
-    #   next cheapest pool that has available capacity. If a pool runs out
-    #   of capacity before fulfilling your desired capacity, EC2 Fleet will
-    #   continue to fulfill your request by drawing from the next cheapest
-    #   pool. To ensure that your desired capacity is met, you might receive
-    #   Spot Instances from several pools.
-    #
-    #   `diversified` - EC2 Fleet launches instances from all of the Spot
-    #   Instance pools that you specify.
-    #
-    #   `capacity-optimized` (recommended) - EC2 Fleet launches instances
-    #   from Spot Instance pools with optimal capacity for the number of
-    #   instances that are launching. To give certain instance types a
-    #   higher chance of launching first, use
-    #   `capacity-optimized-prioritized`. Set a priority for each instance
-    #   type by using the `Priority` parameter for
-    #   `LaunchTemplateOverrides`. You can assign the same priority to
-    #   different `LaunchTemplateOverrides`. EC2 implements the priorities
-    #   on a best-effort basis, but optimizes for capacity first.
-    #   `capacity-optimized-prioritized` is supported only if your fleet
-    #   uses a launch template. Note that if the On-Demand
-    #   `AllocationStrategy` is set to `prioritized`, the same priority is
-    #   applied when fulfilling On-Demand capacity.
+    #   price-capacity-optimized (recommended)
+    #
+    #   : EC2 Fleet identifies the pools with the highest capacity
+    #     availability for the number of instances that are launching. This
+    #     means that we will request Spot Instances from the pools that we
+    #     believe have the lowest chance of interruption in the near term.
+    #     EC2 Fleet then requests Spot Instances from the lowest priced of
+    #     these pools.
+    #
+    #   capacity-optimized
+    #
+    #   : EC2 Fleet identifies the pools with the highest capacity
+    #     availability for the number of instances that are launching. This
+    #     means that we will request Spot Instances from the pools that we
+    #     believe have the lowest chance of interruption in the near term.
+    #     To give certain instance types a higher chance of launching first,
+    #     use `capacity-optimized-prioritized`. Set a priority for each
+    #     instance type by using the `Priority` parameter for
+    #     `LaunchTemplateOverrides`. You can assign the same priority to
+    #     different `LaunchTemplateOverrides`. EC2 implements the priorities
+    #     on a best-effort basis, but optimizes for capacity first.
+    #     `capacity-optimized-prioritized` is supported only if your EC2
+    #     Fleet uses a launch template. Note that if the On-Demand
+    #     `AllocationStrategy` is set to `prioritized`, the same priority is
+    #     applied when fulfilling On-Demand capacity.
+    #
+    #   diversified
+    #
+    #   : EC2 Fleet requests instances from all of the Spot Instance pools
+    #     that you specify.
+    #
+    #   lowest-price
+    #
+    #   : EC2 Fleet requests instances from the lowest priced Spot Instance
+    #     pool that has available capacity. If the lowest priced pool
+    #     doesn't have available capacity, the Spot Instances come from the
+    #     next lowest priced pool that has available capacity. If a pool
+    #     runs out of capacity before fulfilling your desired capacity, EC2
+    #     Fleet will continue to fulfill your request by drawing from the
+    #     next lowest priced pool. To ensure that your desired capacity is
+    #     met, you might receive Spot Instances from several pools. Because
+    #     this strategy only considers instance price and not capacity
+    #     availability, it might lead to high interruption rates.
     #
     #   Default: `lowest-price`
     #

data/lib/aws-sdk-ec2.rb

@@ -76,6 +76,6 @@ require_relative 'aws-sdk-ec2/customizations'
 # @!group service
 module Aws::EC2
 
-  GEM_VERSION = '1.348.0'
+  GEM_VERSION = '1.349.0'
 
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: aws-sdk-ec2
 version: !ruby/object:Gem::Version
-  version: 1.348.0
+  version: 1.349.0
 platform: ruby
 authors:
 - Amazon Web Services
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2022-11-09 00:00:00.000000000 Z
+date: 2022-11-10 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: aws-sigv4