AWS cli documentation change
Summary
Updated AWS CLI version from 2.34.25 to 2.34.28 and added documentation for the warmPoolConfig structure including its parameters (enabled, minSize, maxGroupPreparedCapacity, poolState, reuseOnScaleIn) and their descriptions.
Security assessment
The change updates the CLI version reference and adds documentation for a new feature (warm pool configuration) related to cost optimization and availability. There is no mention of security vulnerabilities, patches, or security incidents. The documentation focuses on operational efficiency and cost management.
Diff
diff --git a/cli/latest/reference/eks/delete-nodegroup.md b/cli/latest/reference/eks/delete-nodegroup.md index 6798919d0..2299307e3 100644 --- a//cli/latest/reference/eks/delete-nodegroup.md +++ b//cli/latest/reference/eks/delete-nodegroup.md @@ -15 +15 @@ - * [AWS CLI 2.34.25 Command Reference](../../index.html) » + * [AWS CLI 2.34.28 Command Reference](../../index.html) » @@ -807,0 +808,38 @@ nodegroup -> (structure) +> +> warmPoolConfig -> (structure) +> +>> The warm pool configuration attached to the node group. Amazon EKS manages warm pools throughout the node group lifecycle using the `AWSServiceRoleForAmazonEKSNodegroup` service-linked role to create, update, and delete warm pool resources. +>> +>> enabled -> (boolean) +>> +>>> Specifies whether to attach warm pools on the managed node group. Set to `true` to enable the warm pool, or `false` to disable and remove it. If not specified during an update, the current value is preserved. +>> +>> minSize -> (integer) +>> +>>> The minimum number of instances to maintain in the warm pool. Default: `0` . Size your warm pool based on scaling patterns to balance cost and availability. Start with 10-20% of expected peak capacity. +>>> +>>> Constraints: +>>> +>>> * min: `0` +>>> + +>> +>> maxGroupPreparedCapacity -> (integer) +>> +>>> The maximum total number of instances across the warm pool and Auto Scaling group combined. This value controls the total prepared capacity available for your node group. +>> +>> poolState -> (string) +>> +>>> The desired state for warm pool instances. Default: `Stopped` . Valid values are `Stopped` (most cost-effective with EBS storage costs only), `Running` (fastest transition time with full EC2 costs), and `Hibernated` (balance between cost and speed, only supported on specific instance types). Warm pool instances in the `Hibernated` state are not supported with Bottlerocket AMIs. +>>> +>>> Possible values: +>>> +>>> * `STOPPED` +>>> * `RUNNING` +>>> * `HIBERNATED` +>>> + +>> +>> reuseOnScaleIn -> (boolean) +>> +>>> Indicates whether instances should return to the warm pool during scale-in events instead of being terminated. Default: `false` . Enable this to reduce costs by reusing instances. This feature is not supported for Bottlerocket AMIs. @@ -819 +857 @@ nodegroup -> (structure) - * [AWS CLI 2.34.25 Command Reference](../../index.html) » + * [AWS CLI 2.34.28 Command Reference](../../index.html) »