AWS autoscaling documentation change
Summary
Updated terminology from 'Auto Scaling group' to 'Amazon EC2 Auto Scaling group' throughout the document for branding consistency. Changed 'Elastic Load Balancing' to 'ELB' abbreviation in one instance.
Security assessment
The changes are purely cosmetic branding updates and terminology standardization. No security vulnerabilities, weaknesses, or incidents are mentioned. The ELB abbreviation change doesn't alter security guidance. No new security features or security-related content was added.
Diff
diff --git a/autoscaling/ec2/userguide/instance-maintenance-policy-overview-and-considerations.md b/autoscaling/ec2/userguide/instance-maintenance-policy-overview-and-considerations.md index d57790fa6..423d557f1 100644 --- a//autoscaling/ec2/userguide/instance-maintenance-policy-overview-and-considerations.md +++ b//autoscaling/ec2/userguide/instance-maintenance-policy-overview-and-considerations.md @@ -5 +5 @@ -OverviewCore conceptsInstance warmupHealth check grace periodScale your Auto Scaling groupExample scenarios +OverviewCore conceptsInstance warmupHealth check grace periodScale your Amazon EC2 Auto Scaling groupExample scenarios @@ -7 +7 @@ OverviewCore conceptsInstance warmupHealth check grace periodScale your Auto Sca -# Instance maintenance policy for Auto Scaling group +# Instance maintenance policy for Amazon EC2 Auto Scaling group @@ -21 +21 @@ This topic provides an overview of the options available and describes what to c - * Scale your Auto Scaling group + * Scale your Amazon EC2 Auto Scaling group @@ -30 +30 @@ This topic provides an overview of the options available and describes what to c -When you create an instance maintenance policy for your Auto Scaling group, the policy affects Amazon EC2 Auto Scaling events that cause instances to be replaced. This results in more consistent replacement behaviors within the same Auto Scaling group. It also lets you optimize your group for availability or cost depending on your needs. +When you create an instance maintenance policy for your Amazon EC2 Auto Scaling group, the policy affects Amazon EC2 Auto Scaling events that cause instances to be replaced. This results in more consistent replacement behaviors within the same Amazon EC2 Auto Scaling group. It also lets you optimize your group for availability or cost depending on your needs. @@ -43 +43 @@ In the console, the following configuration options are available: -The default for an Auto Scaling group is to not have an instance maintenance policy, which causes it to respond to instance maintenance events with the default behaviors. The default behaviors are described in the following table. +The default for an Amazon EC2 Auto Scaling group is to not have an instance maintenance policy, which causes it to respond to instance maintenance events with the default behaviors. The default behaviors are described in the following table. @@ -47,3 +47,3 @@ Instance maintenance event default behaviors Event | Description | Default beh -Health check failure | Happens automatically when instances fail their health checks. Amazon EC2 Auto Scaling replaces instances that fail their health checks. To understand the causes of health check failures, see [Health checks for instances in an Auto Scaling group](./ec2-auto-scaling-health-checks.html). | Terminate and launch. -Instance refresh | Happens when you start an instance refresh. Depending on your configuration, an instance refresh replaces instances one at a time, several at a time, or all at once. For more information, see [Use an instance refresh to update instances in an Auto Scaling group](./asg-instance-refresh.html). | Terminate and launch. -Maximum instance lifetime | Happens automatically when instances reach the maximum instance lifetime that you specify for your Auto Scaling group. Amazon EC2 Auto Scaling replaces instances that reach their maximum instance lifetime. For more information, see [Replace Auto Scaling instances based on maximum instance lifetime](./asg-max-instance-lifetime.html). | Terminate and launch. +Health check failure | Happens automatically when instances fail their health checks. Amazon EC2 Auto Scaling replaces instances that fail their health checks. To understand the causes of health check failures, see [Health checks for instances in an Amazon EC2 Auto Scaling group](./ec2-auto-scaling-health-checks.html). | Terminate and launch. +Instance refresh | Happens when you start an instance refresh. Depending on your configuration, an instance refresh replaces instances one at a time, several at a time, or all at once. For more information, see [Use an instance refresh to update instances in an Amazon EC2 Auto Scaling group](./asg-instance-refresh.html). | Terminate and launch. +Maximum instance lifetime | Happens automatically when instances reach the maximum instance lifetime that you specify for your Amazon EC2 Auto Scaling group. Amazon EC2 Auto Scaling replaces instances that reach their maximum instance lifetime. For more information, see [Replace Amazon EC2 Auto Scaling instances based on maximum instance lifetime](./asg-max-instance-lifetime.html). | Terminate and launch. @@ -52,3 +52,3 @@ Rebalancing | Happens automatically if there are underlying changes that cause - * An Availability Zone that previously had insufficient capacity recovers, or you add or remove an Availability Zone from the group. When this happens, your Auto Scaling group tries to evenly balance itself across Availability Zones. For more information, see [Rebalancing activities](./auto-scaling-benefits.html#AutoScalingBehavior.InstanceUsage). - * You enable Capacity Rebalancing on your Auto Scaling group, and it tries to launch new Spot Instances before existing ones are interrupted as the availability of Spot Instances changes. For more information, see [Capacity Rebalancing in Auto Scaling to replace at-risk Spot Instances](./ec2-auto-scaling-capacity-rebalancing.html). - * You update your Auto Scaling group, and it gradually replaces instances to match the new purchasing options that you chose when updating a mixed instances policy. For more information, see [Update an Auto Scaling group](./update-auto-scaling-group.html). + * An Availability Zone that previously had insufficient capacity recovers, or you add or remove an Availability Zone from the group. When this happens, your Amazon EC2 Auto Scaling group tries to evenly balance itself across Availability Zones. For more information, see [Rebalancing activities](./auto-scaling-benefits.html#AutoScalingBehavior.InstanceUsage). + * You enable Capacity Rebalancing on your Amazon EC2 Auto Scaling group, and it tries to launch new Spot Instances before existing ones are interrupted as the availability of Spot Instances changes. For more information, see [Capacity Rebalancing in Amazon EC2 Auto Scaling to replace at-risk Spot Instances](./ec2-auto-scaling-capacity-rebalancing.html). + * You update your Amazon EC2 Auto Scaling group, and it gradually replaces instances to match the new purchasing options that you chose when updating a mixed instances policy. For more information, see [Update an Amazon EC2 Auto Scaling group](./update-auto-scaling-group.html). @@ -69 +69 @@ Amazon EC2 Auto Scaling will continue to default to terminate and launch in the -With Spot Instances, if you enabled Capacity Rebalancing on your Auto Scaling group, then the instance might already have a pending instance from a different Spot pool that we launched before we initiated the Spot interruption. For details about how Capacity Rebalancing works, see [Capacity Rebalancing in Auto Scaling to replace at-risk Spot Instances](./ec2-auto-scaling-capacity-rebalancing.html). +With Spot Instances, if you enabled Capacity Rebalancing on your Amazon EC2 Auto Scaling group, then the instance might already have a pending instance from a different Spot pool that we launched before we initiated the Spot interruption. For details about how Capacity Rebalancing works, see [Capacity Rebalancing in Amazon EC2 Auto Scaling to replace at-risk Spot Instances](./ec2-auto-scaling-capacity-rebalancing.html). @@ -80 +80 @@ Before you get started, familiarize yourself with the following core concepts an -The _desired capacity_ is the capacity of the Auto Scaling group at the time of creation. It is also the capacity the group attempts to maintain when there are no scaling conditions attached to the group. +The _desired capacity_ is the capacity of the Amazon EC2 Auto Scaling group at the time of creation. It is also the capacity the group attempts to maintain when there are no scaling conditions attached to the group. @@ -85 +85 @@ The _desired capacity_ is the capacity of the Auto Scaling group at the time of -An _instance maintenance policy_ controls whether an instance is provisioned first before an existing instance is terminated for instance maintenance events. It also determines how far below and over your desired capacity your Auto Scaling group might go to replace multiple instances at the same time. +An _instance maintenance policy_ controls whether an instance is provisioned first before an existing instance is terminated for instance maintenance events. It also determines how far below and over your desired capacity your Amazon EC2 Auto Scaling group might go to replace multiple instances at the same time. @@ -90 +90 @@ An _instance maintenance policy_ controls whether an instance is provisioned fir -The _maximum healthy percentage_ is the percentage of its desired capacity that your Auto Scaling group can increase to when replacing instances. It represents the maximum percentage of the group that can be in service and healthy, or pending, to support your workload. In the console, you can set the maximum healthy percentage when you use either the **Launch before terminating** option or the **Custom policy** option. The valid values are 100–200 percent. +The _maximum healthy percentage_ is the percentage of its desired capacity that your Amazon EC2 Auto Scaling group can increase to when replacing instances. It represents the maximum percentage of the group that can be in service and healthy, or pending, to support your workload. In the console, you can set the maximum healthy percentage when you use either the **Launch before terminating** option or the **Custom policy** option. The valid values are 100–200 percent. @@ -103 +103 @@ To replace instances faster, you can specify a low minimum healthy percentage. H -If your instances need time to initialize after they enter the `InService` state, enable the default instance warmup for your Auto Scaling group. With the default instance warmup, you can prevent instances from being counted toward the minimum healthy percentage before they are ready. This ensures that Amazon EC2 Auto Scaling considers how long it takes to have enough capacity in place to support the workload before it terminates existing instances. +If your instances need time to initialize after they enter the `InService` state, enable the default instance warmup for your Amazon EC2 Auto Scaling group. With the default instance warmup, you can prevent instances from being counted toward the minimum healthy percentage before they are ready. This ensures that Amazon EC2 Auto Scaling considers how long it takes to have enough capacity in place to support the workload before it terminates existing instances. @@ -105 +105 @@ If your instances need time to initialize after they enter the `InService` state -As an added benefit, you can improve the Amazon CloudWatch metrics used for dynamic scaling when you enable the default instance warmup. If your Auto Scaling group has any scaling policies, when the group scales out, it uses the same default warmup period to prevent instances from being counted toward CloudWatch metrics before they have finished initializing. +As an added benefit, you can improve the Amazon CloudWatch metrics used for dynamic scaling when you enable the default instance warmup. If your Amazon EC2 Auto Scaling group has any scaling policies, when the group scales out, it uses the same default warmup period to prevent instances from being counted toward CloudWatch metrics before they have finished initializing. @@ -107 +107 @@ As an added benefit, you can improve the Amazon CloudWatch metrics used for dyna -For more information, see [Set the default instance warmup for an Auto Scaling group](./ec2-auto-scaling-default-instance-warmup.html). +For more information, see [Set the default instance warmup for an Amazon EC2 Auto Scaling group](./ec2-auto-scaling-default-instance-warmup.html). @@ -111 +111 @@ For more information, see [Set the default instance warmup for an Auto Scaling g -Amazon EC2 Auto Scaling determines whether an instance is healthy based on the status of the health checks that your Auto Scaling group uses. For more information, see [Health checks for instances in an Auto Scaling group](./ec2-auto-scaling-health-checks.html). +Amazon EC2 Auto Scaling determines whether an instance is healthy based on the status of the health checks that your Amazon EC2 Auto Scaling group uses. For more information, see [Health checks for instances in an Amazon EC2 Auto Scaling group](./ec2-auto-scaling-health-checks.html). @@ -113 +113 @@ Amazon EC2 Auto Scaling determines whether an instance is healthy based on the s -To make sure that these health checks start as soon as possible, don't set the group's health check grace period too high, but high enough for your Elastic Load Balancing health checks to determine whether a target is available to handle requests. For more information, see [Set the health check grace period for an Auto Scaling group](./health-check-grace-period.html). +To make sure that these health checks start as soon as possible, don't set the group's health check grace period too high, but high enough for your ELB health checks to determine whether a target is available to handle requests. For more information, see [Set the health check grace period for an Amazon EC2 Auto Scaling group](./health-check-grace-period.html). @@ -115 +115 @@ To make sure that these health checks start as soon as possible, don't set the g -## Scale your Auto Scaling group +## Scale your Amazon EC2 Auto Scaling group @@ -119 +119 @@ An instance maintenance policy only applies to instance maintenance events and d -When there are scaling policies or scheduled actions attached to your Auto Scaling group, they can run in parallel while instance maintenance events are occurring. In which case, they could increase or decrease the group's desired capacity but only within the scaling limits that you defined. For more information about these limits, see [Set scaling limits for your Auto Scaling group](./asg-capacity-limits.html). +When there are scaling policies or scheduled actions attached to your Amazon EC2 Auto Scaling group, they can run in parallel while instance maintenance events are occurring. In which case, they could increase or decrease the group's desired capacity but only within the scaling limits that you defined. For more information about these limits, see [Set scaling limits for your Amazon EC2 Auto Scaling group](./asg-capacity-limits.html). @@ -134 +134 @@ In a typical scenario, your instance maintenance policy and desired capacity mig -During any instance maintenance event, your Auto Scaling group might have as few as 90 instances and as many as 120. After the event, the group goes back to having 100 instances. +During any instance maintenance event, your Amazon EC2 Auto Scaling group might have as few as 90 instances and as many as 120. After the event, the group goes back to having 100 instances. @@ -136 +136 @@ During any instance maintenance event, your Auto Scaling group might have as few -When you use an instance maintenance policy with an Auto Scaling group that has a warm pool, the minimum and maximum healthy percentages are applied separately to the Auto Scaling group and the warm pool. +When you use an instance maintenance policy with an Amazon EC2 Auto Scaling group that has a warm pool, the minimum and maximum healthy percentages are applied separately to the Amazon EC2 Auto Scaling group and the warm pool. @@ -151 +151 @@ For example, assume this is your configuration: -If you start an instance refresh to recycle the group's instances, Amazon EC2 Auto Scaling replaces instances in the Auto Scaling group first, and then instances in the warm pool. While Amazon EC2 Auto Scaling is still working on replacing instances in the Auto Scaling group, the group might have as few as 90 instances and as many as 120. After finishing with the group, Amazon EC2 Auto Scaling can work on replacing instances in the warm pool. While this is happening, the warm pool might have as few as 9 instances and as many as 12. +If you start an instance refresh to recycle the group's instances, Amazon EC2 Auto Scaling replaces instances in the Amazon EC2 Auto Scaling group first, and then instances in the warm pool. While Amazon EC2 Auto Scaling is still working on replacing instances in the Amazon EC2 Auto Scaling group, the group might have as few as 90 instances and as many as 120. After finishing with the group, Amazon EC2 Auto Scaling can work on replacing instances in the warm pool. While this is happening, the warm pool might have as few as 9 instances and as many as 12.