@aws-sdk/client-auto-scaling 3.304.0 → 3.306.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.
Files changed (10) hide show
  1. package/dist-types/AutoScaling.d.ts +38 -44
  2. package/dist-types/commands/AttachLoadBalancerTargetGroupsCommand.d.ts +6 -7
  3. package/dist-types/commands/AttachLoadBalancersCommand.d.ts +6 -7
  4. package/dist-types/commands/AttachTrafficSourcesCommand.d.ts +2 -2
  5. package/dist-types/commands/DescribeLoadBalancerTargetGroupsCommand.d.ts +6 -7
  6. package/dist-types/commands/DescribeLoadBalancersCommand.d.ts +6 -7
  7. package/dist-types/commands/DetachLoadBalancerTargetGroupsCommand.d.ts +6 -7
  8. package/dist-types/commands/DetachLoadBalancersCommand.d.ts +6 -7
  9. package/dist-types/models/models_0.d.ts +9 -5
  10. package/package.json +30 -30
package/dist-types/AutoScaling.d.ts CHANGED
@@ -92,13 +92,12 @@ export declare class AutoScaling extends AutoScalingClient {
92
92
  /**
93
93
  * @public
94
94
  * <note>
95
- * <p>This API call has been replaced with a new "traffic sources" API call
96
- * (<code>AttachTrafficSources</code>) that can attach multiple traffic sources
97
- * types. While we continue to support <code>AttachLoadBalancers</code>, and you can
98
- * use both the original <code>AttachLoadBalancers</code> API call and the new
99
- * <code>AttachTrafficSources</code> API call on the same Auto Scaling group, we recommend
100
- * using the new "traffic sources" API call to simplify how you manage traffic
101
- * sources.</p>
95
+ * <p>This API operation is superseded by <a>AttachTrafficSources</a>, which
96
+ * can attach multiple traffic sources types. We recommend using
97
+ * <code>AttachTrafficSources</code> to simplify how you manage traffic sources.
98
+ * However, we continue to support <code>AttachLoadBalancers</code>. You can use both
99
+ * the original <code>AttachLoadBalancers</code> API operation and
100
+ * <code>AttachTrafficSources</code> on the same Auto Scaling group.</p>
102
101
  * </note>
103
102
  * <p>Attaches one or more Classic Load Balancers to the specified Auto Scaling group. Amazon EC2 Auto Scaling registers the
104
103
  * running instances with these Classic Load Balancers.</p>
@@ -116,13 +115,12 @@ export declare class AutoScaling extends AutoScalingClient {
116
115
  /**
117
116
  * @public
118
117
  * <note>
119
- * <p>This API call has been replaced with a new "traffic sources" API call
120
- * (<code>AttachTrafficSources</code>) that can attach multiple traffic sources
121
- * types. While we continue to support <code>AttachLoadBalancerTargetGroups</code>, and
122
- * you can use both the original <code>AttachLoadBalancerTargetGroups</code> API call
123
- * and the new <code>AttachTrafficSources</code> API call on the same Auto Scaling group, we
124
- * recommend using the new "traffic sources" API call to simplify how you manage
125
- * traffic sources.</p>
118
+ * <p>This API operation is superseded by <a>AttachTrafficSources</a>, which
119
+ * can attach multiple traffic sources types. We recommend using
120
+ * <code>AttachTrafficSources</code> to simplify how you manage traffic sources.
121
+ * However, we continue to support <code>AttachLoadBalancerTargetGroups</code>. You can
122
+ * use both the original <code>AttachLoadBalancerTargetGroups</code> API operation and
123
+ * <code>AttachTrafficSources</code> on the same Auto Scaling group.</p>
126
124
  * </note>
127
125
  * <p>Attaches one or more target groups to the specified Auto Scaling group.</p>
128
126
  * <p>This operation is used with the following load balancer types: </p>
@@ -162,10 +160,10 @@ export declare class AutoScaling extends AutoScalingClient {
162
160
  * <p>Classic Load Balancer</p>
163
161
  * </li>
164
162
  * <li>
165
- * <p>Network Load Balancer</p>
163
+ * <p>Gateway Load Balancer</p>
166
164
  * </li>
167
165
  * <li>
168
- * <p>Gateway Load Balancer</p>
166
+ * <p>Network Load Balancer</p>
169
167
  * </li>
170
168
  * <li>
171
169
  * <p>VPC Lattice</p>
@@ -505,13 +503,12 @@ export declare class AutoScaling extends AutoScalingClient {
505
503
  /**
506
504
  * @public
507
505
  * <note>
508
- * <p>This API call has been replaced with a new "traffic sources" API call
509
- * (<code>DescribeTrafficSources</code>) that can describe multiple traffic sources
510
- * types. While we continue to support <code>DescribeLoadBalancers</code>, and you can
511
- * use both the original <code>DescribeLoadBalancers</code> API call and the new
512
- * <code>DescribeTrafficSources</code> API call on the same Auto Scaling group, we
513
- * recommend using the new "traffic sources" API call to simplify how you manage
514
- * traffic sources.</p>
506
+ * <p>This API operation is superseded by <a>DescribeTrafficSources</a>,
507
+ * which can describe multiple traffic sources types. We recommend using
508
+ * <code>DescribeTrafficSources</code> to simplify how you manage traffic sources.
509
+ * However, we continue to support <code>DescribeLoadBalancers</code>. You can use both
510
+ * the original <code>DescribeLoadBalancers</code> API operation and
511
+ * <code>DescribeTrafficSources</code> on the same Auto Scaling group.</p>
515
512
  * </note>
516
513
  * <p>Gets information about the load balancers for the specified Auto Scaling group.</p>
517
514
  * <p>This operation describes only Classic Load Balancers. If you have Application Load Balancers, Network Load Balancers, or Gateway Load Balancers, use the
@@ -543,13 +540,12 @@ export declare class AutoScaling extends AutoScalingClient {
543
540
  /**
544
541
  * @public
545
542
  * <note>
546
- * <p>This API call has been replaced with a new "traffic sources" API call
547
- * (<code>DescribeTrafficSources</code>) that can describe multiple traffic sources
548
- * types. While we continue to support <code>DescribeLoadBalancerTargetGroups</code>,
549
- * and you can use both the original <code>DescribeLoadBalancerTargetGroups</code> API
550
- * call and the new <code>DescribeTrafficSources</code> API call on the same Auto Scaling
551
- * group, we recommend using the new "traffic sources" API call to simplify how you
552
- * manage traffic sources.</p>
543
+ * <p>This API operation is superseded by <a>DescribeTrafficSources</a>,
544
+ * which can describe multiple traffic sources types. We recommend using
545
+ * <code>DetachTrafficSources</code> to simplify how you manage traffic sources.
546
+ * However, we continue to support <code>DescribeLoadBalancerTargetGroups</code>. You
547
+ * can use both the original <code>DescribeLoadBalancerTargetGroups</code> API
548
+ * operation and <code>DescribeTrafficSources</code> on the same Auto Scaling group.</p>
553
549
  * </note>
554
550
  * <p>Gets information about the Elastic Load Balancing target groups for the specified Auto Scaling group.</p>
555
551
  * <p>To determine the attachment status of the target group, use the <code>State</code>
@@ -699,13 +695,12 @@ export declare class AutoScaling extends AutoScalingClient {
699
695
  /**
700
696
  * @public
701
697
  * <note>
702
- * <p>This API call has been replaced with a new "traffic sources" API call
703
- * (<code>DetachTrafficSources</code>) that can detach multiple traffic sources
704
- * types. While we continue to support <code>DetachLoadBalancers</code>, and you can
705
- * use both the original <code>DetachLoadBalancers</code> API call and the new
706
- * <code>DetachTrafficSources</code> API call on the same Auto Scaling group, we recommend
707
- * using the new "traffic sources" API call to simplify how you manage traffic
708
- * sources.</p>
698
+ * <p>This API operation is superseded by <a>DetachTrafficSources</a>, which
699
+ * can detach multiple traffic sources types. We recommend using
700
+ * <code>DetachTrafficSources</code> to simplify how you manage traffic sources.
701
+ * However, we continue to support <code>DetachLoadBalancers</code>. You can use both
702
+ * the original <code>DetachLoadBalancers</code> API operation and
703
+ * <code>DetachTrafficSources</code> on the same Auto Scaling group.</p>
709
704
  * </note>
710
705
  * <p>Detaches one or more Classic Load Balancers from the specified Auto Scaling group.</p>
711
706
  * <p>This operation detaches only Classic Load Balancers. If you have Application Load Balancers, Network Load Balancers, or
@@ -720,13 +715,12 @@ export declare class AutoScaling extends AutoScalingClient {
720
715
  /**
721
716
  * @public
722
717
  * <note>
723
- * <p>This API call has been replaced with a new "traffic sources" API call
724
- * (<code>DetachTrafficSources</code>) that can detach multiple traffic sources
725
- * types. While we continue to support <code>DetachLoadBalancerTargetGroups</code>, and
726
- * you can use both the original <code>DetachLoadBalancerTargetGroups</code> API call
727
- * and the new <code>DetachTrafficSources</code> API call on the same Auto Scaling group, we
728
- * recommend using the new "traffic sources" API call to simplify how you manage
729
- * traffic sources.</p>
718
+ * <p>This API operation is superseded by <a>DetachTrafficSources</a>, which
719
+ * can detach multiple traffic sources types. We recommend using
720
+ * <code>DetachTrafficSources</code> to simplify how you manage traffic sources.
721
+ * However, we continue to support <code>DetachLoadBalancerTargetGroups</code>. You can
722
+ * use both the original <code>DetachLoadBalancerTargetGroups</code> API operation and
723
+ * <code>DetachTrafficSources</code> on the same Auto Scaling group.</p>
730
724
  * </note>
731
725
  * <p>Detaches one or more target groups from the specified Auto Scaling group.</p>
732
726
  * <p>When you detach a target group, it enters the <code>Removing</code> state while
package/dist-types/commands/AttachLoadBalancerTargetGroupsCommand.d.ts CHANGED
@@ -20,13 +20,12 @@ export interface AttachLoadBalancerTargetGroupsCommandOutput extends AttachLoadB
20
20
  /**
21
21
  * @public
22
22
  * <note>
23
- * <p>This API call has been replaced with a new "traffic sources" API call
24
- * (<code>AttachTrafficSources</code>) that can attach multiple traffic sources
25
- * types. While we continue to support <code>AttachLoadBalancerTargetGroups</code>, and
26
- * you can use both the original <code>AttachLoadBalancerTargetGroups</code> API call
27
- * and the new <code>AttachTrafficSources</code> API call on the same Auto Scaling group, we
28
- * recommend using the new "traffic sources" API call to simplify how you manage
29
- * traffic sources.</p>
23
+ * <p>This API operation is superseded by <a>AttachTrafficSources</a>, which
24
+ * can attach multiple traffic sources types. We recommend using
25
+ * <code>AttachTrafficSources</code> to simplify how you manage traffic sources.
26
+ * However, we continue to support <code>AttachLoadBalancerTargetGroups</code>. You can
27
+ * use both the original <code>AttachLoadBalancerTargetGroups</code> API operation and
28
+ * <code>AttachTrafficSources</code> on the same Auto Scaling group.</p>
30
29
  * </note>
31
30
  * <p>Attaches one or more target groups to the specified Auto Scaling group.</p>
32
31
  * <p>This operation is used with the following load balancer types: </p>
package/dist-types/commands/AttachLoadBalancersCommand.d.ts CHANGED
@@ -20,13 +20,12 @@ export interface AttachLoadBalancersCommandOutput extends AttachLoadBalancersRes
20
20
  /**
21
21
  * @public
22
22
  * <note>
23
- * <p>This API call has been replaced with a new "traffic sources" API call
24
- * (<code>AttachTrafficSources</code>) that can attach multiple traffic sources
25
- * types. While we continue to support <code>AttachLoadBalancers</code>, and you can
26
- * use both the original <code>AttachLoadBalancers</code> API call and the new
27
- * <code>AttachTrafficSources</code> API call on the same Auto Scaling group, we recommend
28
- * using the new "traffic sources" API call to simplify how you manage traffic
29
- * sources.</p>
23
+ * <p>This API operation is superseded by <a>AttachTrafficSources</a>, which
24
+ * can attach multiple traffic sources types. We recommend using
25
+ * <code>AttachTrafficSources</code> to simplify how you manage traffic sources.
26
+ * However, we continue to support <code>AttachLoadBalancers</code>. You can use both
27
+ * the original <code>AttachLoadBalancers</code> API operation and
28
+ * <code>AttachTrafficSources</code> on the same Auto Scaling group.</p>
30
29
  * </note>
31
30
  * <p>Attaches one or more Classic Load Balancers to the specified Auto Scaling group. Amazon EC2 Auto Scaling registers the
32
31
  * running instances with these Classic Load Balancers.</p>
package/dist-types/commands/AttachTrafficSourcesCommand.d.ts CHANGED
@@ -29,10 +29,10 @@ export interface AttachTrafficSourcesCommandOutput extends AttachTrafficSourcesR
29
29
  * <p>Classic Load Balancer</p>
30
30
  * </li>
31
31
  * <li>
32
- * <p>Network Load Balancer</p>
32
+ * <p>Gateway Load Balancer</p>
33
33
  * </li>
34
34
  * <li>
35
- * <p>Gateway Load Balancer</p>
35
+ * <p>Network Load Balancer</p>
36
36
  * </li>
37
37
  * <li>
38
38
  * <p>VPC Lattice</p>
package/dist-types/commands/DescribeLoadBalancerTargetGroupsCommand.d.ts CHANGED
@@ -20,13 +20,12 @@ export interface DescribeLoadBalancerTargetGroupsCommandOutput extends DescribeL
20
20
  /**
21
21
  * @public
22
22
  * <note>
23
- * <p>This API call has been replaced with a new "traffic sources" API call
24
- * (<code>DescribeTrafficSources</code>) that can describe multiple traffic sources
25
- * types. While we continue to support <code>DescribeLoadBalancerTargetGroups</code>,
26
- * and you can use both the original <code>DescribeLoadBalancerTargetGroups</code> API
27
- * call and the new <code>DescribeTrafficSources</code> API call on the same Auto Scaling
28
- * group, we recommend using the new "traffic sources" API call to simplify how you
29
- * manage traffic sources.</p>
23
+ * <p>This API operation is superseded by <a>DescribeTrafficSources</a>,
24
+ * which can describe multiple traffic sources types. We recommend using
25
+ * <code>DetachTrafficSources</code> to simplify how you manage traffic sources.
26
+ * However, we continue to support <code>DescribeLoadBalancerTargetGroups</code>. You
27
+ * can use both the original <code>DescribeLoadBalancerTargetGroups</code> API
28
+ * operation and <code>DescribeTrafficSources</code> on the same Auto Scaling group.</p>
30
29
  * </note>
31
30
  * <p>Gets information about the Elastic Load Balancing target groups for the specified Auto Scaling group.</p>
32
31
  * <p>To determine the attachment status of the target group, use the <code>State</code>
package/dist-types/commands/DescribeLoadBalancersCommand.d.ts CHANGED
@@ -20,13 +20,12 @@ export interface DescribeLoadBalancersCommandOutput extends DescribeLoadBalancer
20
20
  /**
21
21
  * @public
22
22
  * <note>
23
- * <p>This API call has been replaced with a new "traffic sources" API call
24
- * (<code>DescribeTrafficSources</code>) that can describe multiple traffic sources
25
- * types. While we continue to support <code>DescribeLoadBalancers</code>, and you can
26
- * use both the original <code>DescribeLoadBalancers</code> API call and the new
27
- * <code>DescribeTrafficSources</code> API call on the same Auto Scaling group, we
28
- * recommend using the new "traffic sources" API call to simplify how you manage
29
- * traffic sources.</p>
23
+ * <p>This API operation is superseded by <a>DescribeTrafficSources</a>,
24
+ * which can describe multiple traffic sources types. We recommend using
25
+ * <code>DescribeTrafficSources</code> to simplify how you manage traffic sources.
26
+ * However, we continue to support <code>DescribeLoadBalancers</code>. You can use both
27
+ * the original <code>DescribeLoadBalancers</code> API operation and
28
+ * <code>DescribeTrafficSources</code> on the same Auto Scaling group.</p>
30
29
  * </note>
31
30
  * <p>Gets information about the load balancers for the specified Auto Scaling group.</p>
32
31
  * <p>This operation describes only Classic Load Balancers. If you have Application Load Balancers, Network Load Balancers, or Gateway Load Balancers, use the
package/dist-types/commands/DetachLoadBalancerTargetGroupsCommand.d.ts CHANGED
@@ -20,13 +20,12 @@ export interface DetachLoadBalancerTargetGroupsCommandOutput extends DetachLoadB
20
20
  /**
21
21
  * @public
22
22
  * <note>
23
- * <p>This API call has been replaced with a new "traffic sources" API call
24
- * (<code>DetachTrafficSources</code>) that can detach multiple traffic sources
25
- * types. While we continue to support <code>DetachLoadBalancerTargetGroups</code>, and
26
- * you can use both the original <code>DetachLoadBalancerTargetGroups</code> API call
27
- * and the new <code>DetachTrafficSources</code> API call on the same Auto Scaling group, we
28
- * recommend using the new "traffic sources" API call to simplify how you manage
29
- * traffic sources.</p>
23
+ * <p>This API operation is superseded by <a>DetachTrafficSources</a>, which
24
+ * can detach multiple traffic sources types. We recommend using
25
+ * <code>DetachTrafficSources</code> to simplify how you manage traffic sources.
26
+ * However, we continue to support <code>DetachLoadBalancerTargetGroups</code>. You can
27
+ * use both the original <code>DetachLoadBalancerTargetGroups</code> API operation and
28
+ * <code>DetachTrafficSources</code> on the same Auto Scaling group.</p>
30
29
  * </note>
31
30
  * <p>Detaches one or more target groups from the specified Auto Scaling group.</p>
32
31
  * <p>When you detach a target group, it enters the <code>Removing</code> state while
package/dist-types/commands/DetachLoadBalancersCommand.d.ts CHANGED
@@ -20,13 +20,12 @@ export interface DetachLoadBalancersCommandOutput extends DetachLoadBalancersRes
20
20
  /**
21
21
  * @public
22
22
  * <note>
23
- * <p>This API call has been replaced with a new "traffic sources" API call
24
- * (<code>DetachTrafficSources</code>) that can detach multiple traffic sources
25
- * types. While we continue to support <code>DetachLoadBalancers</code>, and you can
26
- * use both the original <code>DetachLoadBalancers</code> API call and the new
27
- * <code>DetachTrafficSources</code> API call on the same Auto Scaling group, we recommend
28
- * using the new "traffic sources" API call to simplify how you manage traffic
29
- * sources.</p>
23
+ * <p>This API operation is superseded by <a>DetachTrafficSources</a>, which
24
+ * can detach multiple traffic sources types. We recommend using
25
+ * <code>DetachTrafficSources</code> to simplify how you manage traffic sources.
26
+ * However, we continue to support <code>DetachLoadBalancers</code>. You can use both
27
+ * the original <code>DetachLoadBalancers</code> API operation and
28
+ * <code>DetachTrafficSources</code> on the same Auto Scaling group.</p>
30
29
  * </note>
31
30
  * <p>Detaches one or more Classic Load Balancers from the specified Auto Scaling group.</p>
32
31
  * <p>This operation detaches only Classic Load Balancers. If you have Application Load Balancers, Network Load Balancers, or
package/dist-types/models/models_0.d.ts CHANGED
@@ -1509,11 +1509,13 @@ export interface CreateAutoScalingGroupType {
1509
1509
  */
1510
1510
  TargetGroupARNs?: string[];
1511
1511
  /**
1512
- * <p>A comma-separated list of one or more health check types.</p>
1512
+ * <p>A comma-separated value string of one or more health check types.</p>
1513
1513
  * <p>The valid values are <code>EC2</code>, <code>ELB</code>, and <code>VPC_LATTICE</code>.
1514
1514
  * <code>EC2</code> is the default health check and cannot be disabled. For more
1515
1515
  * information, see <a href="https://docs.aws.amazon.com/autoscaling/ec2/userguide/healthcheck.html">Health checks for Auto Scaling
1516
1516
  * instances</a> in the <i>Amazon EC2 Auto Scaling User Guide</i>.</p>
1517
+ * <p>Only specify <code>EC2</code> if you must clear a value that was previously
1518
+ * set.</p>
1517
1519
  */
1518
1520
  HealthCheckType?: string;
1519
1521
  /**
@@ -2672,7 +2674,7 @@ export interface AutoScalingGroup {
2672
2674
  */
2673
2675
  TargetGroupARNs?: string[];
2674
2676
  /**
2675
- * <p>A comma-separated list of one or more health check types.</p>
2677
+ * <p>A comma-separated value string of one or more health check types.</p>
2676
2678
  */
2677
2679
  HealthCheckType: string | undefined;
2678
2680
  /**
@@ -5400,8 +5402,8 @@ export interface DetachTrafficSourcesType {
5400
5402
  */
5401
5403
  AutoScalingGroupName: string | undefined;
5402
5404
  /**
5403
- * <p>The unique identifiers of one or more traffic sources you are detaching. You can
5404
- * specify up to 10 traffic sources.</p>
5405
+ * <p>The unique identifiers of one or more traffic sources. You can specify up to 10
5406
+ * traffic sources.</p>
5405
5407
  */
5406
5408
  TrafficSources: TrafficSourceIdentifier[] | undefined;
5407
5409
  }
@@ -6556,11 +6558,13 @@ export interface UpdateAutoScalingGroupType {
6556
6558
  */
6557
6559
  AvailabilityZones?: string[];
6558
6560
  /**
6559
- * <p>A comma-separated list of one or more health check types.</p>
6561
+ * <p>A comma-separated value string of one or more health check types.</p>
6560
6562
  * <p>The valid values are <code>EC2</code>, <code>ELB</code>, and <code>VPC_LATTICE</code>.
6561
6563
  * <code>EC2</code> is the default health check and cannot be disabled. For more
6562
6564
  * information, see <a href="https://docs.aws.amazon.com/autoscaling/ec2/userguide/healthcheck.html">Health checks for Auto Scaling
6563
6565
  * instances</a> in the <i>Amazon EC2 Auto Scaling User Guide</i>.</p>
6566
+ * <p>Only specify <code>EC2</code> if you must clear a value that was previously
6567
+ * set.</p>
6564
6568
  */
6565
6569
  HealthCheckType?: string;
6566
6570
  /**
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "@aws-sdk/client-auto-scaling",
3
3
  "description": "AWS SDK for JavaScript Auto Scaling Client for Node.js, Browser and React Native",
4
- "version": "3.304.0",
4
+ "version": "3.306.0",
5
5
  "scripts": {
6
6
  "build": "concurrently 'yarn:build:cjs' 'yarn:build:es' 'yarn:build:types'",
7
7
  "build:cjs": "tsc -p tsconfig.cjs.json",
@@ -21,39 +21,39 @@
21
21
  "dependencies": {
22
22
  "@aws-crypto/sha256-browser": "3.0.0",
23
23
  "@aws-crypto/sha256-js": "3.0.0",
24
- "@aws-sdk/client-sts": "3.303.0",
25
- "@aws-sdk/config-resolver": "3.303.0",
26
- "@aws-sdk/credential-provider-node": "3.303.0",
27
- "@aws-sdk/fetch-http-handler": "3.303.0",
28
- "@aws-sdk/hash-node": "3.303.0",
29
- "@aws-sdk/invalid-dependency": "3.303.0",
30
- "@aws-sdk/middleware-content-length": "3.303.0",
31
- "@aws-sdk/middleware-endpoint": "3.303.0",
32
- "@aws-sdk/middleware-host-header": "3.303.0",
33
- "@aws-sdk/middleware-logger": "3.303.0",
34
- "@aws-sdk/middleware-recursion-detection": "3.303.0",
35
- "@aws-sdk/middleware-retry": "3.303.0",
36
- "@aws-sdk/middleware-serde": "3.303.0",
37
- "@aws-sdk/middleware-signing": "3.303.0",
38
- "@aws-sdk/middleware-stack": "3.303.0",
39
- "@aws-sdk/middleware-user-agent": "3.303.0",
40
- "@aws-sdk/node-config-provider": "3.303.0",
41
- "@aws-sdk/node-http-handler": "3.303.0",
42
- "@aws-sdk/protocol-http": "3.303.0",
43
- "@aws-sdk/smithy-client": "3.303.0",
44
- "@aws-sdk/types": "3.303.0",
45
- "@aws-sdk/url-parser": "3.303.0",
24
+ "@aws-sdk/client-sts": "3.306.0",
25
+ "@aws-sdk/config-resolver": "3.306.0",
26
+ "@aws-sdk/credential-provider-node": "3.306.0",
27
+ "@aws-sdk/fetch-http-handler": "3.306.0",
28
+ "@aws-sdk/hash-node": "3.306.0",
29
+ "@aws-sdk/invalid-dependency": "3.306.0",
30
+ "@aws-sdk/middleware-content-length": "3.306.0",
31
+ "@aws-sdk/middleware-endpoint": "3.306.0",
32
+ "@aws-sdk/middleware-host-header": "3.306.0",
33
+ "@aws-sdk/middleware-logger": "3.306.0",
34
+ "@aws-sdk/middleware-recursion-detection": "3.306.0",
35
+ "@aws-sdk/middleware-retry": "3.306.0",
36
+ "@aws-sdk/middleware-serde": "3.306.0",
37
+ "@aws-sdk/middleware-signing": "3.306.0",
38
+ "@aws-sdk/middleware-stack": "3.306.0",
39
+ "@aws-sdk/middleware-user-agent": "3.306.0",
40
+ "@aws-sdk/node-config-provider": "3.306.0",
41
+ "@aws-sdk/node-http-handler": "3.306.0",
42
+ "@aws-sdk/protocol-http": "3.306.0",
43
+ "@aws-sdk/smithy-client": "3.306.0",
44
+ "@aws-sdk/types": "3.306.0",
45
+ "@aws-sdk/url-parser": "3.306.0",
46
46
  "@aws-sdk/util-base64": "3.303.0",
47
47
  "@aws-sdk/util-body-length-browser": "3.303.0",
48
48
  "@aws-sdk/util-body-length-node": "3.303.0",
49
- "@aws-sdk/util-defaults-mode-browser": "3.303.0",
50
- "@aws-sdk/util-defaults-mode-node": "3.303.0",
51
- "@aws-sdk/util-endpoints": "3.303.0",
52
- "@aws-sdk/util-retry": "3.303.0",
53
- "@aws-sdk/util-user-agent-browser": "3.303.0",
54
- "@aws-sdk/util-user-agent-node": "3.303.0",
49
+ "@aws-sdk/util-defaults-mode-browser": "3.306.0",
50
+ "@aws-sdk/util-defaults-mode-node": "3.306.0",
51
+ "@aws-sdk/util-endpoints": "3.306.0",
52
+ "@aws-sdk/util-retry": "3.306.0",
53
+ "@aws-sdk/util-user-agent-browser": "3.306.0",
54
+ "@aws-sdk/util-user-agent-node": "3.306.0",
55
55
  "@aws-sdk/util-utf8": "3.303.0",
56
- "@aws-sdk/util-waiter": "3.303.0",
56
+ "@aws-sdk/util-waiter": "3.306.0",
57
57
  "fast-xml-parser": "4.1.2",
58
58
  "tslib": "^2.5.0"
59
59
  },