AWS autoscaling documentation change
Summary
Updated terminology from 'Auto Scaling group' to 'Amazon EC2 Auto Scaling group' throughout the document for consistency
Security assessment
Changes are purely terminological updates to align with product naming conventions. No security vulnerabilities, mitigations, or security features are mentioned or modified in the content.
Diff
diff --git a/autoscaling/ec2/userguide/mixed-instances-groups-set-up-overview.md b/autoscaling/ec2/userguide/mixed-instances-groups-set-up-overview.md index b7da90cbb..ffde309af 100644 --- a//autoscaling/ec2/userguide/mixed-instances-groups-set-up-overview.md +++ b//autoscaling/ec2/userguide/mixed-instances-groups-set-up-overview.md @@ -9 +9 @@ OverviewInstance type flexibilityAvailability Zone flexibilitySpot max priceProa -This topic provides an overview and best practices for creating an Auto Scaling mixed instances group. +This topic provides an overview and best practices for creating an Amazon EC2 Auto Scaling mixed instances group. @@ -67 +67 @@ The following steps describe how to create a mixed instances group by manually c -Overrides are necessary to override the instance type declared in the launch template and use multiple instances types that are embedded in the Auto Scaling group's own resource definition. For more information about the instance types that are available, see [Instance types](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-types.html) in the _Amazon EC2 User Guide_. +Overrides are necessary to override the instance type declared in the launch template and use multiple instances types that are embedded in the Amazon EC2 Auto Scaling group's own resource definition. For more information about the instance types that are available, see [Instance types](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-types.html) in the _Amazon EC2 User Guide_. @@ -73 +73 @@ You can also configure the following optional parameters for each instance type: - * `WeightedCapacity` – You decide how much the instance counts toward the desired capacity relative to the rest of the instances in your group. If you specify a `WeightedCapacity` value for one instance type, you must specify a `WeightedCapacity` value for all of them. By default, each instance counts as one toward your desired capacity. For more information, see [Configure an Auto Scaling group to use instance weights](./ec2-auto-scaling-mixed-instances-groups-instance-weighting.html). + * `WeightedCapacity` – You decide how much the instance counts toward the desired capacity relative to the rest of the instances in your group. If you specify a `WeightedCapacity` value for one instance type, you must specify a `WeightedCapacity` value for all of them. By default, each instance counts as one toward your desired capacity. For more information, see [Configure an Amazon EC2 Auto Scaling group to use instance weights](./ec2-auto-scaling-mixed-instances-groups-instance-weighting.html). @@ -104 +104 @@ You can also configure the `LaunchTemplateSpecification` parameter within the ov -By default, you set the number of instances as the desired capacity of your Auto Scaling group. +By default, you set the number of instances as the desired capacity of your Amazon EC2 Auto Scaling group. @@ -118 +118 @@ We recommend being flexible across at least 10 instance types for each workload. -We strongly recommend that you span your Auto Scaling group across multiple Availability Zones. With multiple Availability Zones, you can design applications that automatically fail over between zones for greater resiliency. +We strongly recommend that you span your Amazon EC2 Auto Scaling group across multiple Availability Zones. With multiple Availability Zones, you can design applications that automatically fail over between zones for greater resiliency. @@ -126 +126 @@ For more information about using multiple Availability Zones, see [Example: Dist -When you create your Auto Scaling group using the AWS CLI or an SDK, you can specify the `SpotMaxPrice` parameter. The `SpotMaxPrice` parameter determines the maximum price that you're willing to pay for a Spot Instance hour. +When you create your Amazon EC2 Auto Scaling group using the AWS CLI or an SDK, you can specify the `SpotMaxPrice` parameter. The `SpotMaxPrice` parameter determines the maximum price that you're willing to pay for a Spot Instance hour. @@ -138 +138 @@ When Capacity Rebalancing is enabled, Amazon EC2 Auto Scaling attempts to proact -For more information, see [Capacity Rebalancing in Auto Scaling to replace at-risk Spot Instances](./ec2-auto-scaling-capacity-rebalancing.html). +For more information, see [Capacity Rebalancing in Amazon EC2 Auto Scaling to replace at-risk Spot Instances](./ec2-auto-scaling-capacity-rebalancing.html). @@ -148 +148 @@ Amazon EC2 Auto Scaling converts the percentage to the equivalent number of inst -The following table demonstrates the behavior of the Auto Scaling group as it increases and decreases in size. +The following table demonstrates the behavior of the Amazon EC2 Auto Scaling group as it increases and decreases in size. @@ -188 +188 @@ For more best practices for Spot Instances, see [Best practices for EC2 Spot](ht -After you add overrides to an Auto Scaling group using a [mixed instances policy](https://docs.aws.amazon.com/autoscaling/ec2/APIReference/API_MixedInstancesPolicy.html), you can update the overrides with the `UpdateAutoScalingGroup` API call but not delete them. To completely remove the overrides, you must first switch the Auto Scaling group to use a launch template or launch configuration instead of a mixed instances policy. Then, you can add a mixed instances policy again without any overrides. +After you add overrides to an Amazon EC2 Auto Scaling group using a [mixed instances policy](https://docs.aws.amazon.com/autoscaling/ec2/APIReference/API_MixedInstancesPolicy.html), you can update the overrides with the `UpdateAutoScalingGroup` API call but not delete them. To completely remove the overrides, you must first switch the Amazon EC2 Auto Scaling group to use a launch template or launch configuration instead of a mixed instances policy. Then, you can add a mixed instances policy again without any overrides.