AWS autoscaling documentation change
Summary
Updated terminology from 'Auto Scaling group' to 'Amazon EC2 Auto Scaling group' throughout the document for consistency. Also updated a link text to match the new terminology.
Security assessment
The changes are purely cosmetic terminology updates with no security implications. There is no evidence of vulnerability fixes, security weaknesses, or new security features. The updates maintain existing content about Spot/On-Demand allocation strategies without altering security-related aspects.
Diff
diff --git a/autoscaling/ec2/userguide/allocation-strategies.md b/autoscaling/ec2/userguide/allocation-strategies.md index 4e1f4596b..bc7c94df6 100644 --- a//autoscaling/ec2/userguide/allocation-strategies.md +++ b//autoscaling/ec2/userguide/allocation-strategies.md @@ -54 +54 @@ We don't recommend the `lowest-price` strategy because it has the highest risk o -Amazon EC2 Auto Scaling requests your Spot Instances using the lowest priced pools within an Availability Zone, across the N number of Spot pools that you specify for the **Lowest priced pools** setting. For example, if you specify four instance types and four Availability Zones, your Auto Scaling group can access up to 16 Spot pools. (Four in each Availability Zone.) If you specify two Spot pools (N=2) for the allocation strategy, your Auto Scaling group can draw on the two lowest priced pools per Availability Zone to fulfill your Spot capacity. +Amazon EC2 Auto Scaling requests your Spot Instances using the lowest priced pools within an Availability Zone, across the N number of Spot pools that you specify for the **Lowest priced pools** setting. For example, if you specify four instance types and four Availability Zones, your Amazon EC2 Auto Scaling group can access up to 16 Spot pools. (Four in each Availability Zone.) If you specify two Spot pools (N=2) for the allocation strategy, your Amazon EC2 Auto Scaling group can draw on the two lowest priced pools per Availability Zone to fulfill your Spot capacity. @@ -78 +78 @@ To meet your desired capacity, you might receive On-Demand Instances of more tha -When fulfilling On-Demand capacity, Amazon EC2 Auto Scaling determines which instance type to use first based on the order of instance types in the list of launch template overrides. For example, let's say that you specify three launch template overrides in the following order: `c5.large`, `c4.large`, and `c3.large`. When your On-Demand Instances launch, the Auto Scaling group fulfills On-Demand capacity in the following order: `c5.large`, `c4.large`, and then `c3.large`. +When fulfilling On-Demand capacity, Amazon EC2 Auto Scaling determines which instance type to use first based on the order of instance types in the list of launch template overrides. For example, let's say that you specify three launch template overrides in the following order: `c5.large`, `c4.large`, and `c3.large`. When your On-Demand Instances launch, the Amazon EC2 Auto Scaling group fulfills On-Demand capacity in the following order: `c5.large`, `c4.large`, and then `c3.large`. @@ -93 +93 @@ Consider the following when managing the priority order of your On-Demand Instan -When you specify the `WeightedCapacity` parameter in your overrides (or `"DesiredCapacityType": "vcpu"` or `"DesiredCapacityType": "memory-mib"` at the group level), the allocation strategies work exactly like they do for other Auto Scaling groups. +When you specify the `WeightedCapacity` parameter in your overrides (or `"DesiredCapacityType": "vcpu"` or `"DesiredCapacityType": "memory-mib"` at the group level), the allocation strategies work exactly like they do for other Amazon EC2 Auto Scaling groups. @@ -95 +95 @@ When you specify the `WeightedCapacity` parameter in your overrides (or `"Desire -Suppose you have an Auto Scaling group with several instance types that have varying amounts of vCPUs. You use `lowest-price` for your Spot and On-Demand allocation strategies. If you choose to assign weights based on the vCPU count of each instance type, Amazon EC2 Auto Scaling launches whichever instance types have the lowest price per your assigned weight values (for example, per vCPU) at the time of fulfillment. If it's a Spot Instance, then this means the lowest Spot price per vCPU. If it's an On-Demand Instance, then this means the lowest On-Demand price per vCPU. +Suppose you have an Amazon EC2 Auto Scaling group with several instance types that have varying amounts of vCPUs. You use `lowest-price` for your Spot and On-Demand allocation strategies. If you choose to assign weights based on the vCPU count of each instance type, Amazon EC2 Auto Scaling launches whichever instance types have the lowest price per your assigned weight values (for example, per vCPU) at the time of fulfillment. If it's a Spot Instance, then this means the lowest Spot price per vCPU. If it's an On-Demand Instance, then this means the lowest On-Demand price per vCPU. @@ -97 +97 @@ Suppose you have an Auto Scaling group with several instance types that have var -For more information, see [Configure an Auto Scaling group to use instance weights](./ec2-auto-scaling-mixed-instances-groups-instance-weighting.html). +For more information, see [Configure an Amazon EC2 Auto Scaling group to use instance weights](./ec2-auto-scaling-mixed-instances-groups-instance-weighting.html).