AWS autoscaling documentation change
Summary
Updated documentation to consistently use 'Amazon EC2 Auto Scaling group' terminology instead of 'Auto Scaling group' throughout the file
Security assessment
The changes are purely terminological updates to use the full product name. No security-related content was added, removed, or modified beyond terminology. The security group configuration guidance and default security group behavior descriptions remain unchanged except for product name updates.
Diff
diff --git a/autoscaling/ec2/userguide/create-launch-template.md b/autoscaling/ec2/userguide/create-launch-template.md index bc26821ea..a6a7f392f 100644 --- a//autoscaling/ec2/userguide/create-launch-template.md +++ b//autoscaling/ec2/userguide/create-launch-template.md @@ -7 +7 @@ Create your launch template (console)Change the default network interface settin -# Create a launch template for an Auto Scaling group +# Create a launch template for an Amazon EC2 Auto Scaling group @@ -9 +9 @@ Create your launch template (console)Change the default network interface settin -Before you can create an Auto Scaling group using a launch template, you must create a launch template that contains the configuration information to launch an instance, including the ID of the Amazon Machine Image (AMI). +Before you can create an Amazon EC2 Auto Scaling group using a launch template, you must create a launch template that contains the configuration information to launch an instance, including the ID of the Amazon Machine Image (AMI). @@ -87 +87 @@ Alternatively, to use attribute-based instance type selection, choose **Advanced -If you don't specify any security groups in your launch template, Amazon EC2 uses the default security group for the VPC that your Auto Scaling group will launch instances into. By default, this security group doesn't allow inbound traffic from external networks. For more information, see [Default security groups for your VPCs](https://docs.aws.amazon.com/vpc/latest/userguide/default-security-group.html) in the _Amazon VPC User Guide_. +If you don't specify any security groups in your launch template, Amazon EC2 uses the default security group for the VPC that your Amazon EC2 Auto Scaling group will launch instances into. By default, this security group doesn't allow inbound traffic from external networks. For more information, see [Default security groups for your VPCs](https://docs.aws.amazon.com/vpc/latest/userguide/default-security-group.html) in the _Amazon VPC User Guide_. @@ -101 +101 @@ If you don't specify any security groups in your launch template, Amazon EC2 use - 7. For **Resource tags** , specify tags by providing key and value combinations. If you specify instance tags in your launch template and then you choose to propagate your Auto Scaling group's tags to its instances, all the tags are merged. If the same tag key is specified for a tag in your launch template and a tag in your Auto Scaling group, then the tag value from the group takes precedence. + 7. For **Resource tags** , specify tags by providing key and value combinations. If you specify instance tags in your launch template and then you choose to propagate your Amazon EC2 Auto Scaling group's tags to its instances, all the tags are merged. If the same tag key is specified for a tag in your launch template and a tag in your Amazon EC2 Auto Scaling group, then the tag value from the group takes precedence. @@ -107 +107 @@ If you don't specify any security groups in your launch template, Amazon EC2 use - 8. To create an Auto Scaling group, choose **Create Auto Scaling group** from the confirmation page. + 8. To create an Amazon EC2 Auto Scaling group, choose **Create Auto Scaling group** from the confirmation page. @@ -114 +114 @@ If you don't specify any security groups in your launch template, Amazon EC2 use -Network interfaces provide connectivity to other resources in your VPC and the internet. For more information, see [Provide network connectivity for your Auto Scaling instances using Amazon VPC](./asg-in-vpc.html). +Network interfaces provide connectivity to other resources in your VPC and the internet. For more information, see [Provide network connectivity for your Amazon EC2 Auto Scaling instances using Amazon VPC](./asg-in-vpc.html). @@ -124 +124 @@ When changing the default network interface settings, keep in mind the following - * If you specify an existing network interface ID, you can launch only one instance. To do this, you must use the AWS CLI or an SDK to create the Auto Scaling group. When you create the group, you must specify the Availability Zone, but not the subnet ID. Also, you can specify an existing network interface only if it has a device index of 0. + * If you specify an existing network interface ID, you can launch only one instance. To do this, you must use the AWS CLI or an SDK to create the Amazon EC2 Auto Scaling group. When you create the group, you must specify the Availability Zone, but not the subnet ID. Also, you can specify an existing network interface only if it has a device index of 0. @@ -141 +141 @@ When changing the default network interface settings, keep in mind the following - 2. **Network interface** : Keep the default value, **New interface** , to have Amazon EC2 Auto Scaling automatically create a new network interface when an instance is launched. Alternatively, you can choose an existing, available network interface with a device index of 0, but this limits your Auto Scaling group to one instance. + 2. **Network interface** : Keep the default value, **New interface** , to have Amazon EC2 Auto Scaling automatically create a new network interface when an instance is launched. Alternatively, you can choose an existing, available network interface with a device index of 0, but this limits your Amazon EC2 Auto Scaling group to one instance. @@ -147 +147 @@ When changing the default network interface settings, keep in mind the following -If the AMI specifies a subnet for the network interface, this results in an error. We recommend turning off **Auto Scaling guidance** as a workaround. After you make this change, you will not receive an error message. However, regardless of where the subnet is specified, the subnet settings of the Auto Scaling group take precedence and cannot be overridden. +If the AMI specifies a subnet for the network interface, this results in an error. We recommend turning off **Auto Scaling guidance** as a workaround. After you make this change, you will not receive an error message. However, regardless of where the subnet is specified, the subnet settings of the Amazon EC2 Auto Scaling group take precedence and cannot be overridden. @@ -151 +151 @@ If the AMI specifies a subnet for the network interface, this results in an erro - 6. **Security groups** : Choose one or more security groups for the network interface. Each security group must be configured for the VPC that your Auto Scaling group will launch instances into. For more information, see [Amazon EC2 security groups for Linux instances](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-security-groups.html) in the _Amazon EC2 User Guide_. + 6. **Security groups** : Choose one or more security groups for the network interface. Each security group must be configured for the VPC that your Amazon EC2 Auto Scaling group will launch instances into. For more information, see [Amazon EC2 security groups for Linux instances](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-security-groups.html) in the _Amazon EC2 User Guide_. @@ -240 +240 @@ Encrypted snapshot that is shared with you | Encrypted by default KMS key - 7. To create an Auto Scaling group, choose **Create Auto Scaling group** from the confirmation page. + 7. To create an Amazon EC2 Auto Scaling group, choose **Create Auto Scaling group** from the confirmation page. @@ -253 +253 @@ For more information about launch templates, see [Launching an instance from a l - * While you can specify a subnet in a launch template, doing so isn't necessary if you only use the launch template to create Auto Scaling groups. You can't specify the subnet for an Auto Scaling group by specifying the subnet in a launch template. The subnets for the Auto Scaling group are taken from the Auto Scaling group's own resource definition. + * While you can specify a subnet in a launch template, doing so isn't necessary if you only use the launch template to create Amazon EC2 Auto Scaling groups. You can't specify the subnet for an Amazon EC2 Auto Scaling group by specifying the subnet in a launch template. The subnets for the Amazon EC2 Auto Scaling group are taken from the Amazon EC2 Auto Scaling group's own resource definition.