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. Minor phrasing adjustments and link updates.
Security assessment
Changes are purely terminological updates and branding consistency (e.g., 'ELB' instead of 'Elastic Load Balancing'). No security vulnerabilities, configurations, or features are mentioned or modified. Health check behaviors remain unchanged.
Diff
diff --git a/autoscaling/ec2/userguide/health-checks-overview.md b/autoscaling/ec2/userguide/health-checks-overview.md index 3695b5f72..d76c2253f 100644 --- a//autoscaling/ec2/userguide/health-checks-overview.md +++ b//autoscaling/ec2/userguide/health-checks-overview.md @@ -5 +5 @@ -Health check typesAmazon EC2 health checksElastic Load Balancing health checksVPC Lattice health checksHow Amazon EC2 Auto Scaling minimizes downtimeHealth checks for instances in a warm poolHealth check considerations +Health check typesAmazon EC2 health checksELB health checksVPC Lattice health checksHow Amazon EC2 Auto Scaling minimizes downtimeHealth checks for instances in a warm poolHealth check considerations @@ -7 +7 @@ Health check typesAmazon EC2 health checksElastic Load Balancing health checksVP -# About the health checks for your Auto Scaling group +# About the health checks for your Amazon EC2 Auto Scaling group @@ -17 +17 @@ This topic provides an overview of the available health check types and describe - * Elastic Load Balancing health checks + * ELB health checks @@ -41,2 +41,2 @@ Amazon EC2 status checks and scheduled events | -This is the default health check type for an Auto Scaling group. -Elastic Load Balancing health checks | +This is the default health check type for an Amazon EC2 Auto Scaling group. +ELB health checks | @@ -46 +46 @@ Elastic Load Balancing health checks | -To run this health check type, you must turn it on for your Auto Scaling group. +To run this health check type, you must turn it on for your Amazon EC2 Auto Scaling group. @@ -51 +51 @@ VPC Lattice health checks | -To run this health check type, you must turn it on for your Auto Scaling group. +To run this health check type, you must turn it on for your Amazon EC2 Auto Scaling group. @@ -56 +56 @@ Amazon EBS health checks | -To run this health check type, you must turn it on for your Auto Scaling group. +To run this health check type, you must turn it on for your Amazon EC2 Auto Scaling group. @@ -65 +65 @@ Custom health checks | -After an instance launches, it's attached to the Auto Scaling group and enters the `InService` state. For more information about the different lifecycle states for instances in an Auto Scaling group, see [Amazon EC2 Auto Scaling instance lifecycle](./ec2-auto-scaling-lifecycle.html). +After an instance launches, it's attached to the Amazon EC2 Auto Scaling group and enters the `InService` state. For more information about the different lifecycle states for instances in an Amazon EC2 Auto Scaling group, see [Amazon EC2 Auto Scaling instance lifecycle](./ec2-auto-scaling-lifecycle.html). @@ -67 +67 @@ After an instance launches, it's attached to the Auto Scaling group and enters t -Amazon EC2 Auto Scaling periodically checks the health status of all instances within the Auto Scaling group to make sure that they're running and in good condition. +Amazon EC2 Auto Scaling periodically checks the health status of all instances within the Amazon EC2 Auto Scaling group to make sure that they're running and in good condition. @@ -88 +88 @@ The Amazon EC2 status checks do not require any special configuration and are al -Amazon EC2 Auto Scaling lets the status checks fail occasionally, without taking any action. When a status check fails, Amazon EC2 Auto Scaling waits a few minutes for AWS to fix the issue. It does not immediately mark an instance `Unhealthy` when its status for the status checks becomes `impaired`. Additionally, EC2 Auto Scaling doesn't mark the instance as `Unhealthy` if a status check returns `insufficient-data`. +Amazon EC2 Auto Scaling lets the status checks fail occasionally, without taking any action. When a status check fails, Amazon EC2 Auto Scaling waits a few minutes for AWS to fix the issue. It does not immediately mark an instance `Unhealthy` when its status for the status checks becomes `impaired`. Additionally, EC2 Amazon EC2 Auto Scaling doesn't mark the instance as `Unhealthy` if a status check returns `insufficient-data`. @@ -98 +98 @@ If one of your instances is affected by a scheduled event, Amazon EC2 Auto Scali -## Elastic Load Balancing health checks +## ELB health checks @@ -100 +100 @@ If one of your instances is affected by a scheduled event, Amazon EC2 Auto Scali -When you turn on Elastic Load Balancing health checks for your Auto Scaling group, Amazon EC2 Auto Scaling can use the results of those health checks to determine the health status of an instance. +When you turn on ELB health checks for your Amazon EC2 Auto Scaling group, Amazon EC2 Auto Scaling can use the results of those health checks to determine the health status of an instance. @@ -102 +102 @@ When you turn on Elastic Load Balancing health checks for your Auto Scaling grou -Before you can turn on Elastic Load Balancing health checks for your Auto Scaling group, you must configure an Elastic Load Balancing load balancer and configure a health check for it to determine if your instances are healthy. For more information, see [Prepare to attach an Elastic Load Balancing load balancer](./getting-started-elastic-load-balancing.html). +Before you can turn on ELB health checks for your Amazon EC2 Auto Scaling group, you must configure an ELB load balancer and configure a health check for it to determine if your instances are healthy. For more information, see [Prepare to attach an ELB load balancer](./getting-started-elastic-load-balancing.html). @@ -104 +104 @@ Before you can turn on Elastic Load Balancing health checks for your Auto Scalin -After you attach the load balancer to your Auto Scaling group, the following occurs: +After you attach the load balancer to your Amazon EC2 Auto Scaling group, the following occurs: @@ -106 +106 @@ After you attach the load balancer to your Auto Scaling group, the following occ - * Amazon EC2 Auto Scaling registers the instances in the Auto Scaling group with the load balancer. + * Amazon EC2 Auto Scaling registers the instances in the Amazon EC2 Auto Scaling group with the load balancer. @@ -113 +113 @@ After you attach the load balancer to your Auto Scaling group, the following occ -By default, Amazon EC2 Auto Scaling ignores the results of the Elastic Load Balancing health checks. After you turn on these health checks for your Auto Scaling group, when Elastic Load Balancing reports a registered instance as `Unhealthy`, Amazon EC2 Auto Scaling marks the instance `Unhealthy` on its next periodic health check and replaces it. +By default, Amazon EC2 Auto Scaling ignores the results of the ELB health checks. After you turn on these health checks for your Amazon EC2 Auto Scaling group, when ELB reports a registered instance as `Unhealthy`, Amazon EC2 Auto Scaling marks the instance `Unhealthy` on its next periodic health check and replaces it. @@ -119 +119 @@ If connection draining (deregistration delay) is enabled for your load balancer, -For instructions for how to attach the load balancer and turn on Elastic Load Balancing health checks for your Auto Scaling group, see [Attach an Elastic Load Balancing load balancer to your Auto Scaling group](./attach-load-balancer-asg.html). +For instructions for how to attach the load balancer and turn on ELB health checks for your Amazon EC2 Auto Scaling group, see [Attach an ELB load balancer to your Amazon EC2 Auto Scaling group](./attach-load-balancer-asg.html). @@ -121 +121 @@ For instructions for how to attach the load balancer and turn on Elastic Load Ba -When you turn on Elastic Load Balancing health checks for a group, Amazon EC2 Auto Scaling can replace instances that Elastic Load Balancing reports as unhealthy, but only after the load balancer is in the `InService` state. For more information, see [Verify the attachment status of your load balancer](./load-balancer-status.html). +When you turn on ELB health checks for a group, Amazon EC2 Auto Scaling can replace instances that ELB reports as unhealthy, but only after the load balancer is in the `InService` state. For more information, see [Verify the attachment status of your load balancer](./load-balancer-status.html). @@ -125 +125 @@ When you turn on Elastic Load Balancing health checks for a group, Amazon EC2 Au -By default, Amazon EC2 Auto Scaling ignores the results of the VPC Lattice health checks. You can optionally turn on these health checks for your Auto Scaling group. After you do this, when VPC Lattice reports a registered instance as `Unhealthy`, Amazon EC2 Auto Scaling marks the instance `Unhealthy` on its next periodic health check and replaces it. The process of registering instances and then checking their health is the same as how Elastic Load Balancing health checks work. +By default, Amazon EC2 Auto Scaling ignores the results of the VPC Lattice health checks. You can optionally turn on these health checks for your Amazon EC2 Auto Scaling group. After you do this, when VPC Lattice reports a registered instance as `Unhealthy`, Amazon EC2 Auto Scaling marks the instance `Unhealthy` on its next periodic health check and replaces it. The process of registering instances and then checking their health is the same as how ELB health checks work. @@ -129 +129 @@ By default, Amazon EC2 Auto Scaling ignores the results of the VPC Lattice healt -For instructions for how to attach the VPC Lattice target group and turn on VPC Lattice health checks for your Auto Scaling group, see [Attach a VPC Lattice target group to your Auto Scaling group](./attach-vpc-lattice-target-group-asg.html). +For instructions for how to attach the VPC Lattice target group and turn on VPC Lattice health checks for your Amazon EC2 Auto Scaling group, see [Attach a VPC Lattice target group to your Amazon EC2 Auto Scaling group](./attach-vpc-lattice-target-group-asg.html). @@ -139 +139 @@ If Amazon EC2 Auto Scaling determines that any instances are no longer running ( - * If a scaling activity is in progress and your Auto Scaling group is less than its desired capacity by 10 percent or more, Amazon EC2 Auto Scaling waits for the in-progress scaling activity before replacing the unhealthy instances. + * If a scaling activity is in progress and your Amazon EC2 Auto Scaling group is less than its desired capacity by 10 percent or more, Amazon EC2 Auto Scaling waits for the in-progress scaling activity before replacing the unhealthy instances. @@ -154 +154 @@ If Amazon EC2 Auto Scaling determines that any instances are no longer running ( - * If the size of an Auto Scaling group is small enough that the resulting value of 10 percent is less than one, Amazon EC2 Auto Scaling instead replaces the unhealthy instances one at a time. This might result in some downtime for the group. + * If the size of an Amazon EC2 Auto Scaling group is small enough that the resulting value of 10 percent is less than one, Amazon EC2 Auto Scaling instead replaces the unhealthy instances one at a time. This might result in some downtime for the group. @@ -156 +156 @@ If Amazon EC2 Auto Scaling determines that any instances are no longer running ( - * You can modify the default 10 percent value by [setting an instance maintenance policy](https://docs.aws.amazon.com/autoscaling/ec2/userguide/set-instance-maintenance-policy-on-group.html) to change the rate at which Auto Scaling replaces unhealthy instances. However, Auto Scaling might still throttle the rate it marks instances as unhealthy. + * You can modify the default 10 percent value by [setting an instance maintenance policy](https://docs.aws.amazon.com//autoscaling/ec2/userguide/set-instance-maintenance-policy-on-group.html) to change the rate at which Amazon EC2 Auto Scaling replaces unhealthy instances. However, Amazon EC2 Auto Scaling might still throttle the rate it marks instances as unhealthy. @@ -158 +158 @@ If Amazon EC2 Auto Scaling determines that any instances are no longer running ( -For example, if all instances in an Auto Scaling group are reported unhealthy by Elastic Load Balancing health checks and the load balancer is in the `InService` state, Amazon EC2 Auto Scaling might mark fewer instances unhealthy at a time. This can result in much fewer instances replaced at a time than the 10 percent applied in other scenarios. This provides you with time to fix the problem without Amazon EC2 Auto Scaling automatically terminating the entire group. +For example, if all instances in an Amazon EC2 Auto Scaling group are reported unhealthy by ELB health checks and the load balancer is in the `InService` state, Amazon EC2 Auto Scaling might mark fewer instances unhealthy at a time. This can result in much fewer instances replaced at a time than the 10 percent applied in other scenarios. This provides you with time to fix the problem without Amazon EC2 Auto Scaling automatically terminating the entire group. @@ -173 +173 @@ The following are considerations when using Amazon EC2 Auto Scaling health check - * Amazon EC2 Auto Scaling does not provide a way of removing the Amazon EC2 status checks and scheduled events from its health checks. If you do not want instances to be replaced, we recommend that you suspend the `ReplaceUnhealthy` and `HealthCheck` process for individual Auto Scaling groups. For more information, see [Suspend and resume Amazon EC2 Auto Scaling processes](./as-suspend-resume-processes.html). + * Amazon EC2 Auto Scaling does not provide a way of removing the Amazon EC2 status checks and scheduled events from its health checks. If you do not want instances to be replaced, we recommend that you suspend the `ReplaceUnhealthy` and `HealthCheck` process for individual Amazon EC2 Auto Scaling groups. For more information, see [Suspend and resume Amazon EC2 Auto Scaling processes](./as-suspend-resume-processes.html). @@ -177 +177 @@ The following are considerations when using Amazon EC2 Auto Scaling health check - * If you need to troubleshoot an instance without interference from health checks, you can put the instance in `Standby` state. Amazon EC2 Auto Scaling does not perform health checks on instances that are in the `Standby` state until you put the instances back in service. For more information, see [Temporarily remove instances from your Auto Scaling group](./as-enter-exit-standby.html). + * If you need to troubleshoot an instance without interference from health checks, you can put the instance in `Standby` state. Amazon EC2 Auto Scaling does not perform health checks on instances that are in the `Standby` state until you put the instances back in service. For more information, see [Temporarily remove instances from your Amazon EC2 Auto Scaling group](./as-enter-exit-standby.html).