AWS autoscaling documentation change
Summary
Updated terminology from 'ELB' to 'Elastic Load Balancing' throughout the document for consistency and clarity. Changed headings, body text, and link references to use the full service name instead of the acronym.
Security assessment
The changes are purely terminological updates without introducing new security concepts, addressing vulnerabilities, or modifying security configurations. The security group reference remains unchanged in functionality, only updating the service name.
Diff
diff --git a/autoscaling/ec2/userguide/getting-started-elastic-load-balancing.md b/autoscaling/ec2/userguide/getting-started-elastic-load-balancing.md index 8505cf5a2..ee4eaeef4 100644 --- a//autoscaling/ec2/userguide/getting-started-elastic-load-balancing.md +++ b//autoscaling/ec2/userguide/getting-started-elastic-load-balancing.md @@ -7 +7 @@ Configure health checks for targets -# Prepare to attach an ELB load balancer +# Prepare to attach an Elastic Load Balancing load balancer @@ -9 +9 @@ Configure health checks for targets -Before you attach an ELB load balancer to your Auto Scaling group, you must complete the following prerequisites: +Before you attach an Elastic Load Balancing load balancer to your Auto Scaling group, you must complete the following prerequisites: @@ -15 +15 @@ There are two ways to create the load balancer and target group: - * Using ELB – Follow the procedures in the ELB documentation to create and configure the load balancer and target group before creating the Auto Scaling group. Skip the step for registering your Amazon EC2 instances. Amazon EC2 Auto Scaling automatically takes care of registering (and deregistering) instances when you attach a target group to your Auto Scaling group. For more information, see [Getting started with ELB](https://docs.aws.amazon.com/elasticloadbalancing/latest/userguide/load-balancer-getting-started.html) in the _Elastic Load Balancing User Guide_. + * Using Elastic Load Balancing – Follow the procedures in the Elastic Load Balancing documentation to create and configure the load balancer and target group before creating the Auto Scaling group. Skip the step for registering your Amazon EC2 instances. Amazon EC2 Auto Scaling automatically takes care of registering (and deregistering) instances when you attach a target group to your Auto Scaling group. For more information, see [Getting started with Elastic Load Balancing](https://docs.aws.amazon.com/elasticloadbalancing/latest/userguide/load-balancer-getting-started.html) in the _Elastic Load Balancing User Guide_. @@ -19 +19 @@ There are two ways to create the load balancer and target group: - * Before creating a load balancer, know the type of load balancer that you need. For more information, see [ELB types](./autoscaling-load-balancer.html#integrations-aws-elastic-load-balancing-types). + * Before creating a load balancer, know the type of load balancer that you need. For more information, see [Elastic Load Balancing types](./autoscaling-load-balancer.html#integrations-aws-elastic-load-balancing-types). @@ -27 +27 @@ There are two ways to create the load balancer and target group: - * The security groups in the launch template must also allow access from the load balancer on the correct port for ELB to perform its health checks. + * The security groups in the launch template must also allow access from the load balancer on the correct port for Elastic Load Balancing to perform its health checks. @@ -40 +40 @@ If you have bootstrapping scripts that take a while to complete, you can optiona -You can configure health checks for your targets registered with an ELB load balancer to ensure they are able to handle traffic properly. The specific steps vary based on the type of load balancer you are using. For more information, see the following resources: +You can configure health checks for your targets registered with an Elastic Load Balancing load balancer to ensure they are able to handle traffic properly. The specific steps vary based on the type of load balancer you are using. For more information, see the following resources: @@ -53 +53 @@ You can configure health checks for your targets registered with an ELB load bal -By default, Amazon EC2 Auto Scaling does not consider an instance unhealthy and replace it if it fails the ELB health checks. The default health checks for an Auto Scaling group are EC2 health checks only. For more information, see [Health checks for instances in an Auto Scaling group](./ec2-auto-scaling-health-checks.html). +By default, Amazon EC2 Auto Scaling does not consider an instance unhealthy and replace it if it fails the Elastic Load Balancing health checks. The default health checks for an Auto Scaling group are EC2 health checks only. For more information, see [Health checks for instances in an Auto Scaling group](./ec2-auto-scaling-health-checks.html). @@ -55 +55 @@ By default, Amazon EC2 Auto Scaling does not consider an instance unhealthy and -To enable Amazon EC2 Auto Scaling to replace instances that are reported unhealthy by ELB, you can configure your Auto Scaling group to use ELB health checks. By doing so, Amazon EC2 Auto Scaling considers the instance unhealthy if it fails either the EC2 health checks or the ELB health checks. If you attach multiple load balancer target groups or Classic Load Balancers to the group, all of them must report that an instance is healthy in order for it to consider the instance healthy. If any one of them reports an instance as unhealthy, the Auto Scaling group replaces the instance, even if others report it as healthy. +To enable Amazon EC2 Auto Scaling to replace instances that are reported unhealthy by Elastic Load Balancing, you can configure your Auto Scaling group to use Elastic Load Balancing health checks. By doing so, Amazon EC2 Auto Scaling considers the instance unhealthy if it fails either the EC2 health checks or the Elastic Load Balancing health checks. If you attach multiple load balancer target groups or Classic Load Balancers to the group, all of them must report that an instance is healthy in order for it to consider the instance healthy. If any one of them reports an instance as unhealthy, the Auto Scaling group replaces the instance, even if others report it as healthy. @@ -57 +57 @@ To enable Amazon EC2 Auto Scaling to replace instances that are reported unhealt -For information about how to enable these health checks for your Auto Scaling group, see [Attach an ELB load balancer to your Auto Scaling group](./attach-load-balancer-asg.html). +For information about how to enable these 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). @@ -61 +61 @@ For information about how to enable these health checks for your Auto Scaling gr -To make sure that these health checks start as soon as possible, make sure your group's health check grace period is not set too high, but high enough for your ELB health checks to determine whether a target is available to handle requests. For more information, see [Set the health check grace period for an Auto Scaling group](./health-check-grace-period.html). +To make sure that these health checks start as soon as possible, make sure your group's health check grace period is not set too high, but high enough for your Elastic Load Balancing health checks to determine whether a target is available to handle requests. For more information, see [Set the health check grace period for an Auto Scaling group](./health-check-grace-period.html). @@ -69 +69 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -ELB +Elastic Load Balancing