AWS sagemaker documentation change
Summary
Added documentation about rolling upgrade behavior for flexible instance groups, explaining how upgrades are distributed proportionally across different instance types in batches.
Security assessment
This change describes operational behavior during software updates for a specific configuration. While software updates can include security patches, this documentation only explains the distribution mechanism during upgrades, not any security-specific content or vulnerabilities.
Diff
diff --git a/sagemaker/latest/dg/sagemaker-hyperpod-eks-operate-cli-command-update-cluster-software.md b/sagemaker/latest/dg/sagemaker-hyperpod-eks-operate-cli-command-update-cluster-software.md index f8ab62c6e..5e5fc5afc 100644 --- a//sagemaker/latest/dg/sagemaker-hyperpod-eks-operate-cli-command-update-cluster-software.md +++ b//sagemaker/latest/dg/sagemaker-hyperpod-eks-operate-cli-command-update-cluster-software.md @@ -28,0 +29,4 @@ If the security patch fails, you can retrieve failure messages by running the [` +###### Rolling upgrades with flexible instance groups + +For instance groups that use `InstanceRequirements` with multiple instance types, rolling upgrades spread each instance type proportionally across batches. For example, if an instance group has 100 instances (10 P5 and 90 G6) and you configure a 10% batch size, each batch contains 1 P5 instance and 9 G6 instances. +