AWS autoscaling documentation change
Summary
Updated terminology from 'Auto Scaling group' to 'Amazon EC2 Auto Scaling group' and 'Elastic Load Balancing' to 'ELB' for consistency. No functional changes to process suspension behavior.
Security assessment
Changes are purely terminological updates (branding/abbreviation standardization). No references to vulnerabilities, mitigations, or security controls added/modified. The operational behavior of suspended processes remains described identically in substance.
Diff
diff --git a/autoscaling/ec2/userguide/understand-how-suspending-processes-affects-other-processes.md b/autoscaling/ec2/userguide/understand-how-suspending-processes-affects-other-processes.md index 374a53277..7e3d0e5cc 100644 --- a//autoscaling/ec2/userguide/understand-how-suspending-processes-affects-other-processes.md +++ b//autoscaling/ec2/userguide/understand-how-suspending-processes-affects-other-processes.md @@ -38 +38 @@ The following sections describe what happens when different processes are suspen - * `AlarmNotification` is still active, but your Auto Scaling group can't initiate scale-out activities for alarms that are in breach. + * `AlarmNotification` is still active, but your Amazon EC2 Auto Scaling group can't initiate scale-out activities for alarms that are in breach. @@ -40 +40 @@ The following sections describe what happens when different processes are suspen - * `ScheduledActions` is active, but your Auto Scaling group can't initiate scale-out activities for any scheduled actions that occur. + * `ScheduledActions` is active, but your Amazon EC2 Auto Scaling group can't initiate scale-out activities for any scheduled actions that occur. @@ -53 +53 @@ The following sections describe what happens when different processes are suspen - * `AlarmNotification` is still active, but your Auto Scaling group can't initiate scale in activities for alarms that are in breach. + * `AlarmNotification` is still active, but your Amazon EC2 Auto Scaling group can't initiate scale in activities for alarms that are in breach. @@ -55 +55 @@ The following sections describe what happens when different processes are suspen - * `ScheduledActions` is active, but your Auto Scaling group can't initiate scale in activities for any scheduled actions that occur. + * `ScheduledActions` is active, but your Amazon EC2 Auto Scaling group can't initiate scale in activities for any scheduled actions that occur. @@ -57 +57 @@ The following sections describe what happens when different processes are suspen - * `AZRebalance` is still active but does not function properly. It can launch new instances without terminating the old ones. This could cause your Auto Scaling group to grow up to 10 percent larger than its maximum size, because this is allowed temporarily during rebalancing activities. Your Auto Scaling group could remain above its maximum size until you resume the `Terminate` process. + * `AZRebalance` is still active but does not function properly. It can launch new instances without terminating the old ones. This could cause your Amazon EC2 Auto Scaling group to grow up to 10 percent larger than its maximum size, because this is allowed temporarily during rebalancing activities. Your Amazon EC2 Auto Scaling group could remain above its maximum size until you resume the `Terminate` process. @@ -91 +91 @@ The following sections describe what happens when different processes are suspen - * Amazon EC2 Auto Scaling stops marking instances unhealthy as a result of EC2 and Elastic Load Balancing health checks. Your custom health checks continue to function properly. After you suspend `HealthCheck`, if you need to, you can manually set the health state of instances in your group and have `ReplaceUnhealthy` replace them. + * Amazon EC2 Auto Scaling stops marking instances unhealthy as a result of EC2 and ELB health checks. Your custom health checks continue to function properly. After you suspend `HealthCheck`, if you need to, you can manually set the health state of instances in your group and have `ReplaceUnhealthy` replace them. @@ -105 +105 @@ The following sections describe what happens when different processes are suspen - * Amazon EC2 Auto Scaling stops replacing instances that are marked as unhealthy. Instances that fail EC2 or Elastic Load Balancing health checks are still marked as unhealthy. As soon as you resume the `ReplaceUnhealthy` process, Amazon EC2 Auto Scaling replaces instances that were marked unhealthy while this process was suspended. The `ReplaceUnhealthy` process calls `Terminate` first and then `Launch`. + * Amazon EC2 Auto Scaling stops replacing instances that are marked as unhealthy. Instances that fail EC2 or ELB health checks are still marked as unhealthy. As soon as you resume the `ReplaceUnhealthy` process, Amazon EC2 Auto Scaling replaces instances that were marked unhealthy while this process was suspended. The `ReplaceUnhealthy` process calls `Terminate` first and then `Launch`. @@ -123 +123 @@ In addition, when `Launch` or `Terminate` are suspended, the following features - * Spot Instance interruptions – If `Terminate` is suspended and your Auto Scaling group has Spot Instances, they can still terminate in the event that Spot capacity is no longer available. While `Launch` is suspended, Amazon EC2 Auto Scaling can't launch replacement instances from another Spot Instance pool or from the same Spot Instance pool when it is available again. + * Spot Instance interruptions – If `Terminate` is suspended and your Amazon EC2 Auto Scaling group has Spot Instances, they can still terminate in the event that Spot capacity is no longer available. While `Launch` is suspended, Amazon EC2 Auto Scaling can't launch replacement instances from another Spot Instance pool or from the same Spot Instance pool when it is available again. @@ -127 +127 @@ In addition, when `Launch` or `Terminate` are suspended, the following features - * Attaching and detaching instances – When `Launch` and `Terminate` are suspended, you can detach instances that are attached to your Auto Scaling group, but while `Launch` is suspended, you can't attach new instances to the group. + * Attaching and detaching instances – When `Launch` and `Terminate` are suspended, you can detach instances that are attached to your Amazon EC2 Auto Scaling group, but while `Launch` is suspended, you can't attach new instances to the group.