AWS AWSCloudFormation documentation change
Summary
Updated terminology from 'Auto Scaling groups' to 'Amazon EC2 Auto Scaling groups' throughout the document for consistency and full service name accuracy. Changed 'ELB' to 'Elastic Load Balancing' for expanded terminology.
Security assessment
The changes are purely terminological updates to use full service names (Amazon EC2 Auto Scaling groups instead of Auto Scaling groups, ELB to Elastic Load Balancing). There is no indication of addressing security vulnerabilities or adding security-related content. The modifications improve clarity but don't impact security configurations or address security risks.
Diff
diff --git a/AWSCloudFormation/latest/UserGuide/updating.stacks.walkthrough.md b/AWSCloudFormation/latest/UserGuide/updating.stacks.walkthrough.md index 90cd546c7..ca8466bbf 100644 --- a//AWSCloudFormation/latest/UserGuide/updating.stacks.walkthrough.md +++ b//AWSCloudFormation/latest/UserGuide/updating.stacks.walkthrough.md @@ -416 +416 @@ To complete the stack, the template creates an Amazon EC2 security group. -This example uses a single Amazon EC2 instance, but you can use the same mechanisms on more complex solutions that make use of Elastic Load Balancing and Amazon EC2 Auto Scaling groups to manage a collection of application servers. There are, however, some special considerations for Auto Scaling groups. For more information, see Updating Auto Scaling groups. +This example uses a single Amazon EC2 instance, but you can use the same mechanisms on more complex solutions that make use of ELB and Amazon EC2 Auto Scaling groups to manage a collection of application servers. There are, however, some special considerations for Amazon EC2 Auto Scaling groups. For more information, see Updating Amazon EC2 Auto Scaling groups. @@ -565 +565 @@ You can optionally specify a version string for a package. If you change the ver -### Updating Auto Scaling groups +### Updating Amazon EC2 Auto Scaling groups @@ -567 +567 @@ You can optionally specify a version string for a package. If you change the ver -If you are using Auto Scaling groups in your template, as opposed to Amazon EC2 instance resources, updating the application will work in exactly the same way; however, CloudFormation doesn't provide any synchronization or serialization across the Amazon EC2 instances in an Auto Scaling group. The cfn-hup daemon on each host will run independently and update the application on its own schedule. When you use cfn-hup to update the on-instance configuration, each instance will run the cfn-hup hooks on its own schedule; there is no coordination between the instances in the stack. You should consider the following: +If you are using Amazon EC2 Auto Scaling groups in your template, as opposed to Amazon EC2 instance resources, updating the application will work in exactly the same way; however, CloudFormation doesn't provide any synchronization or serialization across the Amazon EC2 instances in an Amazon EC2 Auto Scaling group. The cfn-hup daemon on each host will run independently and update the application on its own schedule. When you use cfn-hup to update the on-instance configuration, each instance will run the cfn-hup hooks on its own schedule; there is no coordination between the instances in the stack. You should consider the following: @@ -569 +569 @@ If you are using Auto Scaling groups in your template, as opposed to Amazon EC2 - * If the cfn-hup changes run on all Amazon EC2 instances in the Auto Scaling group at the same time, your service might be unavailable during the update. + * If the cfn-hup changes run on all Amazon EC2 instances in the Amazon EC2 Auto Scaling group at the same time, your service might be unavailable during the update. @@ -576 +576 @@ If you are using Auto Scaling groups in your template, as opposed to Amazon EC2 -To avoid these issues, consider forcing a rolling update on your instances in the Auto Scaling group. For more information, see [UpdatePolicy attribute](https://docs.aws.amazon.com/AWSCloudFormation/latest/TemplateReference/aws-attribute-updatepolicy.html). +To avoid these issues, consider forcing a rolling update on your instances in the Amazon EC2 Auto Scaling group. For more information, see [UpdatePolicy attribute](https://docs.aws.amazon.com/AWSCloudFormation/latest/TemplateReference/aws-attribute-updatepolicy.html). @@ -716 +716 @@ When you update the stack, CloudFormation detects that the AMI ID has changed, a -### Update the Amazon EC2 launch configuration for an Auto Scaling group +### Update the Amazon EC2 launch configuration for an Amazon EC2 Auto Scaling group @@ -718 +718 @@ When you update the stack, CloudFormation detects that the AMI ID has changed, a -If you are using Auto Scaling groups rather than Amazon EC2 instances, the process of updating the running instances is a little different. With Auto Scaling resources, the configuration of the Amazon EC2 instances, such as the instance type or the AMI ID is encapsulated in the Auto Scaling launch configuration. You can make changes to the launch configuration in the same way as we made changes to the Amazon EC2 instance resources in the previous sections. However, changing the launch configuration doesn't impact any of the running Amazon EC2 instances in the Auto Scaling group. An updated launch configuration applies only to new instances that are created after the update. +If you are using Amazon EC2 Auto Scaling groups rather than Amazon EC2 instances, the process of updating the running instances is a little different. With Amazon EC2 Auto Scaling resources, the configuration of the Amazon EC2 instances, such as the instance type or the AMI ID is encapsulated in the Amazon EC2 Auto Scaling launch configuration. You can make changes to the launch configuration in the same way as we made changes to the Amazon EC2 instance resources in the previous sections. However, changing the launch configuration doesn't impact any of the running Amazon EC2 instances in the Amazon EC2 Auto Scaling group. An updated launch configuration applies only to new instances that are created after the update. @@ -720 +720 @@ If you are using Auto Scaling groups rather than Amazon EC2 instances, the proce -If you want to propagate the change to your launch configuration across all the instances in your Auto Scaling group, you can use an update attribute. For more information, see [UpdatePolicy attribute](https://docs.aws.amazon.com/AWSCloudFormation/latest/TemplateReference/aws-attribute-updatepolicy.html). +If you want to propagate the change to your launch configuration across all the instances in your Amazon EC2 Auto Scaling group, you can use an update attribute. For more information, see [UpdatePolicy attribute](https://docs.aws.amazon.com/AWSCloudFormation/latest/TemplateReference/aws-attribute-updatepolicy.html). @@ -815 +815 @@ This will create a simple, single instance PHP application using an Elastic IP a - 2. Convert the EC2 instance in the template into an Auto Scaling Launch Configuration. The properties are identical, so we only need to change the type name from: + 2. Convert the EC2 instance in the template into an Amazon EC2 Auto Scaling Launch Configuration. The properties are identical, so we only need to change the type name from: @@ -825 +825 @@ to: -For clarity in the template, we changed the name of the resource from _WebServerInstance_ to _LaunchConfig_ , so you'll need to update the resource name referenced by cfn-init and cfn-hup (just search for WebServerInstance and replace it with LaunchConfig, except for cfn-signal). For cfn-signal, you'll need to signal the Auto Scaling group (WebServerGroup) not the instance, as shown in the following snippet: +For clarity in the template, we changed the name of the resource from _WebServerInstance_ to _LaunchConfig_ , so you'll need to update the resource name referenced by cfn-init and cfn-hup (just search for WebServerInstance and replace it with LaunchConfig, except for cfn-signal). For cfn-signal, you'll need to signal the Amazon EC2 Auto Scaling group (WebServerGroup) not the instance, as shown in the following snippet: @@ -833 +833 @@ For clarity in the template, we changed the name of the resource from _WebServer - 3. Add an Auto Scaling group resource. + 3. Add an Amazon EC2 Auto Scaling group resource.