AWS autoscaling documentation change
Summary
Updated terminology from 'Auto Scaling group' to 'Amazon EC2 Auto Scaling group' throughout the document for consistency and full service name accuracy
Security assessment
The changes are purely terminological updates to use the full service name ('Amazon EC2 Auto Scaling group') rather than the abbreviated form. There is no evidence of security vulnerability fixes, security incident references, or new security guidance. The modifications maintain existing security-related content (like key policy configurations) but only update naming conventions.
Diff
diff --git a/autoscaling/ec2/userguide/ts-as-instancelaunchfailure.md b/autoscaling/ec2/userguide/ts-as-instancelaunchfailure.md index d8d8f3e9d..6111d8e40 100644 --- a//autoscaling/ec2/userguide/ts-as-instancelaunchfailure.md +++ b//autoscaling/ec2/userguide/ts-as-instancelaunchfailure.md @@ -79 +79 @@ For further guidance to resolve this issue, check the following: - 4. Update your Auto Scaling group with the new launch template or launch configuration using the [update-auto-scaling-group](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/autoscaling/update-auto-scaling-group.html) command. + 4. Update your Amazon EC2 Auto Scaling group with the new launch template or launch configuration using the [update-auto-scaling-group](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/autoscaling/update-auto-scaling-group.html) command. @@ -96 +96 @@ For further guidance to resolve this issue, check the following: - 4. Update your Auto Scaling group with the new launch template or launch configuration using the [update-auto-scaling-group](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/autoscaling/update-auto-scaling-group.html) command. + 4. Update your Amazon EC2 Auto Scaling group with the new launch template or launch configuration using the [update-auto-scaling-group](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/autoscaling/update-auto-scaling-group.html) command. @@ -105 +105 @@ For further guidance to resolve this issue, check the following: -**Cause** : The Availability Zones specified in your Auto Scaling group don't support your chosen instance type. +**Cause** : The Availability Zones specified in your Amazon EC2 Auto Scaling group don't support your chosen instance type. @@ -111 +111 @@ For further guidance to resolve this issue, check the following: - 2. Update or remove the subnet for any unsupported zones in the settings of your Auto Scaling group using the [update-auto-scaling-group](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/autoscaling/update-auto-scaling-group.html) command. For more information, see [Add an Availability Zone](./as-add-az-console.html). + 2. Update or remove the subnet for any unsupported zones in the settings of your Amazon EC2 Auto Scaling group using the [update-auto-scaling-group](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/autoscaling/update-auto-scaling-group.html) command. For more information, see [Add an Availability Zone](./as-add-az-console.html). @@ -130 +130 @@ For further guidance to resolve this issue, check the following: - 2. Manually create an Amazon EC2 instance that is not part of the Auto Scaling group and investigate the problem. If the block device naming configuration conflicts with the names in the Amazon Machine Image (AMI), the instance will fail during launch. For more information, see [Block device mappings](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/block-device-mapping-concepts.html) in the _Amazon EC2 User Guide_. + 2. Manually create an Amazon EC2 instance that is not part of the Amazon EC2 Auto Scaling group and investigate the problem. If the block device naming configuration conflicts with the names in the Amazon Machine Image (AMI), the instance will fail during launch. For more information, see [Block device mappings](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/block-device-mapping-concepts.html) in the _Amazon EC2 User Guide_. @@ -136 +136 @@ For further guidance to resolve this issue, check the following: - 5. Update your Auto Scaling group with the new launch template or launch configuration using the [update-auto-scaling-group](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/autoscaling/update-auto-scaling-group.html) command. + 5. Update your Amazon EC2 Auto Scaling group with the new launch template or launch configuration using the [update-auto-scaling-group](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/autoscaling/update-auto-scaling-group.html) command. @@ -149 +149 @@ For further guidance to resolve this issue, check the following: - 2. Update your Auto Scaling group with the new launch template or launch configuration using the [update-auto-scaling-group](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/autoscaling/update-auto-scaling-group.html) command. + 2. Update your Amazon EC2 Auto Scaling group with the new launch template or launch configuration using the [update-auto-scaling-group](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/autoscaling/update-auto-scaling-group.html) command. @@ -162 +162 @@ For further guidance to resolve this issue, check the following: - 2. Update your Auto Scaling group with the new launch template or launch configuration using the [update-auto-scaling-group](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/autoscaling/update-auto-scaling-group.html) command. + 2. Update your Amazon EC2 Auto Scaling group with the new launch template or launch configuration using the [update-auto-scaling-group](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/autoscaling/update-auto-scaling-group.html) command. @@ -179 +179 @@ For further guidance to resolve this issue, check the following: - 4. Update your Auto Scaling group with a new placement group, launch template, or launch configuration using the [update-auto-scaling-group](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/autoscaling/update-auto-scaling-group.html) command. + 4. Update your Amazon EC2 Auto Scaling group with a new placement group, launch template, or launch configuration using the [update-auto-scaling-group](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/autoscaling/update-auto-scaling-group.html) command. @@ -192 +192 @@ For further guidance to resolve this issue, check the following: - 1. Determine which service-linked role to use for this Auto Scaling group. + 1. Determine which service-linked role to use for this Amazon EC2 Auto Scaling group. @@ -196 +196 @@ For further guidance to resolve this issue, check the following: - 3. Update the Auto Scaling group to use the service-linked role. + 3. Update the Amazon EC2 Auto Scaling group to use the service-linked role. @@ -203 +203 @@ For an example of a key policy that lets the service-linked role use the custome -**Cause 2** : If the customer managed key and Auto Scaling group are in _different_ AWS accounts, you need to configure cross-account access to the customer managed key in order to give permission to use the customer managed key to the proper service-linked role. +**Cause 2** : If the customer managed key and Amazon EC2 Auto Scaling group are in _different_ AWS accounts, you need to configure cross-account access to the customer managed key in order to give permission to use the customer managed key to the proper service-linked role. @@ -207 +207 @@ For an example of a key policy that lets the service-linked role use the custome - 1. Update the key policy on the customer managed key to allow the Auto Scaling group account access to the customer managed key. + 1. Update the key policy on the customer managed key to allow the Amazon EC2 Auto Scaling group account access to the customer managed key. @@ -209 +209 @@ For an example of a key policy that lets the service-linked role use the custome - 2. Define an IAM user or role in the Auto Scaling group account that can create a grant. + 2. Define an IAM user or role in the Amazon EC2 Auto Scaling group account that can create a grant. @@ -211 +211 @@ For an example of a key policy that lets the service-linked role use the custome - 3. Determine which service-linked role to use for this Auto Scaling group. + 3. Determine which service-linked role to use for this Amazon EC2 Auto Scaling group. @@ -215 +215 @@ For an example of a key policy that lets the service-linked role use the custome - 5. Update the Auto Scaling group to use the service-linked role. + 5. Update the Amazon EC2 Auto Scaling group to use the service-linked role. @@ -222 +222 @@ For more information, see [Example 2: Key policy sections that allow cross-accou -**Solution 3** : Use a customer managed key in the same AWS account as the Auto Scaling group. +**Solution 3** : Use a customer managed key in the same AWS account as the Amazon EC2 Auto Scaling group. @@ -224 +224 @@ For more information, see [Example 2: Key policy sections that allow cross-accou - 1. Copy and re-encrypt the snapshot with another customer managed key that belongs to the same account as the Auto Scaling group. + 1. Copy and re-encrypt the snapshot with another customer managed key that belongs to the same account as the Amazon EC2 Auto Scaling group. @@ -241 +241 @@ For more information, see [Example 2: Key policy sections that allow cross-accou - * Expand your Auto Scaling group to additional Availability Zones. For more information, see [Add an Availability Zone](./as-add-az-console.html). + * Expand your Amazon EC2 Auto Scaling group to additional Availability Zones. For more information, see [Add an Availability Zone](./as-add-az-console.html). @@ -243 +243 @@ For more information, see [Example 2: Key policy sections that allow cross-accou - * Follow the best practice of using a diverse set of instance types so that you're not reliant on one specific instance type. For more information, see [Auto Scaling groups with multiple instance types and purchase options](./ec2-auto-scaling-mixed-instances-groups.html). + * Follow the best practice of using a diverse set of instance types so that you're not reliant on one specific instance type. For more information, see [Amazon EC2 Auto Scaling groups with multiple instance types and purchase options](./ec2-auto-scaling-mixed-instances-groups.html). @@ -271 +271 @@ With Capacity Blocks, you are constrained by the amount of capacity originally p -**Solution** : Follow the recommended approach for Capacity Blocks and use scheduled scaling. Doing so helps you make sure you increase the desired capacity of your Auto Scaling group only when the reservation is active and decrease it before the reservation is over. +**Solution** : Follow the recommended approach for Capacity Blocks and use scheduled scaling. Doing so helps you make sure you increase the desired capacity of your Amazon EC2 Auto Scaling group only when the reservation is active and decrease it before the reservation is over. @@ -281 +281 @@ With Capacity Blocks, you are constrained by the amount of capacity originally p - * Expand your Auto Scaling group to additional Availability Zones. For more information, see [Add an Availability Zone](./as-add-az-console.html). + * Expand your Amazon EC2 Auto Scaling group to additional Availability Zones. For more information, see [Add an Availability Zone](./as-add-az-console.html). @@ -283 +283 @@ With Capacity Blocks, you are constrained by the amount of capacity originally p - * Follow the best practice of using a diverse set of instance types so that you're not reliant on one specific instance type. For more information, see [Auto Scaling groups with multiple instance types and purchase options](./ec2-auto-scaling-mixed-instances-groups.html). + * Follow the best practice of using a diverse set of instance types so that you're not reliant on one specific instance type. For more information, see [Amazon EC2 Auto Scaling groups with multiple instance types and purchase options](./ec2-auto-scaling-mixed-instances-groups.html).