AWS autoscaling documentation change
Summary
Updated terminology from 'Auto Scaling group' to 'Amazon EC2 Auto Scaling group' throughout the document for consistency and branding accuracy.
Security assessment
The changes are purely terminological, replacing 'Auto Scaling group' with the more precise 'Amazon EC2 Auto Scaling group' to align with AWS branding. There is no indication of security vulnerability fixes, mitigation guidance, or new security features being documented. The content focuses on operational procedures for instance refreshes without introducing security-related concepts.
Diff
diff --git a/autoscaling/ec2/userguide/start-instance-refresh.md b/autoscaling/ec2/userguide/start-instance-refresh.md index f9d568a60..e410f3a7c 100644 --- a//autoscaling/ec2/userguide/start-instance-refresh.md +++ b//autoscaling/ec2/userguide/start-instance-refresh.md @@ -11 +11 @@ Start an instance refresh (console)Start an instance refresh (AWS CLI) -You can roll back an instance refresh that is in progress to undo any changes. For this to work, the Auto Scaling group must meet the prerequisites for using rollbacks before starting the instance refresh. For more information, see [Undo changes with a manual or auto rollback](./instance-refresh-rollback.html). +You can roll back an instance refresh that is in progress to undo any changes. For this to work, the Amazon EC2 Auto Scaling group must meet the prerequisites for using rollbacks before starting the instance refresh. For more information, see [Undo changes with a manual or auto rollback](./instance-refresh-rollback.html). @@ -19 +19 @@ If this is your first time starting an instance refresh, using the console will -Use the following procedure if you have not previously defined a [mixed instances policy](./ec2-auto-scaling-mixed-instances-groups.html) for your Auto Scaling group. If you have previously defined a mixed instances policy, see Start an instance refresh in the console (mixed instances group) to start an instance refresh. +Use the following procedure if you have not previously defined a [mixed instances policy](./ec2-auto-scaling-mixed-instances-groups.html) for your Amazon EC2 Auto Scaling group. If you have previously defined a mixed instances policy, see Start an instance refresh in the console (mixed instances group) to start an instance refresh. @@ -23 +23 @@ Use the following procedure if you have not previously defined a [mixed instance - 1. Open the Amazon EC2 console at [https://console.aws.amazon.com/ec2/](https://console.aws.amazon.com/ec2/), and choose **Auto Scaling Groups** from the navigation pane. + 1. Open the Amazon EC2 console at [https://console.aws.amazon.com/ec2/](https://console.aws.amazon.com/ec2/), and choose **Amazon EC2 Auto Scaling Groups** from the navigation pane. @@ -25 +25 @@ Use the following procedure if you have not previously defined a [mixed instance - 2. Select the check box next to your Auto Scaling group. + 2. Select the check box next to your Amazon EC2 Auto Scaling group. @@ -35 +35 @@ A split pane opens up at the bottom of the **Auto Scaling groups** page. - * If you _haven't_ set an instance maintenance policy on the Auto Scaling group, the default setting for **Instance replacement method** is **Terminate and launch**. This is the legacy default behavior for an instance refresh. + * If you _haven't_ set an instance maintenance policy on the Amazon EC2 Auto Scaling group, the default setting for **Instance replacement method** is **Terminate and launch**. This is the legacy default behavior for an instance refresh. @@ -37 +37 @@ A split pane opens up at the bottom of the **Auto Scaling groups** page. - * If you set an instance maintenance policy on the Auto Scaling group, it provides default values for **Instance replacement method**. To override the instance maintenance policy, choose **Override**. Overriding only applies to the current instance refresh. The next time you start an instance refresh, these values are reset to the instance maintenance policy defaults. + * If you set an instance maintenance policy on the Amazon EC2 Auto Scaling group, it provides default values for **Instance replacement method**. To override the instance maintenance policy, choose **Override**. Overriding only applies to the current instance refresh. The next time you start an instance refresh, these values are reset to the instance maintenance policy defaults. @@ -59 +59 @@ The following procedure explains how to update the instance replacement method. -Keeping the default **Violate min healthy percentage** option is not recommended for very small groups. If there is only one instance in the Auto Scaling group, starting an instance refresh can result in an outage. +Keeping the default **Violate min healthy percentage** option is not recommended for very small groups. If there is only one instance in the Amazon EC2 Auto Scaling group, starting an instance refresh can result in an outage. @@ -61 +61 @@ Keeping the default **Violate min healthy percentage** option is not recommended -This step configures fallback behavior if you are using an Auto Scaling group that doesn't have an instance maintenance policy yet. This option isn't available and doesn't appear when your group has an instance maintenance policy. This option is also only available for the **Terminate and launch** replacement method. Other replacement methods will violate the maximum healthy percentage in order to prioritize availability. +This step configures fallback behavior if you are using an Amazon EC2 Auto Scaling group that doesn't have an instance maintenance policy yet. This option isn't available and doesn't appear when your group has an instance maintenance policy. This option is also only available for the **Terminate and launch** replacement method. Other replacement methods will violate the maximum healthy percentage in order to prioritize availability. @@ -65 +65 @@ This step configures fallback behavior if you are using an Auto Scaling group th -While warming up, a newly launched instance is also not counted toward the aggregated instance metrics of the Auto Scaling group (such as `CPUUtilization`, `NetworkIn`, and `NetworkOut`). If you added scaling policies to the Auto Scaling group, the scaling activities run in parallel. If you set a long interval for the instance refresh warmup period, it takes more time for newly launched instances to show up in the metrics. Therefore, an adequate warmup period keeps Amazon EC2 Auto Scaling from scaling on stale metric data. +While warming up, a newly launched instance is also not counted toward the aggregated instance metrics of the Amazon EC2 Auto Scaling group (such as `CPUUtilization`, `NetworkIn`, and `NetworkOut`). If you added scaling policies to the Amazon EC2 Auto Scaling group, the scaling activities run in parallel. If you set a long interval for the instance refresh warmup period, it takes more time for newly launched instances to show up in the metrics. Therefore, an adequate warmup period keeps Amazon EC2 Auto Scaling from scaling on stale metric data. @@ -67 +67 @@ While warming up, a newly launched instance is also not counted toward the aggre -If you have already correctly defined a default instance warmup for the Auto Scaling group, then you don't need to change the instance warmup. However, if you want to override the default, you can set a value for this option. For more information about setting the default instance warmup, see [Set the default instance warmup for an Auto Scaling group](./ec2-auto-scaling-default-instance-warmup.html). +If you have already correctly defined a default instance warmup for the Amazon EC2 Auto Scaling group, then you don't need to change the instance warmup. However, if you want to override the default, you can set a value for this option. For more information about setting the default instance warmup, see [Set the default instance warmup for an Amazon EC2 Auto Scaling group](./ec2-auto-scaling-default-instance-warmup.html). @@ -87 +87 @@ When you enable skip matching, you can set a new launch template or a new versio -To use the skip matching feature to update an Auto Scaling group that currently uses a launch configuration, you must select a launch template in **Desired configuration**. Skip matching with a launch configuration is not supported. +To use the skip matching feature to update an Amazon EC2 Auto Scaling group that currently uses a launch configuration, you must select a launch template in **Desired configuration**. Skip matching with a launch configuration is not supported. @@ -89 +89 @@ To use the skip matching feature to update an Auto Scaling group that currently - 4. For **Standby instances** , choose **Ignore** , **Terminate** , or **Wait**. This determines what happens if instances are found in `Standby` state. For more information, see [Temporarily remove instances from your Auto Scaling group](./as-enter-exit-standby.html). + 4. For **Standby instances** , choose **Ignore** , **Terminate** , or **Wait**. This determines what happens if instances are found in `Standby` state. For more information, see [Temporarily remove instances from your Amazon EC2 Auto Scaling group](./as-enter-exit-standby.html). @@ -99 +99 @@ If you choose **Wait** , you must take additional steps to remove scale-in prote - 7. (Optional) Expand the **Desired configuration** section to specify updates that you want to make to your Auto Scaling group. + 7. (Optional) Expand the **Desired configuration** section to specify updates that you want to make to your Amazon EC2 Auto Scaling group. @@ -105 +105 @@ For this step, you can choose to use JSON or YAML syntax to edit parameter value - * If you _haven't_ created a new launch template or a new launch template version for your Auto Scaling group, don't select this check box. + * If you _haven't_ created a new launch template or a new launch template version for your Amazon EC2 Auto Scaling group, don't select this check box. @@ -115 +115 @@ After you choose a version, you can see the version information. This is the ver - * Select this check box if you want to override the instance type in the launch template or run Spot Instances. You can either manually add each instance type or choose a primary instance type and recommendation option that retrieves any additional matching instance types for you. If you plan to launch Spot Instances, we recommend adding a few different instance types. This way, Amazon EC2 Auto Scaling can launch another instance type if there is insufficient instance capacity in your chosen Availability Zones. For more information, see [Auto Scaling groups with multiple instance types and purchase options](./ec2-auto-scaling-mixed-instances-groups.html). + * Select this check box if you want to override the instance type in the launch template or run Spot Instances. You can either manually add each instance type or choose a primary instance type and recommendation option that retrieves any additional matching instance types for you. If you plan to launch Spot Instances, we recommend adding a few different instance types. This way, Amazon EC2 Auto Scaling can launch another instance type if there is insufficient instance capacity in your chosen Availability Zones. For more information, see [Amazon EC2 Auto Scaling groups with multiple instance types and purchase options](./ec2-auto-scaling-mixed-instances-groups.html). @@ -121 +121 @@ Don't use Spot Instances with applications that can't handle a Spot Instance int -If you select this check box, make sure that the launch template doesn't already request Spot Instances. You can't use a launch template that requests Spot Instances to create an Auto Scaling group that uses multiple instance types and launches Spot and On-Demand Instances. +If you select this check box, make sure that the launch template doesn't already request Spot Instances. You can't use a launch template that requests Spot Instances to create an Amazon EC2 Auto Scaling group that uses multiple instance types and launches Spot and On-Demand Instances. @@ -125 +125 @@ If you select this check box, make sure that the launch template doesn't already -To configure these options on an Auto Scaling group that currently uses a launch configuration, you must select a launch template in **Update launch template**. Overriding the instance type in your launch configuration is not supported. +To configure these options on an Amazon EC2 Auto Scaling group that currently uses a launch configuration, you must select a launch template in **Update launch template**. Overriding the instance type in your launch configuration is not supported. @@ -129 +129 @@ To configure these options on an Auto Scaling group that currently uses a launch -This setting can only be enabled when the Auto Scaling group meets the prerequisites for using rollbacks. +This setting can only be enabled when the Amazon EC2 Auto Scaling group meets the prerequisites for using rollbacks. @@ -142 +142 @@ At this point, it's a good idea to verify that the differences between the curre -Use the following procedure if you have created an Auto Scaling group with a [mixed instances policy](./ec2-auto-scaling-mixed-instances-groups.html). If you haven't defined a mixed instances policy for your group yet, see Start an instance refresh in the console (basic procedure) to start an instance refresh. +Use the following procedure if you have created an Amazon EC2 Auto Scaling group with a [mixed instances policy](./ec2-auto-scaling-mixed-instances-groups.html). If you haven't defined a mixed instances policy for your group yet, see Start an instance refresh in the console (basic procedure) to start an instance refresh. @@ -146 +146 @@ Use the following procedure if you have created an Auto Scaling group with a [mi - 1. Open the Amazon EC2 console at [https://console.aws.amazon.com/ec2/](https://console.aws.amazon.com/ec2/), and choose **Auto Scaling Groups** from the navigation pane. + 1. Open the Amazon EC2 console at [https://console.aws.amazon.com/ec2/](https://console.aws.amazon.com/ec2/), and choose **Amazon EC2 Auto Scaling Groups** from the navigation pane. @@ -148 +148 @@ Use the following procedure if you have created an Auto Scaling group with a [mi - 2. Select the check box next to your Auto Scaling group. + 2. Select the check box next to your Amazon EC2 Auto Scaling group. @@ -158 +158 @@ A split pane opens up at the bottom of the **Auto Scaling groups** page. - * If you _haven't_ set an instance maintenance policy on the Auto Scaling group, the default setting for **Instance replacement method** is **Terminate and launch**. This is the legacy default behavior for an instance refresh. + * If you _haven't_ set an instance maintenance policy on the Amazon EC2 Auto Scaling group, the default setting for **Instance replacement method** is **Terminate and launch**. This is the legacy default behavior for an instance refresh. @@ -160 +160 @@ A split pane opens up at the bottom of the **Auto Scaling groups** page. - * If you set an instance maintenance policy on the Auto Scaling group, it provides default values for **Instance replacement method**. To override the instance maintenance policy, choose **Override**. Overriding only applies to the current instance refresh. The next time you start an instance refresh, these values are reset to the instance maintenance policy defaults. + * If you set an instance maintenance policy on the Amazon EC2 Auto Scaling group, it provides default values for **Instance replacement method**. To override the instance maintenance policy, choose **Override**. Overriding only applies to the current instance refresh. The next time you start an instance refresh, these values are reset to the instance maintenance policy defaults. @@ -182 +182 @@ The following procedure explains how to update the instance replacement method. -Keeping the default **Violate min healthy percentage** option is not recommended for very small groups. If there is only one instance in the Auto Scaling group, starting an instance refresh can result in an outage. +Keeping the default **Violate min healthy percentage** option is not recommended for very small groups. If there is only one instance in the Amazon EC2 Auto Scaling group, starting an instance refresh can result in an outage. @@ -184 +184 @@ Keeping the default **Violate min healthy percentage** option is not recommended -This step configures fallback behavior if you are using an Auto Scaling group that doesn't have an instance maintenance policy yet. This option isn't available and doesn't appear when your group has an instance maintenance policy. This option is also only available for the **Terminate and launch** replacement method. Other replacement methods will violate the maximum healthy percentage in order to prioritize availability. +This step configures fallback behavior if you are using an Amazon EC2 Auto Scaling group that doesn't have an instance maintenance policy yet. This option isn't available and doesn't appear when your group has an instance maintenance policy. This option is also only available for the **Terminate and launch** replacement method. Other replacement methods will violate the maximum healthy percentage in order to prioritize availability. @@ -188 +188 @@ This step configures fallback behavior if you are using an Auto Scaling group th -While warming up, a newly launched instance is also not counted toward the aggregated instance metrics of the Auto Scaling group (such as `CPUUtilization`, `NetworkIn`, and `NetworkOut`). If you added scaling policies to the Auto Scaling group, the scaling activities run in parallel. If you set a long interval for the instance refresh warmup period, it takes more time for newly launched instances to show up in the metrics. Therefore, an adequate warmup period keeps Amazon EC2 Auto Scaling from scaling on stale metric data. +While warming up, a newly launched instance is also not counted toward the aggregated instance metrics of the Amazon EC2 Auto Scaling group (such as `CPUUtilization`, `NetworkIn`, and `NetworkOut`). If you added scaling policies to the Amazon EC2 Auto Scaling group, the scaling activities run in parallel. If you set a long interval for the instance refresh warmup period, it takes more time for newly launched instances to show up in the metrics. Therefore, an adequate warmup period keeps Amazon EC2 Auto Scaling from scaling on stale metric data. @@ -190 +190 @@ While warming up, a newly launched instance is also not counted toward the aggre -If you have already correctly defined a default instance warmup for the Auto Scaling group, then you don't need to change the instance warmup. However, if you want to override the default, you can set a value for this option. For more information about setting the default instance warmup, see [Set the default instance warmup for an Auto Scaling group](./ec2-auto-scaling-default-instance-warmup.html). +If you have already correctly defined a default instance warmup for the Amazon EC2 Auto Scaling group, then you don't need to change the instance warmup. However, if you want to override the default, you can set a value for this option. For more information about setting the default instance warmup, see [Set the default instance warmup for an Amazon EC2 Auto Scaling group](./ec2-auto-scaling-default-instance-warmup.html). @@ -206 +206 @@ When you enable skip matching, you can set a new launch template or a new versio - 3. For **Standby instances** , choose **Ignore** , **Terminate** , or **Wait**. This determines what happens if instances are found in `Standby` state. For more information, see [Temporarily remove instances from your Auto Scaling group](./as-enter-exit-standby.html). + 3. For **Standby instances** , choose **Ignore** , **Terminate** , or **Wait**. This determines what happens if instances are found in `Standby` state. For more information, see [Temporarily remove instances from your Amazon EC2 Auto Scaling group](./as-enter-exit-standby.html). @@ -222 +222 @@ For this step, you can choose to use JSON or YAML syntax to edit parameter value - * If you _haven't_ created a new launch template or a new launch template version for your Auto Scaling group, don't select this check box. + * If you _haven't_ created a new launch template or a new launch template version for your Amazon EC2 Auto Scaling group, don't select this check box. @@ -230 +230 @@ After you choose a version, you can see the version information. This is the ver -By default, this check box is selected. Amazon EC2 Auto Scaling populates each parameter with the value that's currently set in the _mixed instances policy_ for the Auto Scaling group. Only update values for the parameters that you want to change. For guidance on these settings, see [Auto Scaling groups with multiple instance types and purchase options](./ec2-auto-scaling-mixed-instances-groups.html). +By default, this check box is selected. Amazon EC2 Auto Scaling populates each parameter with the value that's currently set in the _mixed instances policy_ for the Amazon EC2 Auto Scaling group. Only update values for the parameters that you want to change. For guidance on these settings, see [Amazon EC2 Auto Scaling groups with multiple instance types and purchase options](./ec2-auto-scaling-mixed-instances-groups.html). @@ -238 +238 @@ We recommend that you do not clear this check box. Only clear it if you want to -This setting can only be enabled when the Auto Scaling group meets the prerequisites for using rollbacks. +This setting can only be enabled when the Amazon EC2 Auto Scaling group meets the prerequisites for using rollbacks.