AWS autoscaling documentation change
Summary
Updated terminology from 'Elastic Load Balancing' to 'ELB' and 'Auto Scaling group' to 'Amazon EC2 Auto Scaling group' throughout the document. Changed references to documentation links and maintained consistency in product naming conventions.
Security assessment
The changes primarily involve branding updates and terminology standardization (e.g., Elastic Load Balancing -> ELB). While some security-related content exists (e.g., security group requirements), these are pre-existing configuration recommendations. No new security vulnerabilities or security features were introduced in these changes.
Diff
diff --git a/autoscaling/ec2/userguide/getting-started-elastic-load-balancing.md b/autoscaling/ec2/userguide/getting-started-elastic-load-balancing.md index ee4eaeef4..fadaed873 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 Elastic Load Balancing load balancer +# Prepare to attach an ELB load balancer @@ -9 +9 @@ Configure health checks for targets -Before you attach an Elastic Load Balancing load balancer to your Auto Scaling group, you must complete the following prerequisites: +Before you attach an ELB load balancer to your Amazon EC2 Auto Scaling group, you must complete the following prerequisites: @@ -11 +11 @@ Before you attach an Elastic Load Balancing load balancer to your Auto Scaling g - * You must have already created the load balancer and target group that is used to route traffic to your Auto Scaling group. + * You must have already created the load balancer and target group that is used to route traffic to your Amazon EC2 Auto Scaling group. @@ -15 +15 @@ There are two ways to create the load balancer and target group: - * 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_. + * Using ELB – Follow the procedures in the ELB documentation to create and configure the load balancer and target group before creating the Amazon EC2 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 Amazon EC2 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_. @@ -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 [Elastic Load Balancing 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 [ELB types](./autoscaling-load-balancer.html#integrations-aws-elastic-load-balancing-types). @@ -21 +21 @@ There are two ways to create the load balancer and target group: - * The load balancer and its target group must be in the same AWS account, VPC, and Region as your Auto Scaling group. + * The load balancer and its target group must be in the same AWS account, VPC, and Region as your Amazon EC2 Auto Scaling group. @@ -23 +23 @@ There are two ways to create the load balancer and target group: - * The target group must specify a target type of `instance`. You can't specify a target type of `ip` when using an Auto Scaling group. + * The target group must specify a target type of `instance`. You can't specify a target type of `ip` when using an Amazon EC2 Auto Scaling group. @@ -25 +25 @@ There are two ways to create the load balancer and target group: - * If the launch template for your Auto Scaling group does not contain the correct security group to allow the necessary inbound traffic from the load balancer, you must update the launch template. The recommended rules depend on the type of load balancer and the types of backends that the load balancer uses. For example, to route traffic to web servers, allow inbound HTTP access on port 80 from the load balancer. Existing instances are not updated with the new settings when the launch template is modified. To update existing instances, you can start an instance refresh to replace the instances. For more information, see [Use an instance refresh to update instances in an Auto Scaling group](./asg-instance-refresh.html). + * If the launch template for your Amazon EC2 Auto Scaling group does not contain the correct security group to allow the necessary inbound traffic from the load balancer, you must update the launch template. The recommended rules depend on the type of load balancer and the types of backends that the load balancer uses. For example, to route traffic to web servers, allow inbound HTTP access on port 80 from the load balancer. Existing instances are not updated with the new settings when the launch template is modified. To update existing instances, you can start an instance refresh to replace the instances. For more information, see [Use an instance refresh to update instances in an Amazon EC2 Auto Scaling group](./asg-instance-refresh.html). @@ -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 Elastic Load Balancing 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 ELB to perform its health checks. @@ -29 +29 @@ There are two ways to create the load balancer and target group: - * When deploying virtual appliances behind a Gateway Load Balancer, the Amazon Machine Image (AMI) in the launch template must specify the ID of an AMI that supports the GENEVE protocol to allow the Auto Scaling group to exchange traffic with a Gateway Load Balancer. Also, the security groups in the launch template must allow UDP traffic on port 6081. + * When deploying virtual appliances behind a Gateway Load Balancer, the Amazon Machine Image (AMI) in the launch template must specify the ID of an AMI that supports the GENEVE protocol to allow the Amazon EC2 Auto Scaling group to exchange traffic with a Gateway Load Balancer. Also, the security groups in the launch template must allow UDP traffic on port 6081. @@ -36 +36 @@ There are two ways to create the load balancer and target group: -If you have bootstrapping scripts that take a while to complete, you can optionally add a launch lifecycle hook to your Auto Scaling group to delay instances from registering behind the load balancer before your bootstrap scripts have completed successfully and the applications on the instances are ready to accept traffic. You can't add a lifecycle hook when you initially create an Auto Scaling group in the Amazon EC2 Auto Scaling console. However, you can add a lifecycle hook after the group is created. For more information, see [Amazon EC2 Auto Scaling lifecycle hooks](./lifecycle-hooks.html). +If you have bootstrapping scripts that take a while to complete, you can optionally add a launch lifecycle hook to your Amazon EC2 Auto Scaling group to delay instances from registering behind the load balancer before your bootstrap scripts have completed successfully and the applications on the instances are ready to accept traffic. You can't add a lifecycle hook when you initially create an Amazon EC2 Auto Scaling group in the Amazon EC2 Auto Scaling console. However, you can add a lifecycle hook after the group is created. For more information, see [Amazon EC2 Auto Scaling lifecycle hooks](./lifecycle-hooks.html). @@ -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 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: +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: @@ -53 +53 @@ You can configure health checks for your targets registered with an Elastic Load -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). +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 Amazon EC2 Auto Scaling group are EC2 health checks only. For more information, see [Health checks for instances in an Amazon EC2 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 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. +To enable Amazon EC2 Auto Scaling to replace instances that are reported unhealthy by ELB, you can configure your Amazon EC2 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 Amazon EC2 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 Elastic Load Balancing load balancer to your Auto Scaling group](./attach-load-balancer-asg.html). +For information about how to enable these 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). @@ -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 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). +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 Amazon EC2 Auto Scaling group](./health-check-grace-period.html). @@ -69 +69 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Elastic Load Balancing +ELB