AWS autoscaling documentation change
Summary
Updated terminology from 'Auto Scaling' to 'Amazon EC2 Auto Scaling' throughout the document for consistency. Changed references from 'Elastic Load Balancing' to 'ELB' and updated links/documentation references.
Security assessment
The changes are purely terminological updates to use full service names ('Amazon EC2 Auto Scaling') and abbreviations ('ELB'). No security vulnerabilities, mitigations, or new security features are mentioned. The content about health checks and security group configuration remains functionally unchanged.
Diff
diff --git a/autoscaling/ec2/userguide/ts-as-healthchecks.md b/autoscaling/ec2/userguide/ts-as-healthchecks.md index 25529f3ed..33972c334 100644 --- a//autoscaling/ec2/userguide/ts-as-healthchecks.md +++ b//autoscaling/ec2/userguide/ts-as-healthchecks.md @@ -28 +28 @@ To retrieve an error message, see [View the reason for health check failures](./ -**Problem** : Auto Scaling instances fail the Amazon EC2 status checks. +**Problem** : Amazon EC2 Auto Scaling instances fail the Amazon EC2 status checks. @@ -30 +30 @@ To retrieve an error message, see [View the reason for health check failures](./ -**Cause 1** : If there are issues that cause Amazon EC2 to consider the instances in your Auto Scaling group impaired, Amazon EC2 Auto Scaling automatically replaces the instances as part of its health checks. +**Cause 1** : If there are issues that cause Amazon EC2 to consider the instances in your Amazon EC2 Auto Scaling group impaired, Amazon EC2 Auto Scaling automatically replaces the instances as part of its health checks. @@ -34 +34 @@ To retrieve an error message, see [View the reason for health check failures](./ - 1. Manually create an Amazon EC2 instance that is not part of the Auto Scaling group and investigate the problem. For general help with investigating impaired instances, see [Troubleshoot instances with failed status checks](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstances.html) in the _Amazon EC2 User Guide_. + 1. Manually create an Amazon EC2 instance that is not part of the Amazon EC2 Auto Scaling group and investigate the problem. For general help with investigating impaired instances, see [Troubleshoot instances with failed status checks](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstances.html) in the _Amazon EC2 User Guide_. @@ -36 +36 @@ To retrieve an error message, see [View the reason for health check failures](./ - 2. After you confirm that your instance launched successfully and is healthy, deploy a new, error-free instance configuration to the Auto Scaling group. + 2. After you confirm that your instance launched successfully and is healthy, deploy a new, error-free instance configuration to the Amazon EC2 Auto Scaling group. @@ -45 +45 @@ To retrieve an error message, see [View the reason for health check failures](./ -**Problem** : Auto Scaling instances that have been stopped, rebooted, or terminated are replaced. +**Problem** : Amazon EC2 Auto Scaling instances that have been stopped, rebooted, or terminated are replaced. @@ -49 +49 @@ To retrieve an error message, see [View the reason for health check failures](./ -**Solution 1** : If you need to stop or reboot the instances in your Auto Scaling group, we recommend that you put the instances on standby first. For more information, see [Temporarily remove instances from your Auto Scaling group](./as-enter-exit-standby.html). +**Solution 1** : If you need to stop or reboot the instances in your Amazon EC2 Auto Scaling group, we recommend that you put the instances on standby first. For more information, see [Temporarily remove instances from your Amazon EC2 Auto Scaling group](./as-enter-exit-standby.html). @@ -57 +57 @@ To retrieve an error message, see [View the reason for health check failures](./ - * Increase the number of different capacity pools that you can launch instances from by running multiple instance types in multiple Availability Zones. For more information, see [Auto Scaling groups with multiple instance types and purchase options](./ec2-auto-scaling-mixed-instances-groups.html). + * Increase the number of different capacity pools that you can launch instances from by running multiple instance types in multiple Availability Zones. For more information, see [Amazon EC2 Auto Scaling groups with multiple instance types and purchase options](./ec2-auto-scaling-mixed-instances-groups.html). @@ -59 +59 @@ To retrieve an error message, see [View the reason for health check failures](./ - * If you use multiple instance types, consider enabling the Capacity Rebalancing feature. This is useful if you want the Amazon EC2 Spot service to attempt to launch a new Spot Instance before a running instance is terminated. For more information, see [Capacity Rebalancing in Auto Scaling to replace at-risk Spot Instances](./ec2-auto-scaling-capacity-rebalancing.html). + * If you use multiple instance types, consider enabling the Capacity Rebalancing feature. This is useful if you want the Amazon EC2 Spot service to attempt to launch a new Spot Instance before a running instance is terminated. For more information, see [Capacity Rebalancing in Amazon EC2 Auto Scaling to replace at-risk Spot Instances](./ec2-auto-scaling-capacity-rebalancing.html). @@ -64 +64 @@ To retrieve an error message, see [View the reason for health check failures](./ -**Cause 3** : With Capacity Blocks, Amazon EC2 terminates any instances that are still running 30 minutes before the end time of the Capacity Block. This abrupt termination causes your Auto Scaling group to try to launch new instances to maintain its desired capacity, even as the Capacity Block is ending. +**Cause 3** : With Capacity Blocks, Amazon EC2 terminates any instances that are still running 30 minutes before the end time of the Capacity Block. This abrupt termination causes your Amazon EC2 Auto Scaling group to try to launch new instances to maintain its desired capacity, even as the Capacity Block is ending. @@ -68 +68 @@ To retrieve an error message, see [View the reason for health check failures](./ - * Decrease the desired capacity of the Auto Scaling group to prevent it from trying to launch new instances. For more information, see [Manual scaling for Amazon EC2 Auto Scaling](./ec2-auto-scaling-scaling-manually.html). + * Decrease the desired capacity of the Amazon EC2 Auto Scaling group to prevent it from trying to launch new instances. For more information, see [Manual scaling for Amazon EC2 Auto Scaling](./ec2-auto-scaling-scaling-manually.html). @@ -70 +70 @@ To retrieve an error message, see [View the reason for health check failures](./ - * Make sure you scale in your Auto Scaling group 30 minutes before the Capacity Block end time so that you do not encounter this error frequently. Make sure any lifecycle hooks have completed 30 minutes before the Capacity Block end time. For more information, see [Use Capacity Blocks for machine learning workloads](./launch-template-capacity-blocks.html). + * Make sure you scale in your Amazon EC2 Auto Scaling group 30 minutes before the Capacity Block end time so that you do not encounter this error frequently. Make sure any lifecycle hooks have completed 30 minutes before the Capacity Block end time. For more information, see [Use Capacity Blocks for machine learning workloads](./launch-template-capacity-blocks.html). @@ -77 +77 @@ To retrieve an error message, see [View the reason for health check failures](./ -**Problem** : Auto Scaling instances might pass the EC2 status checks. But they might fail the Elastic Load Balancing health checks for the target groups or Classic Load Balancers with which the Auto Scaling group is registered. +**Problem** : Amazon EC2 Auto Scaling instances might pass the EC2 status checks. But they might fail the ELB health checks for the target groups or Classic Load Balancers with which the Amazon EC2 Auto Scaling group is registered. @@ -79 +79 @@ To retrieve an error message, see [View the reason for health check failures](./ -**Cause 1** : If your Auto Scaling group relies on health checks provided by Elastic Load Balancing, Amazon EC2 Auto Scaling determines the health status of your instances by checking the results of both the EC2 status checks and the Elastic Load Balancing health checks. The load balancer performs health checks by sending a request to each instance and waiting for the correct response, or by establishing a connection with the instance. An instance might fail the Elastic Load Balancing health check because an application running on the instance has issues that cause the load balancer to consider the instance out of service. +**Cause 1** : If your Amazon EC2 Auto Scaling group relies on health checks provided by ELB, Amazon EC2 Auto Scaling determines the health status of your instances by checking the results of both the EC2 status checks and the ELB health checks. The load balancer performs health checks by sending a request to each instance and waiting for the correct response, or by establishing a connection with the instance. An instance might fail the ELB health check because an application running on the instance has issues that cause the load balancer to consider the instance out of service. @@ -81 +81 @@ To retrieve an error message, see [View the reason for health check failures](./ -**Solution 1** : To pass the Elastic Load Balancing health checks: +**Solution 1** : To pass the ELB health checks: @@ -87 +87 @@ To retrieve an error message, see [View the reason for health check failures](./ - * Verify that the security groups for your load balancer and Auto Scaling group are correctly configured. + * Verify that the security groups for your load balancer and Amazon EC2 Auto Scaling group are correctly configured. @@ -89 +89 @@ To retrieve an error message, see [View the reason for health check failures](./ - * Verify that the load balancer is configured in the same Availability Zones as your Auto Scaling group. + * Verify that the load balancer is configured in the same Availability Zones as your Amazon EC2 Auto Scaling group. @@ -94 +94 @@ To retrieve an error message, see [View the reason for health check failures](./ -**Solution 2** : Update the Auto Scaling group to turn off Elastic Load Balancing health checks. For instructions for how to turn off these health checks, see [ Detach a target group or Classic Load Balancer](https://docs.aws.amazon.com/autoscaling/ec2/userguide/attach-load-balancer-asg.html#as-remove-load-balancer). +**Solution 2** : Update the Amazon EC2 Auto Scaling group to turn off ELB health checks. For instructions for how to turn off these health checks, see [ Detach a target group or Classic Load Balancer](https://docs.aws.amazon.com//autoscaling/ec2/userguide/attach-load-balancer-asg.html#as-remove-load-balancer). @@ -98 +98 @@ To retrieve an error message, see [View the reason for health check failures](./ -**Solution 3** : Edit the health check grace period for your Auto Scaling group. Set the grace period to a long enough time period to support the number of consecutive successful health checks required before Elastic Load Balancing considers a newly launched instance healthy. For more information, see [Set the health check grace period for an Auto Scaling group](./health-check-grace-period.html). +**Solution 3** : Edit the health check grace period for your Amazon EC2 Auto Scaling group. Set the grace period to a long enough time period to support the number of consecutive successful health checks required before ELB considers a newly launched instance healthy. For more information, see [Set the health check grace period for an Amazon EC2 Auto Scaling group](./health-check-grace-period.html).