@aws-sdk/client-ec2 3.211.0 → 3.213.0

package/dist-cjs/protocols/Aws_ec2.js

@@ -25096,6 +25096,9 @@ const serializeAws_ec2CreateNatGatewayRequest = (input, context) => {
     if (input.ConnectivityType != null) {
         entries["ConnectivityType"] = input.ConnectivityType;
     }
+    if (input.PrivateIpAddress != null) {
+        entries["PrivateIpAddress"] = input.PrivateIpAddress;
+    }
     return entries;
 };
 const serializeAws_ec2CreateNetworkAclEntryRequest = (input, context) => {

package/dist-es/protocols/Aws_ec2.js

@@ -23978,6 +23978,9 @@ const serializeAws_ec2CreateNatGatewayRequest = (input, context) => {
     if (input.ConnectivityType != null) {
         entries["ConnectivityType"] = input.ConnectivityType;
     }
+    if (input.PrivateIpAddress != null) {
+        entries["PrivateIpAddress"] = input.PrivateIpAddress;
+    }
     return entries;
 };
 const serializeAws_ec2CreateNetworkAclEntryRequest = (input, context) => {

package/dist-types/models/models_1.d.ts

@@ -1097,48 +1097,28 @@ export interface SpotOptionsRequest {
      * <p>The strategy that determines how to allocate the target Spot Instance capacity across the Spot Instance
      *          pools specified by the EC2 Fleet launch configuration. For more information, see <a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-fleet-allocation-strategy.html">Allocation strategies for Spot Instances</a> in the
      *          <i>Amazon EC2 User Guide</i>.</p>
-     *
-     *          <dl>
-     *             <dt>price-capacity-optimized (recommended)</dt>
-     *             <dd>
-     *                <p>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.</p>
-     *             </dd>
-     *             <dt>capacity-optimized</dt>
-     *             <dd>
-     *                <p>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
-     *                   <code>capacity-optimized-prioritized</code>. Set a priority for each instance type by
-     *                   using the <code>Priority</code> parameter for <code>LaunchTemplateOverrides</code>. You can
-     *                   assign the same priority to different <code>LaunchTemplateOverrides</code>. EC2 implements
-     *                   the priorities on a best-effort basis, but optimizes for capacity first.
-     *                   <code>capacity-optimized-prioritized</code> is supported only if your EC2 Fleet uses a
-     *                   launch template. Note that if the On-Demand <code>AllocationStrategy</code> is set to
-     *                   <code>prioritized</code>, the same priority is applied when fulfilling On-Demand
-     *                   capacity.</p>
-     *             </dd>
-     *             <dt>diversified</dt>
-     *             <dd>
-     *                <p>EC2 Fleet requests instances from all of the Spot Instance pools that you
-     *                   specify.</p>
-     *             </dd>
-     *             <dt>lowest-price</dt>
-     *             <dd>
-     *                <p>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.</p>
-     *             </dd>
-     *          </dl>
-     *
+     *          <p>
+     *             <code>lowest-price</code> - 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.</p>
+     *          <p>
+     *             <code>diversified</code> - EC2 Fleet launches instances from all
+     *          of the Spot Instance pools that you specify.</p>
+     *          <p>
+     *             <code>capacity-optimized</code> (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
+     *             <code>capacity-optimized-prioritized</code>. Set a priority for each instance type by
+     *          using the <code>Priority</code> parameter for <code>LaunchTemplateOverrides</code>. You can
+     *          assign the same priority to different <code>LaunchTemplateOverrides</code>. EC2 implements
+     *          the priorities on a best-effort basis, but optimizes for capacity first.
+     *             <code>capacity-optimized-prioritized</code> is supported only if your fleet uses a
+     *          launch template. Note that if the On-Demand <code>AllocationStrategy</code> is set to
+     *             <code>prioritized</code>, the same priority is applied when fulfilling On-Demand
+     *          capacity.</p>
      *          <p>Default: <code>lowest-price</code>
      *          </p>
      */
@@ -2050,7 +2030,8 @@ export interface CreateFlowLogsRequest {
     /**
      * <p>The IDs of the resources to monitor. For example, if the resource type is
      *                 <code>VPC</code>, specify the IDs of the VPCs.</p>
-     *         <p>Constraints: Maximum of 1000 resources</p>
+     *         <p>Constraints: Maximum of 25 for transit gateway resource types. Maximum of 1000 for the
+     *             other resource types.</p>
      */
     ResourceIds: string[] | undefined;
     /**
@@ -2058,8 +2039,9 @@ export interface CreateFlowLogsRequest {
      */
     ResourceType: FlowLogsResourceType | string | undefined;
     /**
-     * <p>The type of traffic to monitor (accepted traffic, rejected traffic, or all
-     *             traffic).</p>
+     * <p>The type of traffic to monitor (accepted traffic, rejected traffic, or all traffic).
+     *             This parameter is not supported for transit gateway resource types. It is required for
+     *             the other resource types.</p>
      */
     TrafficType?: TrafficType | string;
     /**
@@ -2092,10 +2074,11 @@ export interface CreateFlowLogsRequest {
     LogDestination?: string;
     /**
      * <p>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 <a href="https://docs.aws.amazon.com/vpc/latest/userguide/flow-logs.html#flow-log-records">Flow log
-     *                 records</a>. If you omit this parameter, the flow log is created using the
+     *             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.</p>
+     *             field. For more information about the available fields, see <a href="https://docs.aws.amazon.com/vpc/latest/userguide/flow-logs.html#flow-log-records">Flow log
+     *                 records</a> in the <i>Amazon VPC User Guide</i> or <a href="https://docs.aws.amazon.com/vpc/latest/tgw/tgw-flow-logs.html#flow-log-records">Transit Gateway Flow Log
+     *                     records</a> in the <i>Amazon Web Services Transit Gateway Guide</i>.</p>
      *         <p>Specify the fields using the <code>${field-id}</code> format, separated by spaces. For
      *             the CLI, surround this parameter value with single quotes on Linux or
      *             double quotes on Windows.</p>
@@ -2106,7 +2089,9 @@ export interface CreateFlowLogsRequest {
      */
     TagSpecifications?: TagSpecification[];
     /**
-     * <p>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).</p>
+     * <p>The maximum interval of time during which a flow of packets is 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.</p>
      *         <p>When a network interface is attached to a <a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-types.html#ec2-nitro-instances">Nitro-based
      *                 instance</a>, the aggregation interval is always 60 seconds or less, regardless
      *             of the value that you specify.</p>
@@ -5426,6 +5411,10 @@ export interface CreateNatGatewayRequest {
      *           The default is public connectivity.</p>
      */
     ConnectivityType?: ConnectivityType | string;
+    /**
+     * <p>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.</p>
+     */
+    PrivateIpAddress?: string;
 }
 /**
  * <p>Describes the IP addresses and network interface associated with a NAT gateway.</p>

package/dist-types/models/models_3.d.ts

@@ -3099,48 +3099,28 @@ export interface SpotOptions {
      * <p>The strategy that determines how to allocate the target Spot Instance capacity across the Spot Instance
      *          pools specified by the EC2 Fleet launch configuration. For more information, see <a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-fleet-allocation-strategy.html">Allocation strategies for Spot Instances</a> in the
      *          <i>Amazon EC2 User Guide</i>.</p>
-     *
-     *          <dl>
-     *             <dt>price-capacity-optimized (recommended)</dt>
-     *             <dd>
-     *                <p>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.</p>
-     *             </dd>
-     *             <dt>capacity-optimized</dt>
-     *             <dd>
-     *                <p>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
-     *                   <code>capacity-optimized-prioritized</code>. Set a priority for each instance type by
-     *                   using the <code>Priority</code> parameter for <code>LaunchTemplateOverrides</code>. You can
-     *                   assign the same priority to different <code>LaunchTemplateOverrides</code>. EC2 implements
-     *                   the priorities on a best-effort basis, but optimizes for capacity first.
-     *                   <code>capacity-optimized-prioritized</code> is supported only if your EC2 Fleet uses a
-     *                   launch template. Note that if the On-Demand <code>AllocationStrategy</code> is set to
-     *                   <code>prioritized</code>, the same priority is applied when fulfilling On-Demand
-     *                   capacity.</p>
-     *             </dd>
-     *             <dt>diversified</dt>
-     *             <dd>
-     *                <p>EC2 Fleet requests instances from all of the Spot Instance pools that you
-     *                   specify.</p>
-     *             </dd>
-     *             <dt>lowest-price</dt>
-     *             <dd>
-     *                <p>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.</p>
-     *             </dd>
-     *          </dl>
-     *
+     *          <p>
+     *             <code>lowest-price</code> - 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.</p>
+     *          <p>
+     *             <code>diversified</code> - EC2 Fleet launches instances from all of the Spot Instance pools that you
+     *          specify.</p>
+     *          <p>
+     *             <code>capacity-optimized</code> (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
+     *             <code>capacity-optimized-prioritized</code>. Set a priority for each instance type by
+     *          using the <code>Priority</code> parameter for <code>LaunchTemplateOverrides</code>. You can
+     *          assign the same priority to different <code>LaunchTemplateOverrides</code>. EC2 implements
+     *          the priorities on a best-effort basis, but optimizes for capacity first.
+     *             <code>capacity-optimized-prioritized</code> is supported only if your fleet uses a
+     *          launch template. Note that if the On-Demand <code>AllocationStrategy</code> is set to
+     *             <code>prioritized</code>, the same priority is applied when fulfilling On-Demand
+     *          capacity.</p>
      *          <p>Default: <code>lowest-price</code>
      *          </p>
      */

package/dist-types/models/models_4.d.ts

@@ -4364,48 +4364,28 @@ export interface SpotFleetRequestConfigData {
      * <p>The strategy that determines how to allocate the target Spot Instance capacity across the Spot Instance
      *             pools specified by the Spot Fleet launch configuration. For more information, see <a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/spot-fleet-allocation-strategy.html">Allocation
      *                 strategies for Spot Instances</a> in the <i>Amazon EC2 User Guide</i>.</p>
-     *
-     *          <dl>
-     *             <dt>priceCapacityOptimized (recommended)</dt>
-     *             <dd>
-     *                 <p>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.</p>
-     *              </dd>
-     *             <dt>capacityOptimized</dt>
-     *             <dd>
-     *                 <p>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
-     *           <code>capacityOptimizedPrioritized</code>. Set a priority for each instance type by
-     *           using the <code>Priority</code> parameter for <code>LaunchTemplateOverrides</code>. You can
-     *           assign the same priority to different <code>LaunchTemplateOverrides</code>. EC2 implements
-     *           the priorities on a best-effort basis, but optimizes for capacity first.
-     *           <code>capacityOptimizedPrioritized</code> is supported only if your Spot Fleet uses a
-     *           launch template. Note that if the <code>OnDemandAllocationStrategy</code> is set to
-     *           <code>prioritized</code>, the same priority is applied when fulfilling On-Demand
-     *           capacity.</p>
-     *              </dd>
-     *             <dt>diversified</dt>
-     *             <dd>
-     *                 <p>Spot Fleet requests instances from all of the Spot Instance pools that you
-     *           specify.</p>
-     *              </dd>
-     *             <dt>lowestPrice</dt>
-     *             <dd>
-     *                 <p>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.</p>
-     *              </dd>
-     *          </dl>
-     *
+     *         <p>
+     *             <code>lowestPrice</code> - 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.</p>
+     *         <p>
+     *             <code>diversified</code> - Spot Fleet launches instances from all of the Spot Instance pools that you
+     *             specify.</p>
+     *         <p>
+     *             <code>capacityOptimized</code> (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
+     *             <code>capacityOptimizedPrioritized</code>. Set a priority for each instance type by
+     *             using the <code>Priority</code> parameter for <code>LaunchTemplateOverrides</code>. You can
+     *             assign the same priority to different <code>LaunchTemplateOverrides</code>. EC2 implements
+     *             the priorities on a best-effort basis, but optimizes for capacity first.
+     *             <code>capacityOptimizedPrioritized</code> is supported only if your Spot Fleet uses a
+     *             launch template. Note that if the <code>OnDemandAllocationStrategy</code> is set to
+     *             <code>prioritized</code>, the same priority is applied when fulfilling On-Demand
+     *             capacity.</p>
      *         <p>Default: <code>lowestPrice</code>
      *          </p>
      */

package/dist-types/ts3.4/models/models_1.d.ts

@@ -1357,6 +1357,7 @@ export interface CreateNatGatewayRequest {
   SubnetId: string | undefined;
   TagSpecifications?: TagSpecification[];
   ConnectivityType?: ConnectivityType | string;
+  PrivateIpAddress?: string;
 }
 export interface NatGatewayAddress {
   AllocationId?: string;

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@aws-sdk/client-ec2",
   "description": "AWS SDK for JavaScript Ec2 Client for Node.js, Browser and React Native",
-  "version": "3.211.0",
+  "version": "3.213.0",
   "scripts": {
     "build": "concurrently 'yarn:build:cjs' 'yarn:build:es' 'yarn:build:types'",
     "build:cjs": "tsc -p tsconfig.cjs.json",
@@ -19,40 +19,40 @@
   "dependencies": {
     "@aws-crypto/sha256-browser": "2.0.0",
     "@aws-crypto/sha256-js": "2.0.0",
-    "@aws-sdk/client-sts": "3.211.0",
-    "@aws-sdk/config-resolver": "3.209.0",
-    "@aws-sdk/credential-provider-node": "3.211.0",
-    "@aws-sdk/fetch-http-handler": "3.208.0",
-    "@aws-sdk/hash-node": "3.208.0",
-    "@aws-sdk/invalid-dependency": "3.208.0",
-    "@aws-sdk/middleware-content-length": "3.208.0",
-    "@aws-sdk/middleware-endpoint": "3.208.0",
-    "@aws-sdk/middleware-host-header": "3.208.0",
-    "@aws-sdk/middleware-logger": "3.208.0",
-    "@aws-sdk/middleware-recursion-detection": "3.208.0",
-    "@aws-sdk/middleware-retry": "3.209.0",
-    "@aws-sdk/middleware-sdk-ec2": "3.208.0",
-    "@aws-sdk/middleware-serde": "3.208.0",
-    "@aws-sdk/middleware-signing": "3.208.0",
-    "@aws-sdk/middleware-stack": "3.208.0",
-    "@aws-sdk/middleware-user-agent": "3.208.0",
-    "@aws-sdk/node-config-provider": "3.209.0",
-    "@aws-sdk/node-http-handler": "3.208.0",
-    "@aws-sdk/protocol-http": "3.208.0",
-    "@aws-sdk/smithy-client": "3.209.0",
-    "@aws-sdk/types": "3.208.0",
-    "@aws-sdk/url-parser": "3.208.0",
+    "@aws-sdk/client-sts": "3.213.0",
+    "@aws-sdk/config-resolver": "3.212.0",
+    "@aws-sdk/credential-provider-node": "3.212.0",
+    "@aws-sdk/fetch-http-handler": "3.212.0",
+    "@aws-sdk/hash-node": "3.212.0",
+    "@aws-sdk/invalid-dependency": "3.212.0",
+    "@aws-sdk/middleware-content-length": "3.212.0",
+    "@aws-sdk/middleware-endpoint": "3.212.0",
+    "@aws-sdk/middleware-host-header": "3.212.0",
+    "@aws-sdk/middleware-logger": "3.212.0",
+    "@aws-sdk/middleware-recursion-detection": "3.212.0",
+    "@aws-sdk/middleware-retry": "3.212.0",
+    "@aws-sdk/middleware-sdk-ec2": "3.212.0",
+    "@aws-sdk/middleware-serde": "3.212.0",
+    "@aws-sdk/middleware-signing": "3.212.0",
+    "@aws-sdk/middleware-stack": "3.212.0",
+    "@aws-sdk/middleware-user-agent": "3.212.0",
+    "@aws-sdk/node-config-provider": "3.212.0",
+    "@aws-sdk/node-http-handler": "3.212.0",
+    "@aws-sdk/protocol-http": "3.212.0",
+    "@aws-sdk/smithy-client": "3.212.0",
+    "@aws-sdk/types": "3.212.0",
+    "@aws-sdk/url-parser": "3.212.0",
     "@aws-sdk/util-base64": "3.208.0",
     "@aws-sdk/util-body-length-browser": "3.188.0",
     "@aws-sdk/util-body-length-node": "3.208.0",
-    "@aws-sdk/util-defaults-mode-browser": "3.209.0",
-    "@aws-sdk/util-defaults-mode-node": "3.209.0",
-    "@aws-sdk/util-endpoints": "3.211.0",
-    "@aws-sdk/util-user-agent-browser": "3.208.0",
-    "@aws-sdk/util-user-agent-node": "3.209.0",
+    "@aws-sdk/util-defaults-mode-browser": "3.212.0",
+    "@aws-sdk/util-defaults-mode-node": "3.212.0",
+    "@aws-sdk/util-endpoints": "3.212.0",
+    "@aws-sdk/util-user-agent-browser": "3.212.0",
+    "@aws-sdk/util-user-agent-node": "3.212.0",
     "@aws-sdk/util-utf8-browser": "3.188.0",
     "@aws-sdk/util-utf8-node": "3.208.0",
-    "@aws-sdk/util-waiter": "3.208.0",
+    "@aws-sdk/util-waiter": "3.212.0",
     "fast-xml-parser": "4.0.11",
     "tslib": "^2.3.1",
     "uuid": "^8.3.2"