AWS AWSCloudFormation documentation change
Summary
Updated terminology from 'ELB' to 'Elastic Load Balancing' in health check and deregistration delay descriptions, and in IAM permissions list
Security assessment
Change is purely terminological (ELB → Elastic Load Balancing) with no security implications. No vulnerabilities, configurations, or security features were modified or added.
Diff
diff --git a/AWSCloudFormation/latest/UserGuide/walkthrough-autoscaling.md b/AWSCloudFormation/latest/UserGuide/walkthrough-autoscaling.md index db6efcb1a..d52e768a9 100644 --- a//AWSCloudFormation/latest/UserGuide/walkthrough-autoscaling.md +++ b//AWSCloudFormation/latest/UserGuide/walkthrough-autoscaling.md @@ -446 +446 @@ The next part of this template specifies the `Resources`. This section specifies - * `Port`, `Protocol`, and `HealthCheckProtocol` specify the EC2 instance port (80) and protocol (HTTP) that the `ApplicationLoadBalancer` routes traffic to and that ELB uses to check the health of the EC2 instances. + * `Port`, `Protocol`, and `HealthCheckProtocol` specify the EC2 instance port (80) and protocol (HTTP) that the `ApplicationLoadBalancer` routes traffic to and that Elastic Load Balancing uses to check the health of the EC2 instances. @@ -448 +448 @@ The next part of this template specifies the `Resources`. This section specifies - * `HealthCheckIntervalSeconds` specifies that the EC2 instances have an interval of 30 seconds between health checks. The `HealthCheckTimeoutSeconds` is defined as the length of time ELB waits for a response from the health check target (15 seconds in this example). After the timeout period lapses, ELB marks that EC2 instance's health check as unhealthy. When an EC2 instance fails three consecutive health checks (`UnhealthyThresholdCount`), ELB stops routing traffic to that EC2 instance until that instance has five consecutive healthy health checks (`HealthyThresholdCount`). At that point, ELB considers the instance healthy and begins routing traffic to the instance again. + * `HealthCheckIntervalSeconds` specifies that the EC2 instances have an interval of 30 seconds between health checks. The `HealthCheckTimeoutSeconds` is defined as the length of time Elastic Load Balancing waits for a response from the health check target (15 seconds in this example). After the timeout period lapses, Elastic Load Balancing marks that EC2 instance's health check as unhealthy. When an EC2 instance fails three consecutive health checks (`UnhealthyThresholdCount`), Elastic Load Balancing stops routing traffic to that EC2 instance until that instance has five consecutive healthy health checks (`HealthyThresholdCount`). At that point, Elastic Load Balancing considers the instance healthy and begins routing traffic to the instance again. @@ -450 +450 @@ The next part of this template specifies the `Resources`. This section specifies - * `TargetGroupAttributes` updates the deregistration delay value of the target group to 20 seconds. By default, ELB waits 300 seconds before completing the deregistration process. + * `TargetGroupAttributes` updates the deregistration delay value of the target group to 20 seconds. By default, Elastic Load Balancing waits 300 seconds before completing the deregistration process. @@ -504 +504 @@ The next part of this template specifies the `Resources`. This section specifies -Before you launch the stack, check that you have AWS Identity and Access Management (IAM) permissions to use all of the following services: Amazon EC2, Amazon EC2 Auto Scaling, AWS Systems Manager, ELB, Amazon SNS, and CloudFormation. +Before you launch the stack, check that you have AWS Identity and Access Management (IAM) permissions to use all of the following services: Amazon EC2, Amazon EC2 Auto Scaling, AWS Systems Manager, Elastic Load Balancing, Amazon SNS, and CloudFormation.