AWS autoscaling documentation change
Summary
Consistently replaced 'Auto Scaling group' with 'Amazon EC2 Auto Scaling group' in target group attachment documentation
Security assessment
Terminology updates without functional changes. The health check behavior description remains unchanged and contains no new security context.
Diff
diff --git a/autoscaling/ec2/userguide/verify-target-group-attachment-status.md b/autoscaling/ec2/userguide/verify-target-group-attachment-status.md index 54658ffbc..e3b6f262e 100644 --- a//autoscaling/ec2/userguide/verify-target-group-attachment-status.md +++ b//autoscaling/ec2/userguide/verify-target-group-attachment-status.md @@ -7 +7 @@ -After you attach a VPC Lattice target group to an Auto Scaling group, it enters the `Adding` state while registering the instances in the group. When all instances in the group are registered, it enters the `Added` state. After at least one registered instance passes the health checks, it enters the `InService` state. When the target group is in the `InService` state, Amazon EC2 Auto Scaling can terminate and replace any instances that are reported as unhealthy. If no registered instances pass the health checks (for example, due to a misconfigured health check), the target group doesn't enter the `InService` state. Amazon EC2 Auto Scaling doesn't terminate and replace the instances. +After you attach a VPC Lattice target group to an Amazon EC2 Auto Scaling group, it enters the `Adding` state while registering the instances in the group. When all instances in the group are registered, it enters the `Added` state. After at least one registered instance passes the health checks, it enters the `InService` state. When the target group is in the `InService` state, Amazon EC2 Auto Scaling can terminate and replace any instances that are reported as unhealthy. If no registered instances pass the health checks (for example, due to a misconfigured health check), the target group doesn't enter the `InService` state. Amazon EC2 Auto Scaling doesn't terminate and replace the instances. @@ -15 +15 @@ You can verify the attachment status by using the AWS Command Line Interface (AW -The following [describe-traffic-sources](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/autoscaling/describe-traffic-sources.html) command returns the attachment status of all traffic sources for the specified Auto Scaling group. +The following [describe-traffic-sources](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/autoscaling/describe-traffic-sources.html) command returns the attachment status of all traffic sources for the specified Amazon EC2 Auto Scaling group. @@ -20 +20 @@ The following [describe-traffic-sources](https://awscli.amazonaws.com/v2/documen -The example returns the ARN of the VPC Lattice target group that's attached to the Auto Scaling group, along with the attachment status of the target group in the `State` element. +The example returns the ARN of the VPC Lattice target group that's attached to the Amazon EC2 Auto Scaling group, along with the attachment status of the target group in the `State` element.