npm - @aws-sdk/client-auto-scaling - Versions diffs - 3.301.0 → 3.303.0 - Mend

@aws-sdk/client-auto-scaling 3.301.0 → 3.303.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 (27) hide show

package/dist-types/AutoScaling.d.ts CHANGED Viewed

@@ -92,7 +92,13 @@ export declare class AutoScaling extends AutoScalingClient {
     /**
      * @public
      * <note>
-     *             <p>To attach an Application Load Balancer, Network Load Balancer, or Gateway Load Balancer, use the <a>AttachLoadBalancerTargetGroups</a> API operation instead.</p>
+     *             <p>This API call has been replaced with a new "traffic sources" API call
+     *                     (<code>AttachTrafficSources</code>) that can attach multiple traffic sources
+     *                 types. While we continue to support <code>AttachLoadBalancers</code>, and you can
+     *                 use both the original <code>AttachLoadBalancers</code> API call and the new
+     *                     <code>AttachTrafficSources</code> API call on the same Auto Scaling group, we recommend
+     *                 using the new "traffic sources" API call to simplify how you manage traffic
+     *                 sources.</p>
      *          </note>
      *          <p>Attaches one or more Classic Load Balancers to the specified Auto Scaling group. Amazon EC2 Auto Scaling registers the
      *             running instances with these Classic Load Balancers.</p>
@@ -109,7 +115,16 @@ export declare class AutoScaling extends AutoScalingClient {
     attachLoadBalancers(args: AttachLoadBalancersCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: AttachLoadBalancersCommandOutput) => void): void;
     /**
      * @public
-     * <p>Attaches one or more target groups to the specified Auto Scaling group.</p>
+     * <note>
+     *             <p>This API call has been replaced with a new "traffic sources" API call
+     *                     (<code>AttachTrafficSources</code>) that can attach multiple traffic sources
+     *                 types. While we continue to support <code>AttachLoadBalancerTargetGroups</code>, and
+     *                 you can use both the original <code>AttachLoadBalancerTargetGroups</code> API call
+     *                 and the new <code>AttachTrafficSources</code> API call on the same Auto Scaling group, we
+     *                 recommend using the new "traffic sources" API call to simplify how you manage
+     *                 traffic sources.</p>
+     *          </note>
+     *          <p>Attaches one or more target groups to the specified Auto Scaling group.</p>
      *          <p>This operation is used with the following load balancer types: </p>
      *          <ul>
      *             <li>
@@ -137,15 +152,30 @@ export declare class AutoScaling extends AutoScalingClient {
     attachLoadBalancerTargetGroups(args: AttachLoadBalancerTargetGroupsCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: AttachLoadBalancerTargetGroupsCommandOutput) => void): void;
     /**
      * @public
-     * <p>
-     *             <b>Reserved for use with Amazon VPC Lattice, which is in preview and subject to change.
-     *             Do not use this API for production workloads. This API is also subject to change.</b>
-     *          </p>
-     *          <p>Attaches one or more traffic sources to the specified Auto Scaling group.</p>
-     *          <p>To describe the traffic sources for an Auto Scaling group, call the <a>DescribeTrafficSources</a> API. To detach a traffic source from the Auto Scaling
-     *             group, call the <a>DetachTrafficSources</a> API.</p>
+     * <p>Attaches one or more traffic sources to the specified Auto Scaling group.</p>
+     *          <p>You can use any of the following as traffic sources for an Auto Scaling group:</p>
+     *          <ul>
+     *             <li>
+     *                <p>Application Load Balancer</p>
+     *             </li>
+     *             <li>
+     *                <p>Classic Load Balancer</p>
+     *             </li>
+     *             <li>
+     *                <p>Network Load Balancer</p>
+     *             </li>
+     *             <li>
+     *                <p>Gateway Load Balancer</p>
+     *             </li>
+     *             <li>
+     *                <p>VPC Lattice</p>
+     *             </li>
+     *          </ul>
      *          <p>This operation is additive and does not detach existing traffic sources from the Auto Scaling
-     *             group.</p>
+     *             group. </p>
+     *          <p>After the operation completes, use the <a>DescribeTrafficSources</a> API to
+     *             return details about the state of the attachments between traffic sources and your Auto Scaling
+     *             group. To detach a traffic source from the Auto Scaling group, call the <a>DetachTrafficSources</a> API.</p>
      */
     attachTrafficSources(args: AttachTrafficSourcesCommandInput, options?: __HttpHandlerOptions): Promise<AttachTrafficSourcesCommandOutput>;
     attachTrafficSources(args: AttachTrafficSourcesCommandInput, cb: (err: any, data?: AttachTrafficSourcesCommandOutput) => void): void;
@@ -474,8 +504,17 @@ export declare class AutoScaling extends AutoScalingClient {
     describeLifecycleHookTypes(args: DescribeLifecycleHookTypesCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: DescribeLifecycleHookTypesCommandOutput) => void): void;
     /**
      * @public
-     * <p>Gets information about the load balancers for the specified Auto Scaling group.</p>
-     *          <p>This operation describes only Classic Load Balancers. If you have Application Load Balancers, Network Load Balancers, or Gateway Load Balancer, use the
+     * <note>
+     *             <p>This API call has been replaced with a new "traffic sources" API call
+     *                     (<code>DescribeTrafficSources</code>) that can describe multiple traffic sources
+     *                 types. While we continue to support <code>DescribeLoadBalancers</code>, and you can
+     *                 use both the original <code>DescribeLoadBalancers</code> API call and the new
+     *                     <code>DescribeTrafficSources</code> API call on the same Auto Scaling group, we
+     *                 recommend using the new "traffic sources" API call to simplify how you manage
+     *                 traffic sources.</p>
+     *          </note>
+     *          <p>Gets information about the load balancers for the specified Auto Scaling group.</p>
+     *          <p>This operation describes only Classic Load Balancers. If you have Application Load Balancers, Network Load Balancers, or Gateway Load Balancers, use the
      *                 <a>DescribeLoadBalancerTargetGroups</a> API instead.</p>
      *          <p>To determine the attachment status of the load balancer, use the <code>State</code>
      *             element in the response. When you attach a load balancer to an Auto Scaling group, the initial
@@ -503,7 +542,16 @@ export declare class AutoScaling extends AutoScalingClient {
     describeLoadBalancers(args: DescribeLoadBalancersCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: DescribeLoadBalancersCommandOutput) => void): void;
     /**
      * @public
-     * <p>Gets information about the Elastic Load Balancing target groups for the specified Auto Scaling group.</p>
+     * <note>
+     *             <p>This API call has been replaced with a new "traffic sources" API call
+     *                     (<code>DescribeTrafficSources</code>) that can describe multiple traffic sources
+     *                 types. While we continue to support <code>DescribeLoadBalancerTargetGroups</code>,
+     *                 and you can use both the original <code>DescribeLoadBalancerTargetGroups</code> API
+     *                 call and the new <code>DescribeTrafficSources</code> API call on the same Auto Scaling
+     *                 group, we recommend using the new "traffic sources" API call to simplify how you
+     *                 manage traffic sources.</p>
+     *          </note>
+     *          <p>Gets information about the Elastic Load Balancing target groups for the specified Auto Scaling group.</p>
      *          <p>To determine the attachment status of the target group, use the <code>State</code>
      *             element in the response. When you attach a target group to an Auto Scaling group, the initial
      *                 <code>State</code> value is <code>Adding</code>. The state transitions to
@@ -614,11 +662,11 @@ export declare class AutoScaling extends AutoScalingClient {
     describeTerminationPolicyTypes(args: DescribeTerminationPolicyTypesCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: DescribeTerminationPolicyTypesCommandOutput) => void): void;
     /**
      * @public
-     * <p>
-     *             <b>Reserved for use with Amazon VPC Lattice, which is in preview and subject to change.
-     *             Do not use this API for production workloads. This API is also subject to change.</b>
-     *          </p>
-     *          <p>Gets information about the traffic sources for the specified Auto Scaling group.</p>
+     * <p>Gets information about the traffic sources for the specified Auto Scaling group.</p>
+     *          <p>You can optionally provide a traffic source type. If you provide a traffic source
+     *             type, then the results only include that traffic source type.</p>
+     *          <p>If you do not provide a traffic source type, then the results include all the traffic
+     *             sources for the specified Auto Scaling group. </p>
      */
     describeTrafficSources(args: DescribeTrafficSourcesCommandInput, options?: __HttpHandlerOptions): Promise<DescribeTrafficSourcesCommandOutput>;
     describeTrafficSources(args: DescribeTrafficSourcesCommandInput, cb: (err: any, data?: DescribeTrafficSourcesCommandOutput) => void): void;
@@ -650,9 +698,18 @@ export declare class AutoScaling extends AutoScalingClient {
     detachInstances(args: DetachInstancesCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: DetachInstancesCommandOutput) => void): void;
     /**
      * @public
-     * <p>Detaches one or more Classic Load Balancers from the specified Auto Scaling group.</p>
+     * <note>
+     *             <p>This API call has been replaced with a new "traffic sources" API call
+     *                 (<code>DetachTrafficSources</code>) that can detach multiple traffic sources
+     *                 types. While we continue to support <code>DetachLoadBalancers</code>, and you can
+     *                 use both the original <code>DetachLoadBalancers</code> API call and the new
+     *                     <code>DetachTrafficSources</code> API call on the same Auto Scaling group, we recommend
+     *                 using the new "traffic sources" API call to simplify how you manage traffic
+     *                 sources.</p>
+     *          </note>
+     *          <p>Detaches one or more Classic Load Balancers from the specified Auto Scaling group.</p>
      *          <p>This operation detaches only Classic Load Balancers. If you have Application Load Balancers, Network Load Balancers, or
-     *             Gateway Load Balancer, use the <a>DetachLoadBalancerTargetGroups</a> API instead.</p>
+     *             Gateway Load Balancers, use the <a>DetachLoadBalancerTargetGroups</a> API instead.</p>
      *          <p>When you detach a load balancer, it enters the <code>Removing</code> state while
      *             deregistering the instances in the group. When all instances are deregistered, then you
      *             can no longer describe the load balancer using the <a>DescribeLoadBalancers</a> API call. The instances remain running.</p>
@@ -662,7 +719,16 @@ export declare class AutoScaling extends AutoScalingClient {
     detachLoadBalancers(args: DetachLoadBalancersCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: DetachLoadBalancersCommandOutput) => void): void;
     /**
      * @public
-     * <p>Detaches one or more target groups from the specified Auto Scaling group.</p>
+     * <note>
+     *             <p>This API call has been replaced with a new "traffic sources" API call
+     *                     (<code>DetachTrafficSources</code>) that can detach multiple traffic sources
+     *                 types. While we continue to support <code>DetachLoadBalancerTargetGroups</code>, and
+     *                 you can use both the original <code>DetachLoadBalancerTargetGroups</code> API call
+     *                 and the new <code>DetachTrafficSources</code> API call on the same Auto Scaling group, we
+     *                 recommend using the new "traffic sources" API call to simplify how you manage
+     *                 traffic sources.</p>
+     *          </note>
+     *          <p>Detaches one or more target groups from the specified Auto Scaling group.</p>
      *          <p>When you detach a target group, it enters the <code>Removing</code> state while
      *             deregistering the instances in the group. When all instances are deregistered, then you
      *             can no longer describe the target group using the <a>DescribeLoadBalancerTargetGroups</a> API call. The instances remain
@@ -678,11 +744,10 @@ export declare class AutoScaling extends AutoScalingClient {
     detachLoadBalancerTargetGroups(args: DetachLoadBalancerTargetGroupsCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: DetachLoadBalancerTargetGroupsCommandOutput) => void): void;
     /**
      * @public
-     * <p>
-     *             <b>Reserved for use with Amazon VPC Lattice, which is in preview and subject to change.
-     *             Do not use this API for production workloads. This API is also subject to change.</b>
-     *          </p>
-     *          <p>Detaches one or more traffic sources from the specified Auto Scaling group.</p>
+     * <p>Detaches one or more traffic sources from the specified Auto Scaling group.</p>
+     *          <p>When you detach a taffic, it enters the <code>Removing</code> state while
+     *             deregistering the instances in the group. When all instances are deregistered, then you
+     *             can no longer describe the traffic source using the <a>DescribeTrafficSources</a> API call. The instances continue to run.</p>
      */
     detachTrafficSources(args: DetachTrafficSourcesCommandInput, options?: __HttpHandlerOptions): Promise<DetachTrafficSourcesCommandOutput>;
     detachTrafficSources(args: DetachTrafficSourcesCommandInput, cb: (err: any, data?: DetachTrafficSourcesCommandOutput) => void): void;
@@ -934,8 +999,8 @@ export declare class AutoScaling extends AutoScalingClient {
      *                <p>There is no desired configuration specified for the instance refresh.</p>
      *             </li>
      *             <li>
-     *                <p>The Auto Scaling group has a launch template that uses an Amazon Web Services Systems Manager
-     *                     parameter instead of an AMI ID for the <code>ImageId</code> property.</p>
+     *                <p>The Auto Scaling group has a launch template that uses an Amazon Web Services Systems Manager parameter instead
+     *                     of an AMI ID for the <code>ImageId</code> property.</p>
      *             </li>
      *             <li>
      *                <p>The Auto Scaling group uses the launch template's <code>$Latest</code> or

package/dist-types/commands/AttachLoadBalancerTargetGroupsCommand.d.ts CHANGED Viewed

@@ -19,7 +19,16 @@ export interface AttachLoadBalancerTargetGroupsCommandOutput extends AttachLoadB
 }
 /**
  * @public
- * <p>Attaches one or more target groups to the specified Auto Scaling group.</p>
+ * <note>
+ *             <p>This API call has been replaced with a new "traffic sources" API call
+ *                     (<code>AttachTrafficSources</code>) that can attach multiple traffic sources
+ *                 types. While we continue to support <code>AttachLoadBalancerTargetGroups</code>, and
+ *                 you can use both the original <code>AttachLoadBalancerTargetGroups</code> API call
+ *                 and the new <code>AttachTrafficSources</code> API call on the same Auto Scaling group, we
+ *                 recommend using the new "traffic sources" API call to simplify how you manage
+ *                 traffic sources.</p>
+ *          </note>
+ *          <p>Attaches one or more target groups to the specified Auto Scaling group.</p>
  *          <p>This operation is used with the following load balancer types: </p>
  *          <ul>
  *             <li>

package/dist-types/commands/AttachLoadBalancersCommand.d.ts CHANGED Viewed

@@ -20,7 +20,13 @@ export interface AttachLoadBalancersCommandOutput extends AttachLoadBalancersRes
 /**
  * @public
  * <note>
- *             <p>To attach an Application Load Balancer, Network Load Balancer, or Gateway Load Balancer, use the <a>AttachLoadBalancerTargetGroups</a> API operation instead.</p>
+ *             <p>This API call has been replaced with a new "traffic sources" API call
+ *                     (<code>AttachTrafficSources</code>) that can attach multiple traffic sources
+ *                 types. While we continue to support <code>AttachLoadBalancers</code>, and you can
+ *                 use both the original <code>AttachLoadBalancers</code> API call and the new
+ *                     <code>AttachTrafficSources</code> API call on the same Auto Scaling group, we recommend
+ *                 using the new "traffic sources" API call to simplify how you manage traffic
+ *                 sources.</p>
  *          </note>
  *          <p>Attaches one or more Classic Load Balancers to the specified Auto Scaling group. Amazon EC2 Auto Scaling registers the
  *             running instances with these Classic Load Balancers.</p>

package/dist-types/commands/AttachTrafficSourcesCommand.d.ts CHANGED Viewed

@@ -19,15 +19,30 @@ export interface AttachTrafficSourcesCommandOutput extends AttachTrafficSourcesR
 }
 /**
  * @public
- * <p>
- *             <b>Reserved for use with Amazon VPC Lattice, which is in preview and subject to change.
- *             Do not use this API for production workloads. This API is also subject to change.</b>
- *          </p>
- *          <p>Attaches one or more traffic sources to the specified Auto Scaling group.</p>
- *          <p>To describe the traffic sources for an Auto Scaling group, call the <a>DescribeTrafficSources</a> API. To detach a traffic source from the Auto Scaling
- *             group, call the <a>DetachTrafficSources</a> API.</p>
+ * <p>Attaches one or more traffic sources to the specified Auto Scaling group.</p>
+ *          <p>You can use any of the following as traffic sources for an Auto Scaling group:</p>
+ *          <ul>
+ *             <li>
+ *                <p>Application Load Balancer</p>
+ *             </li>
+ *             <li>
+ *                <p>Classic Load Balancer</p>
+ *             </li>
+ *             <li>
+ *                <p>Network Load Balancer</p>
+ *             </li>
+ *             <li>
+ *                <p>Gateway Load Balancer</p>
+ *             </li>
+ *             <li>
+ *                <p>VPC Lattice</p>
+ *             </li>
+ *          </ul>
  *          <p>This operation is additive and does not detach existing traffic sources from the Auto Scaling
- *             group.</p>
+ *             group. </p>
+ *          <p>After the operation completes, use the <a>DescribeTrafficSources</a> API to
+ *             return details about the state of the attachments between traffic sources and your Auto Scaling
+ *             group. To detach a traffic source from the Auto Scaling group, call the <a>DetachTrafficSources</a> API.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript
@@ -38,7 +53,8 @@ export interface AttachTrafficSourcesCommandOutput extends AttachTrafficSourcesR
  *   AutoScalingGroupName: "STRING_VALUE", // required
  *   TrafficSources: [ // TrafficSources // required
  *     { // TrafficSourceIdentifier
- *       Identifier: "STRING_VALUE",
+ *       Identifier: "STRING_VALUE", // required
+ *       Type: "STRING_VALUE",
  *     },
  *   ],
  * };

package/dist-types/commands/CreateAutoScalingGroupCommand.d.ts CHANGED Viewed

@@ -193,7 +193,8 @@ export interface CreateAutoScalingGroupCommandOutput extends __MetadataBearer {
  *   DefaultInstanceWarmup: Number("int"),
  *   TrafficSources: [ // TrafficSources
  *     { // TrafficSourceIdentifier
- *       Identifier: "STRING_VALUE",
+ *       Identifier: "STRING_VALUE", // required
+ *       Type: "STRING_VALUE",
  *     },
  *   ],
  * };

package/dist-types/commands/DescribeLoadBalancerTargetGroupsCommand.d.ts CHANGED Viewed

@@ -19,7 +19,16 @@ export interface DescribeLoadBalancerTargetGroupsCommandOutput extends DescribeL
 }
 /**
  * @public
- * <p>Gets information about the Elastic Load Balancing target groups for the specified Auto Scaling group.</p>
+ * <note>
+ *             <p>This API call has been replaced with a new "traffic sources" API call
+ *                     (<code>DescribeTrafficSources</code>) that can describe multiple traffic sources
+ *                 types. While we continue to support <code>DescribeLoadBalancerTargetGroups</code>,
+ *                 and you can use both the original <code>DescribeLoadBalancerTargetGroups</code> API
+ *                 call and the new <code>DescribeTrafficSources</code> API call on the same Auto Scaling
+ *                 group, we recommend using the new "traffic sources" API call to simplify how you
+ *                 manage traffic sources.</p>
+ *          </note>
+ *          <p>Gets information about the Elastic Load Balancing target groups for the specified Auto Scaling group.</p>
  *          <p>To determine the attachment status of the target group, use the <code>State</code>
  *             element in the response. When you attach a target group to an Auto Scaling group, the initial
  *                 <code>State</code> value is <code>Adding</code>. The state transitions to

package/dist-types/commands/DescribeLoadBalancersCommand.d.ts CHANGED Viewed

@@ -19,8 +19,17 @@ export interface DescribeLoadBalancersCommandOutput extends DescribeLoadBalancer
 }
 /**
  * @public
- * <p>Gets information about the load balancers for the specified Auto Scaling group.</p>
- *          <p>This operation describes only Classic Load Balancers. If you have Application Load Balancers, Network Load Balancers, or Gateway Load Balancer, use the
+ * <note>
+ *             <p>This API call has been replaced with a new "traffic sources" API call
+ *                     (<code>DescribeTrafficSources</code>) that can describe multiple traffic sources
+ *                 types. While we continue to support <code>DescribeLoadBalancers</code>, and you can
+ *                 use both the original <code>DescribeLoadBalancers</code> API call and the new
+ *                     <code>DescribeTrafficSources</code> API call on the same Auto Scaling group, we
+ *                 recommend using the new "traffic sources" API call to simplify how you manage
+ *                 traffic sources.</p>
+ *          </note>
+ *          <p>Gets information about the load balancers for the specified Auto Scaling group.</p>
+ *          <p>This operation describes only Classic Load Balancers. If you have Application Load Balancers, Network Load Balancers, or Gateway Load Balancers, use the
  *                 <a>DescribeLoadBalancerTargetGroups</a> API instead.</p>
  *          <p>To determine the attachment status of the load balancer, use the <code>State</code>
  *             element in the response. When you attach a load balancer to an Auto Scaling group, the initial

package/dist-types/commands/DescribeTrafficSourcesCommand.d.ts CHANGED Viewed

@@ -19,11 +19,11 @@ export interface DescribeTrafficSourcesCommandOutput extends DescribeTrafficSour
 }
 /**
  * @public
- * <p>
- *             <b>Reserved for use with Amazon VPC Lattice, which is in preview and subject to change.
- *             Do not use this API for production workloads. This API is also subject to change.</b>
- *          </p>
- *          <p>Gets information about the traffic sources for the specified Auto Scaling group.</p>
+ * <p>Gets information about the traffic sources for the specified Auto Scaling group.</p>
+ *          <p>You can optionally provide a traffic source type. If you provide a traffic source
+ *             type, then the results only include that traffic source type.</p>
+ *          <p>If you do not provide a traffic source type, then the results include all the traffic
+ *             sources for the specified Auto Scaling group. </p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript
@@ -32,7 +32,7 @@ export interface DescribeTrafficSourcesCommandOutput extends DescribeTrafficSour
  * const client = new AutoScalingClient(config);
  * const input = { // DescribeTrafficSourcesRequest
  *   AutoScalingGroupName: "STRING_VALUE", // required
- *   TrafficSourceType: "STRING_VALUE", // required
+ *   TrafficSourceType: "STRING_VALUE",
  *   NextToken: "STRING_VALUE",
  *   MaxRecords: Number("int"),
  * };

package/dist-types/commands/DetachLoadBalancerTargetGroupsCommand.d.ts CHANGED Viewed

@@ -19,7 +19,16 @@ export interface DetachLoadBalancerTargetGroupsCommandOutput extends DetachLoadB
 }
 /**
  * @public
- * <p>Detaches one or more target groups from the specified Auto Scaling group.</p>
+ * <note>
+ *             <p>This API call has been replaced with a new "traffic sources" API call
+ *                     (<code>DetachTrafficSources</code>) that can detach multiple traffic sources
+ *                 types. While we continue to support <code>DetachLoadBalancerTargetGroups</code>, and
+ *                 you can use both the original <code>DetachLoadBalancerTargetGroups</code> API call
+ *                 and the new <code>DetachTrafficSources</code> API call on the same Auto Scaling group, we
+ *                 recommend using the new "traffic sources" API call to simplify how you manage
+ *                 traffic sources.</p>
+ *          </note>
+ *          <p>Detaches one or more target groups from the specified Auto Scaling group.</p>
  *          <p>When you detach a target group, it enters the <code>Removing</code> state while
  *             deregistering the instances in the group. When all instances are deregistered, then you
  *             can no longer describe the target group using the <a>DescribeLoadBalancerTargetGroups</a> API call. The instances remain

package/dist-types/commands/DetachLoadBalancersCommand.d.ts CHANGED Viewed

@@ -19,9 +19,18 @@ export interface DetachLoadBalancersCommandOutput extends DetachLoadBalancersRes
 }
 /**
  * @public
- * <p>Detaches one or more Classic Load Balancers from the specified Auto Scaling group.</p>
+ * <note>
+ *             <p>This API call has been replaced with a new "traffic sources" API call
+ *                 (<code>DetachTrafficSources</code>) that can detach multiple traffic sources
+ *                 types. While we continue to support <code>DetachLoadBalancers</code>, and you can
+ *                 use both the original <code>DetachLoadBalancers</code> API call and the new
+ *                     <code>DetachTrafficSources</code> API call on the same Auto Scaling group, we recommend
+ *                 using the new "traffic sources" API call to simplify how you manage traffic
+ *                 sources.</p>
+ *          </note>
+ *          <p>Detaches one or more Classic Load Balancers from the specified Auto Scaling group.</p>
  *          <p>This operation detaches only Classic Load Balancers. If you have Application Load Balancers, Network Load Balancers, or
- *             Gateway Load Balancer, use the <a>DetachLoadBalancerTargetGroups</a> API instead.</p>
+ *             Gateway Load Balancers, use the <a>DetachLoadBalancerTargetGroups</a> API instead.</p>
  *          <p>When you detach a load balancer, it enters the <code>Removing</code> state while
  *             deregistering the instances in the group. When all instances are deregistered, then you
  *             can no longer describe the load balancer using the <a>DescribeLoadBalancers</a> API call. The instances remain running.</p>

package/dist-types/commands/DetachTrafficSourcesCommand.d.ts CHANGED Viewed

@@ -19,11 +19,10 @@ export interface DetachTrafficSourcesCommandOutput extends DetachTrafficSourcesR
 }
 /**
  * @public
- * <p>
- *             <b>Reserved for use with Amazon VPC Lattice, which is in preview and subject to change.
- *             Do not use this API for production workloads. This API is also subject to change.</b>
- *          </p>
- *          <p>Detaches one or more traffic sources from the specified Auto Scaling group.</p>
+ * <p>Detaches one or more traffic sources from the specified Auto Scaling group.</p>
+ *          <p>When you detach a taffic, it enters the <code>Removing</code> state while
+ *             deregistering the instances in the group. When all instances are deregistered, then you
+ *             can no longer describe the traffic source using the <a>DescribeTrafficSources</a> API call. The instances continue to run.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript
@@ -34,7 +33,8 @@ export interface DetachTrafficSourcesCommandOutput extends DetachTrafficSourcesR
  *   AutoScalingGroupName: "STRING_VALUE", // required
  *   TrafficSources: [ // TrafficSources // required
  *     { // TrafficSourceIdentifier
- *       Identifier: "STRING_VALUE",
+ *       Identifier: "STRING_VALUE", // required
+ *       Type: "STRING_VALUE",
  *     },
  *   ],
  * };

package/dist-types/commands/RollbackInstanceRefreshCommand.d.ts CHANGED Viewed

@@ -32,8 +32,8 @@ export interface RollbackInstanceRefreshCommandOutput extends RollbackInstanceRe
  *                <p>There is no desired configuration specified for the instance refresh.</p>
  *             </li>
  *             <li>
- *                <p>The Auto Scaling group has a launch template that uses an Amazon Web Services Systems Manager
- *                     parameter instead of an AMI ID for the <code>ImageId</code> property.</p>
+ *                <p>The Auto Scaling group has a launch template that uses an Amazon Web Services Systems Manager parameter instead
+ *                     of an AMI ID for the <code>ImageId</code> property.</p>
  *             </li>
  *             <li>
  *                <p>The Auto Scaling group uses the launch template's <code>$Latest</code> or