AWS autoscaling documentation change
Summary
Updated branding from 'Auto Scaling' to 'Amazon EC2 Auto Scaling' throughout the document, added a new related resource link for instance lifecycle policies, and replaced 'Elastic Load Balancing' with 'ELB' abbreviation.
Security assessment
Changes are primarily branding updates and adding a reference to instance lifecycle policies documentation. No security vulnerabilities, patches, or security-specific features are mentioned. The instance lifecycle policy addition relates to operational management, not explicit security controls.
Diff
diff --git a/autoscaling/ec2/userguide/lifecycle-hooks.md b/autoscaling/ec2/userguide/lifecycle-hooks.md index ac47c85d8..dac5d3251 100644 --- a//autoscaling/ec2/userguide/lifecycle-hooks.md +++ b//autoscaling/ec2/userguide/lifecycle-hooks.md @@ -9 +9 @@ Lifecycle hook availabilityConsiderations and limitationsRelated resources -Amazon EC2 Auto Scaling offers the ability to add lifecycle hooks to your Auto Scaling groups. These hooks let you create solutions that are aware of events in the Auto Scaling instance lifecycle, and then perform a custom action on instances when the corresponding lifecycle event occurs. A lifecycle hook provides a specified amount of time (one hour by default) to wait for the action to complete before the instance transitions to the next state. +Amazon EC2 Auto Scaling offers the ability to add lifecycle hooks to your Amazon EC2 Auto Scaling groups. These hooks let you create solutions that are aware of events in the Amazon EC2 Auto Scaling instance lifecycle, and then perform a custom action on instances when the corresponding lifecycle event occurs. A lifecycle hook provides a specified amount of time (one hour by default) to wait for the action to complete before the instance transitions to the next state. @@ -11 +11 @@ Amazon EC2 Auto Scaling offers the ability to add lifecycle hooks to your Auto S -As an example of using lifecycle hooks with Auto Scaling instances: +As an example of using lifecycle hooks with Amazon EC2 Auto Scaling instances: @@ -20 +20 @@ As an example of using lifecycle hooks with Auto Scaling instances: -A popular use of lifecycle hooks is to control when instances are registered with Elastic Load Balancing. By adding a launch lifecycle hook to your Auto Scaling group, you can ensure that your bootstrap scripts have completed successfully and the applications on the instances are ready to accept traffic before they are registered to the load balancer at the end of the lifecycle hook. +A popular use of lifecycle hooks is to control when instances are registered with ELB. By adding a launch lifecycle hook to your Amazon EC2 Auto Scaling group, you can ensure that your bootstrap scripts have completed successfully and the applications on the instances are ready to accept traffic before they are registered to the load balancer at the end of the lifecycle hook. @@ -30 +30 @@ A popular use of lifecycle hooks is to control when instances are registered wit - * [How lifecycle hooks work in Auto Scaling groups](./lifecycle-hooks-overview.html) + * [How lifecycle hooks work in Amazon EC2 Auto Scaling groups](./lifecycle-hooks-overview.html) @@ -33,0 +34,2 @@ A popular use of lifecycle hooks is to control when instances are registered wit + * [Control instance retention with instance lifecycle policies](./instance-lifecycle-policy.html) + @@ -36 +38 @@ A popular use of lifecycle hooks is to control when instances are registered wit - * [Add lifecycle hooks to your Auto Scaling group](./adding-lifecycle-hooks.html) + * [Add lifecycle hooks to your Amazon EC2 Auto Scaling group](./adding-lifecycle-hooks.html) @@ -38 +40 @@ A popular use of lifecycle hooks is to control when instances are registered wit - * [Complete a lifecycle action in an Auto Scaling group](./completing-lifecycle-hooks.html) + * [Complete a lifecycle action in an Amazon EC2 Auto Scaling group](./completing-lifecycle-hooks.html) @@ -62 +64 @@ When working with lifecycle hooks, keep in mind the following notes and limitati - * Amazon EC2 Auto Scaling provides its own lifecycle to help with the management of Auto Scaling groups. This lifecycle differs from that of other EC2 instances. For more information, see [Amazon EC2 Auto Scaling instance lifecycle](./ec2-auto-scaling-lifecycle.html). Instances in a warm pool also have their own lifecycle, as described in [Lifecycle state transitions for instances in a warm pool](./warm-pool-instance-lifecycle.html#lifecycle-state-transitions). + * Amazon EC2 Auto Scaling provides its own lifecycle to help with the management of Amazon EC2 Auto Scaling groups. This lifecycle differs from that of other EC2 instances. For more information, see [Amazon EC2 Auto Scaling instance lifecycle](./ec2-auto-scaling-lifecycle.html). Instances in a warm pool also have their own lifecycle, as described in [Lifecycle state transitions for instances in a warm pool](./warm-pool-instance-lifecycle.html#lifecycle-state-transitions). @@ -64 +66 @@ When working with lifecycle hooks, keep in mind the following notes and limitati - * You can use lifecycle hooks with Spot Instances, but a lifecycle hook does not prevent an instance from terminating in the event that capacity is no longer available, which can happen at any time with a two-minute interruption notice. For more information, see [Spot Instance interruptions](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/spot-interruptions.html) in the _Amazon EC2 User Guide_. However, you can enable Capacity Rebalancing to proactively replace Spot Instances that have received a rebalance recommendation from the Amazon EC2 Spot service, a signal that is sent when a Spot Instance is at elevated risk of interruption. For more information, see [Capacity Rebalancing in Auto Scaling to replace at-risk Spot Instances](./ec2-auto-scaling-capacity-rebalancing.html). + * You can use lifecycle hooks with Spot Instances, but a lifecycle hook does not prevent an instance from terminating in the event that capacity is no longer available, which can happen at any time with a two-minute interruption notice. For more information, see [Spot Instance interruptions](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/spot-interruptions.html) in the _Amazon EC2 User Guide_. However, you can enable Capacity Rebalancing to proactively replace Spot Instances that have received a rebalance recommendation from the Amazon EC2 Spot service, a signal that is sent when a Spot Instance is at elevated risk of interruption. For more information, see [Capacity Rebalancing in Amazon EC2 Auto Scaling to replace at-risk Spot Instances](./ec2-auto-scaling-capacity-rebalancing.html). @@ -74 +76 @@ When working with lifecycle hooks, keep in mind the following notes and limitati - * You can add multiple lifecycle hooks to an Auto Scaling group while you are creating it, by calling the [CreateAutoScalingGroup](https://docs.aws.amazon.com/autoscaling/ec2/APIReference/API_CreateAutoScalingGroup.html) API using the AWS CLI, CloudFormation, or an SDK. However, each hook must have the same notification target and IAM role, if specified. To create lifecycle hooks with different notification targets and different roles, create the lifecycle hooks one at a time in separate calls to the [PutLifecycleHook](https://docs.aws.amazon.com/autoscaling/ec2/APIReference/API_PutLifecycleHook.html) API. + * You can add multiple lifecycle hooks to an Amazon EC2 Auto Scaling group while you are creating it, by calling the [CreateAutoScalingGroup](https://docs.aws.amazon.com/autoscaling/ec2/APIReference/API_CreateAutoScalingGroup.html) API using the AWS CLI, CloudFormation, or an SDK. However, each hook must have the same notification target and IAM role, if specified. To create lifecycle hooks with different notification targets and different roles, create the lifecycle hooks one at a time in separate calls to the [PutLifecycleHook](https://docs.aws.amazon.com/autoscaling/ec2/APIReference/API_PutLifecycleHook.html) API. @@ -76 +78 @@ When working with lifecycle hooks, keep in mind the following notes and limitati - * If you add a lifecycle hook for instance launch, the health check grace period starts as soon as the instance reaches the `InService` state. For more information, see [Set the health check grace period for an Auto Scaling group](./health-check-grace-period.html). + * If you add a lifecycle hook for instance launch, the health check grace period starts as soon as the instance reaches the `InService` state. For more information, see [Set the health check grace period for an Amazon EC2 Auto Scaling group](./health-check-grace-period.html). @@ -83 +85 @@ When working with lifecycle hooks, keep in mind the following notes and limitati - * Dynamic scaling policies scale in and out in response to CloudWatch metric data, such as CPU and network I/O, that's aggregated across multiple instances. When scaling out, Amazon EC2 Auto Scaling doesn't immediately count a new instance towards the aggregated instance metrics of the Auto Scaling group. It waits until the instance reaches the `InService` state and the instance warmup has finished. For more information, see [Scaling performance considerations](./ec2-auto-scaling-default-instance-warmup.html#scaling-performance-considerations) in the default instance warmup topic. + * Dynamic scaling policies scale in and out in response to CloudWatch metric data, such as CPU and network I/O, that's aggregated across multiple instances. When scaling out, Amazon EC2 Auto Scaling doesn't immediately count a new instance towards the aggregated instance metrics of the Amazon EC2 Auto Scaling group. It waits until the instance reaches the `InService` state and the instance warmup has finished. For more information, see [Scaling performance considerations](./ec2-auto-scaling-default-instance-warmup.html#scaling-performance-considerations) in the default instance warmup topic. @@ -117 +119 @@ Remove an instance maintenance policy -How lifecycle hooks work in Auto Scaling groups +How lifecycle hooks work in Amazon EC2 Auto Scaling groups