aws-sdk-ec2 1.349.0 → 1.350.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: bfcf334f96306b62b0cf8d8c0fcd1fdd03297bef34acc16517caf7e382361682
-  data.tar.gz: 394acca3282f8247d29596e702360b6b6c3ef803d79164c4d1be2ec4052e07c2
+  metadata.gz: d3605da6fc357f9f71fd0729b458aaa70388bdca09615f4442832d83a2d6dc97
+  data.tar.gz: a9ca870782a8d2347b5be1570bc29f9fa1740cacde738901e11103fc6d4ddd39
 SHA512:
-  metadata.gz: a411b555002a85b22e62aefc8a5c2f069d9ee00d5633befb4599d6bbb4c2543dca055701f96b0cc4ea4ddc2d3bb8cffb3be0ee12b5038168360a5a3708363215
-  data.tar.gz: cfc030a085c74f3c660487de6c332c9c90960ea3a909997c2e1a9e0d8f76e88033a1e728b19e1a17ae7ac16243924af7943c03cc44a6888ba80b958bf41c2b90
+  metadata.gz: c5e9db5789689e2e25dc8931855abf3f3707b3278816b392fa8026cda8fc7ec6f2959fbb1ed0279c5fa14ee6f01cee54b2c8b5d6be584265320aae65fe254c1a
+  data.tar.gz: e418c48319224d85e342b63f13a366612755c15183c12ed6870a71f5167b5c63e9d8f5328a11ffccf930e476cf29419294721a8f448c112954b2bd1f94fae16c

data/CHANGELOG.md

@@ -1,6 +1,11 @@
 Unreleased Changes
 ------------------
 
+1.350.0 (2022-11-17)
+------------------
+
+* Feature - This release adds a new optional parameter "privateIpAddress" for the CreateNatGateway API. PrivateIPAddress will allow customers to select a custom Private IPv4 address instead of having it be auto-assigned.
+
 1.349.0 (2022-11-10)
 ------------------
 

data/VERSION

@@ -1 +1 @@
-1.349.0
+1.350.0

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

@@ -6246,14 +6246,16 @@ module Aws::EC2
     #   The IDs of the resources to monitor. For example, if the resource type
     #   is `VPC`, specify the IDs of the VPCs.
     #
-    #   Constraints: Maximum of 1000 resources
+    #   Constraints: Maximum of 25 for transit gateway resource types. Maximum
+    #   of 1000 for the other resource types.
     #
     # @option params [required, String] :resource_type
     #   The type of resource to monitor.
     #
     # @option params [String] :traffic_type
     #   The type of traffic to monitor (accepted traffic, rejected traffic, or
-    #   all traffic).
+    #   all traffic). This parameter is not supported for transit gateway
+    #   resource types. It is required for the other resource types.
     #
     # @option params [String] :log_destination_type
     #   The type of destination for the flow log data.
@@ -6286,10 +6288,12 @@ module Aws::EC2
     #
     # @option params [String] :log_format
     #   The fields to include in the flow log record. List the fields in the
-    #   order in which they should appear. For more information about the
-    #   available fields, see [Flow log records][1]. If you omit this
-    #   parameter, the flow log is created using the default format. If you
-    #   specify this parameter, you must include at least one field.
+    #   order in which they should appear. If you omit this parameter, the
+    #   flow log is created using the default format. If you specify this
+    #   parameter, you must include at least one field. For more information
+    #   about the available fields, see [Flow log records][1] in the *Amazon
+    #   VPC User Guide* or [Transit Gateway Flow Log records][2] in the
+    #   *Amazon Web Services Transit Gateway Guide*.
     #
     #   Specify the fields using the `$\{field-id\}` format, separated by
     #   spaces. For the CLI, surround this parameter value with single quotes
@@ -6298,14 +6302,16 @@ module Aws::EC2
     #
     #
     #   [1]: https://docs.aws.amazon.com/vpc/latest/userguide/flow-logs.html#flow-log-records
+    #   [2]: https://docs.aws.amazon.com/vpc/latest/tgw/tgw-flow-logs.html#flow-log-records
     #
     # @option params [Array<Types::TagSpecification>] :tag_specifications
     #   The tags to apply to the flow logs.
     #
     # @option params [Integer] :max_aggregation_interval
     #   The maximum interval of time during which a flow of packets is
-    #   captured and aggregated into a flow log record. You can specify 60
-    #   seconds (1 minute) or 600 seconds (10 minutes).
+    #   captured and aggregated into a flow log record. The possible values
+    #   are 60 seconds (1 minute) or 600 seconds (10 minutes). This parameter
+    #   must be 60 seconds for transit gateway resource types.
     #
     #   When a network interface is attached to a [Nitro-based instance][1],
     #   the aggregation interval is always 60 seconds or less, regardless of
@@ -8718,6 +8724,11 @@ module Aws::EC2
     #   Indicates whether the NAT gateway supports public or private
     #   connectivity. The default is public connectivity.
     #
+    # @option params [String] :private_ip_address
+    #   The private IPv4 address to assign to the NAT gateway. If you don't
+    #   provide an address, a private IPv4 address will be automatically
+    #   assigned.
+    #
     # @return [Types::CreateNatGatewayResult] Returns a {Seahorse::Client::Response response} object which responds to the following methods:
     #
     #   * {Types::CreateNatGatewayResult#client_token #client_token} => String
@@ -8769,6 +8780,7 @@ module Aws::EC2
     #       },
     #     ],
     #     connectivity_type: "private", # accepts private, public
+    #     private_ip_address: "String",
     #   })
     #
     # @example Response structure
@@ -52578,7 +52590,7 @@ module Aws::EC2
         params: params,
         config: config)
       context[:gem_name] = 'aws-sdk-ec2'
-      context[:gem_version] = '1.349.0'
+      context[:gem_version] = '1.350.0'
       Seahorse::Client::Request.new(handlers, context)
     end
 

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

@@ -4349,6 +4349,7 @@ module Aws::EC2
     CreateNatGatewayRequest.add_member(:subnet_id, Shapes::ShapeRef.new(shape: SubnetId, required: true, location_name: "SubnetId"))
     CreateNatGatewayRequest.add_member(:tag_specifications, Shapes::ShapeRef.new(shape: TagSpecificationList, location_name: "TagSpecification"))
     CreateNatGatewayRequest.add_member(:connectivity_type, Shapes::ShapeRef.new(shape: ConnectivityType, location_name: "ConnectivityType"))
+    CreateNatGatewayRequest.add_member(:private_ip_address, Shapes::ShapeRef.new(shape: String, location_name: "PrivateIpAddress"))
     CreateNatGatewayRequest.struct_class = Types::CreateNatGatewayRequest
 
     CreateNatGatewayResult.add_member(:client_token, Shapes::ShapeRef.new(shape: String, location_name: "clientToken"))

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

@@ -705,6 +705,7 @@ module Aws::EC2
     #       },
     #     ],
     #     connectivity_type: "private", # accepts private, public
+    #     private_ip_address: "String",
     #   })
     # @param [Hash] options ({})
     # @option options [String] :allocation_id
@@ -735,6 +736,10 @@ module Aws::EC2
     # @option options [String] :connectivity_type
     #   Indicates whether the NAT gateway supports public or private
     #   connectivity. The default is public connectivity.
+    # @option options [String] :private_ip_address
+    #   The private IPv4 address to assign to the NAT gateway. If you don't
+    #   provide an address, a private IPv4 address will be automatically
+    #   assigned.
     # @return [NatGateway]
     def create_nat_gateway(options = {})
       resp = @client.create_nat_gateway(options)

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

@@ -8561,7 +8561,8 @@ module Aws::EC2
     #   The IDs of the resources to monitor. For example, if the resource
     #   type is `VPC`, specify the IDs of the VPCs.
     #
-    #   Constraints: Maximum of 1000 resources
+    #   Constraints: Maximum of 25 for transit gateway resource types.
+    #   Maximum of 1000 for the other resource types.
     #   @return [Array<String>]
     #
     # @!attribute [rw] resource_type
@@ -8570,7 +8571,8 @@ module Aws::EC2
     #
     # @!attribute [rw] traffic_type
     #   The type of traffic to monitor (accepted traffic, rejected traffic,
-    #   or all traffic).
+    #   or all traffic). This parameter is not supported for transit gateway
+    #   resource types. It is required for the other resource types.
     #   @return [String]
     #
     # @!attribute [rw] log_destination_type
@@ -8606,10 +8608,12 @@ module Aws::EC2
     #
     # @!attribute [rw] log_format
     #   The fields to include in the flow log record. List the fields in the
-    #   order in which they should appear. For more information about the
-    #   available fields, see [Flow log records][1]. If you omit this
-    #   parameter, the flow log is created using the default format. If you
-    #   specify this parameter, you must include at least one field.
+    #   order in which they should appear. If you omit this parameter, the
+    #   flow log is created using the default format. If you specify this
+    #   parameter, you must include at least one field. For more information
+    #   about the available fields, see [Flow log records][1] in the *Amazon
+    #   VPC User Guide* or [Transit Gateway Flow Log records][2] in the
+    #   *Amazon Web Services Transit Gateway Guide*.
     #
     #   Specify the fields using the `$\{field-id\}` format, separated by
     #   spaces. For the CLI, surround this parameter value with single
@@ -8618,6 +8622,7 @@ module Aws::EC2
     #
     #
     #   [1]: https://docs.aws.amazon.com/vpc/latest/userguide/flow-logs.html#flow-log-records
+    #   [2]: https://docs.aws.amazon.com/vpc/latest/tgw/tgw-flow-logs.html#flow-log-records
     #   @return [String]
     #
     # @!attribute [rw] tag_specifications
@@ -8626,8 +8631,9 @@ module Aws::EC2
     #
     # @!attribute [rw] max_aggregation_interval
     #   The maximum interval of time during which a flow of packets is
-    #   captured and aggregated into a flow log record. You can specify 60
-    #   seconds (1 minute) or 600 seconds (10 minutes).
+    #   captured and aggregated into a flow log record. The possible values
+    #   are 60 seconds (1 minute) or 600 seconds (10 minutes). This
+    #   parameter must be 60 seconds for transit gateway resource types.
     #
     #   When a network interface is attached to a [Nitro-based instance][1],
     #   the aggregation interval is always 60 seconds or less, regardless of
@@ -10559,6 +10565,7 @@ module Aws::EC2
     #           },
     #         ],
     #         connectivity_type: "private", # accepts private, public
+    #         private_ip_address: "String",
     #       }
     #
     # @!attribute [rw] allocation_id
@@ -10604,6 +10611,12 @@ module Aws::EC2
     #   connectivity. The default is public connectivity.
     #   @return [String]
     #
+    # @!attribute [rw] private_ip_address
+    #   The private IPv4 address to assign to the NAT gateway. If you don't
+    #   provide an address, a private IPv4 address will be automatically
+    #   assigned.
+    #   @return [String]
+    #
     # @see http://docs.aws.amazon.com/goto/WebAPI/ec2-2016-11-15/CreateNatGatewayRequest AWS API Documentation
     #
     class CreateNatGatewayRequest < Struct.new(
@@ -10612,7 +10625,8 @@ module Aws::EC2
       :dry_run,
       :subnet_id,
       :tag_specifications,
-      :connectivity_type)
+      :connectivity_type,
+      :private_ip_address)
       SENSITIVE = []
       include Aws::Structure
     end
@@ -65712,49 +65726,31 @@ module Aws::EC2
     #   [Allocation strategies for Spot Instances][1] in the *Amazon EC2
     #   User Guide*.
     #
-    #   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.
+    #   `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.
     #
     #   Default: `lowestPrice`
     #
@@ -66341,49 +66337,31 @@ module Aws::EC2
     #   [Allocation strategies for Spot Instances][1] in the *Amazon EC2
     #   User Guide*.
     #
-    #   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.
+    #   `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.
     #
     #   Default: `lowest-price`
     #
@@ -66501,49 +66479,31 @@ module Aws::EC2
     #   [Allocation strategies for Spot Instances][1] in the *Amazon EC2
     #   User Guide*.
     #
-    #   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.
+    #   `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.
     #
     #   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.349.0'
+  GEM_VERSION = '1.350.0'
 
 end

metadata

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