AWS AWSCloudFormation documentation change
Summary
Updated terminology: replaced 'Auto Scaling group' with 'Amazon EC2 Auto Scaling group' and 'Elastic Load Balancing' with 'ELB' for consistency. Minor phrasing adjustments in health check and deregistration delay descriptions.
Security assessment
Changes are purely editorial/branding updates without modifying security configurations. References to security groups remain unchanged, and no vulnerabilities or security enhancements are mentioned.
Diff
diff --git a/AWSCloudFormation/latest/UserGuide/walkthrough-autoscaling.md b/AWSCloudFormation/latest/UserGuide/walkthrough-autoscaling.md index bc47f6603..7173e5af8 100644 --- a//AWSCloudFormation/latest/UserGuide/walkthrough-autoscaling.md +++ b//AWSCloudFormation/latest/UserGuide/walkthrough-autoscaling.md @@ -9 +9 @@ Full stack templateTemplate walkthroughStep 1: Launch the stackStep 2: Clean up -For this walkthrough, you create a stack that helps you set up a scaled and load-balanced application. The walkthrough provides a sample template that you use to create the stack. The example template provisions an Auto Scaling group, an Application Load Balancer, security groups that control traffic to the load balancer and to the Auto Scaling group, and an Amazon SNS notification configuration to publish notifications about scaling activities. +For this walkthrough, you create a stack that helps you set up a scaled and load-balanced application. The walkthrough provides a sample template that you use to create the stack. The example template provisions an Amazon EC2 Auto Scaling group, an Application Load Balancer, security groups that control traffic to the load balancer and to the Amazon EC2 Auto Scaling group, and an Amazon SNS notification configuration to publish notifications about scaling activities. @@ -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 Elastic Load Balancing 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 ELB 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 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. + * `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. @@ -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, Elastic Load Balancing waits 300 seconds before completing the deregistration process. + * `TargetGroupAttributes` updates the deregistration delay value of the target group to 20 seconds. By default, ELB waits 300 seconds before completing the deregistration process. @@ -493 +493 @@ The next part of this template specifies the `Resources`. This section specifies - * `MinSize` and `MaxSize` set the minimum and maximum number of EC2 instances in the Auto Scaling group. + * `MinSize` and `MaxSize` set the minimum and maximum number of EC2 instances in the Amazon EC2 Auto Scaling group. @@ -495 +495 @@ The next part of this template specifies the `Resources`. This section specifies - * `TargetGroupARNs` takes the ARN of the target group with the logical name `EC2TargetGroup`. As this Auto Scaling group scales, it automatically registers and deregisters instances with this target group. + * `TargetGroupARNs` takes the ARN of the target group with the logical name `EC2TargetGroup`. As this Amazon EC2 Auto Scaling group scales, it automatically registers and deregisters instances with this target group. @@ -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, Elastic Load Balancing, 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, ELB, Amazon SNS, and CloudFormation. @@ -532 +532 @@ You can view the status of the stack in the CloudFormation console in the **Stat -After you create the stack, you must confirm the subscription before the email address can start to receive notifications. For more information, see [Get Amazon SNS notifications when your Auto Scaling group scales](https://docs.aws.amazon.com/autoscaling/ec2/userguide/ec2-auto-scaling-sns-notifications.html) in the _Amazon EC2 Auto Scaling User Guide_. +After you create the stack, you must confirm the subscription before the email address can start to receive notifications. For more information, see [Get Amazon SNS notifications when your Amazon EC2 Auto Scaling group scales](https://docs.aws.amazon.com/autoscaling/ec2/userguide/ec2-auto-scaling-sns-notifications.html) in the _Amazon EC2 Auto Scaling User Guide_.