AWS sagemaker medium security documentation change
Summary
Added April 2025 release notes with new features (DPO tutorial, Quickstart guide, instance types), documentation link updates, bug fixes, and security patching instructions
Security assessment
Explicitly mentions security patching via UpdateClusterSoftware API and provides documentation for applying security updates. This directly addresses security maintenance processes.
Diff
diff --git a/sagemaker/latest/dg/sagemaker-hyperpod-release-notes.md b/sagemaker/latest/dg/sagemaker-hyperpod-release-notes.md index 8dbbde776..7fb4cffe2 100644 --- a//sagemaker/latest/dg/sagemaker-hyperpod-release-notes.md +++ b//sagemaker/latest/dg/sagemaker-hyperpod-release-notes.md @@ -5 +5 @@ -March 16, 2025February 20, 2025February 18, 2025February 06, 2025January 22, 2025January 09, 2025December 21, 2024December 13, 2024November 24, 2024November 15, 2024November 11, 2024October 31, 2024October 21, 2024September 10, 2024August 20, 2024June 20, 2024April 24, 2024March 27, 2024March 14, 2024February 15, 2024November 29, 2023 +April 10, 2025April 03, 2025March 16, 2025February 20, 2025February 18, 2025February 06, 2025January 22, 2025January 09, 2025December 21, 2024December 13, 2024November 24, 2024November 15, 2024November 11, 2024October 31, 2024October 21, 2024September 10, 2024August 20, 2024June 20, 2024April 24, 2024March 27, 2024March 14, 2024February 15, 2024November 29, 2023 @@ -12,0 +13,26 @@ The HyperPod AMI releases are documented separately to include information of th +## SageMaker HyperPod release notes: April 10, 2025 + +SageMaker HyperPod releases the following for [Orchestrating SageMaker HyperPod clusters with Slurm](./sagemaker-hyperpod-slurm.html). + +**New features and improvements** + + * Added a Direct Preference Optimization (DPO) recipe tutorial for SageMaker HyperPod with Slurm orchestration. This fine-tuning tutorial provides step-by-step guidance for optimizing model alignment using the DPO method on GPU-powered SageMaker HyperPod Slurm clusters. For more information, see [HyperPod Slurm cluster DPO tutorial (GPU)](./hyperpod-gpu-slurm-dpo-tutorial.html). + + + + +## SageMaker HyperPod release notes: April 03, 2025 + +SageMaker HyperPod releases the following for [Orchestrating SageMaker HyperPod clusters with Slurm](./sagemaker-hyperpod-slurm.html) and [Orchestrating SageMaker HyperPod clusters with Amazon EKS](./sagemaker-hyperpod-eks.html). + +**New features and improvements** + + * Added a [Quickstart](./sagemaker-hyperpod-quickstart.html) page for deploying SageMaker HyperPod clusters. The page leverages streamlined setup workflows from SageMaker HyperPod’s specialized workshops and automates deployment using prebuilt AWS CloudFormation templates. It supports infrastructure preferences like Slurm or Amazon EKS, for easy configuration and deployment of baseline clusters. + + * SageMaker HyperPod now supports the following instance types for both Slurm and Amazon EKS clusters. + + * New instance types: I3en, M7i, R7i instances. For the full list of supported instances, see the `InstanceType` field in the `[ClusterInstanceGroupSpecification](https://docs.aws.amazon.com/APIReference/API_ClusterInstanceGroupSpecification.html#sagemaker-Type-ClusterInstanceGroupSpecification-InstanceType)`. + + + + @@ -36 +62 @@ SageMaker HyperPod releases the following for [Orchestrating SageMaker HyperPod - * Added support for deleting instance groups from your SageMaker HyperPod cluster. For more information, see [Delete instance groups](./smcluster-scale-down.html#smcluster-remove-instancegroup) from EKS-orchestrated clusters and [Scale down a cluster](./sagemaker-hyperpod-operate-cli-command.html#sagemaker-hyperpod-operate-cli-command-scale-down) for Slurm-orchestrated clusters. + * Added support for deleting instance groups from your SageMaker HyperPod cluster. For more information, see [Delete instance groups](./smcluster-scale-down.html#smcluster-remove-instancegroup) from EKS-orchestrated clusters and [Scale down a cluster](./sagemaker-hyperpod-operate-slurm-cli-command.html#sagemaker-hyperpod-operate-slurm-cli-command-scale-down) for Slurm-orchestrated clusters. @@ -229 +255 @@ SageMaker HyperPod releases the following for [Orchestrating SageMaker HyperPod - * Added scaling down SageMaker HyperPod clusters at the instance group level and instance level for both Amazon EKS and Slurm orchestrated clusters. For more information about scaling down Amazon EKS clusters, see [Scale down a SageMaker HyperPod cluster](./smcluster-scale-down.html). For more information about scaling down Slurm clusters, see _Scale down a cluster_ in [Using the AWS CLI](./sagemaker-hyperpod-operate-cli-command.html). + * Added scaling down SageMaker HyperPod clusters at the instance group level and instance level for both Amazon EKS and Slurm orchestrated clusters. For more information about scaling down Amazon EKS clusters, see [Scale down a SageMaker HyperPod cluster](./smcluster-scale-down.html). For more information about scaling down Slurm clusters, see _Scale down a cluster_ in [Using the AWS CLI](./sagemaker-hyperpod-operate-slurm-cli-command.html). @@ -284 +310 @@ SageMaker HyperPod releases the following for [Orchestrating SageMaker HyperPod - * Enhanced the [SageMaker HyperPod auto-resume functionality](https://docs.aws.amazon.com/sagemaker/latest/dg/sagemaker-hyperpod-resiliency.html#sagemaker-hyperpod-resiliency-auto-resume), extending the resiliency capability for Slurm nodes attached with Generic RESources (GRES). + * Enhanced the [SageMaker HyperPod auto-resume functionality](https://docs.aws.amazon.com/sagemaker/latest/dg/sagemaker-hyperpod-resiliency-slurm.html#sagemaker-hyperpod-resiliency-slurm-auto-resume), extending the resiliency capability for Slurm nodes attached with Generic RESources (GRES). @@ -317 +343 @@ SageMaker HyperPod releases the following for [Orchestrating SageMaker HyperPod - * [Tutorial for getting started with SageMaker HyperPod](./smcluster-getting-started.html) + * [Tutorial for getting started with SageMaker HyperPod](./smcluster-getting-started-slurm.html) @@ -319 +345 @@ SageMaker HyperPod releases the following for [Orchestrating SageMaker HyperPod - * [SageMaker HyperPod operation](./sagemaker-hyperpod-operate.html) + * [SageMaker HyperPod operation](./sagemaker-hyperpod-operate-slurm.html) @@ -328 +354 @@ Note that you need to update the HyperPod cluster software to use this capabilit - * Run the following command to call the [UpdateClusterSoftware](https://docs.aws.amazon.com/sagemaker/latest/APIReference/API_UpdateClusterSoftware.html) API to update your existing HyperPod clusters with the latest HyperPod DLAMI. To find more instructions, see [Update the SageMaker HyperPod platform software of a cluster](./sagemaker-hyperpod-operate-cli-command.html#sagemaker-hyperpod-operate-cli-command-update-cluster-software). + * Run the following command to call the [UpdateClusterSoftware](https://docs.aws.amazon.com/sagemaker/latest/APIReference/API_UpdateClusterSoftware.html) API to update your existing HyperPod clusters with the latest HyperPod DLAMI. To find more instructions, see [Update the SageMaker HyperPod platform software of a cluster](./sagemaker-hyperpod-operate-slurm-cli-command.html#sagemaker-hyperpod-operate-slurm-cli-command-update-cluster-software). @@ -332 +358 @@ Note that you need to update the HyperPod cluster software to use this capabilit -Back up your work before running this API. The patching process replaces the root volume with the updated AMI, which means that your previous data stored in the instance root volume will be lost. Make sure that you back up your data from the instance root volume to Amazon S3 or Amazon FSx for Lustre. For more information, see [Use the backup script provided by SageMaker HyperPod](./sagemaker-hyperpod-operate-cli-command.html#sagemaker-hyperpod-operate-cli-command-update-cluster-software-backup). +Back up your work before running this API. The patching process replaces the root volume with the updated AMI, which means that your previous data stored in the instance root volume will be lost. Make sure that you back up your data from the instance root volume to Amazon S3 or Amazon FSx for Lustre. For more information, see [Use the backup script provided by SageMaker HyperPod](./sagemaker-hyperpod-operate-slurm-cli-command.html#sagemaker-hyperpod-operate-slurm-cli-command-update-cluster-software-backup). @@ -349 +375 @@ SageMaker HyperPod releases the following for [Orchestrating SageMaker HyperPod - * Fixed a bug with the `ThreadsPerCore` parameter in the [`ClusterInstanceGroupSpecification`](https://docs.aws.amazon.com/sagemaker/latest/APIReference/API_ClusterInstanceGroupSpecification.html) API. With the fix, the [`CreateCluster`](https://docs.aws.amazon.com/sagemaker/latest/APIReference/API_CreateCluster.html) and [`UpdateCluster`](https://docs.aws.amazon.com/sagemaker/latest/APIReference/API_UpdateCluster.html) APIs properly take and apply the user input through `ThreadsPerCore`. This fix is effective on HyperPod clusters created after April 24, 2024. If you had issues with this bug and want to get this fix applied to your cluster, you need to create a new cluster. Make sure that you back up and restore your work while moving to a new cluster following the instructions at [Use the backup script provided by SageMaker HyperPod](./sagemaker-hyperpod-operate-cli-command.html#sagemaker-hyperpod-operate-cli-command-update-cluster-software-backup). + * Fixed a bug with the `ThreadsPerCore` parameter in the [`ClusterInstanceGroupSpecification`](https://docs.aws.amazon.com/sagemaker/latest/APIReference/API_ClusterInstanceGroupSpecification.html) API. With the fix, the [`CreateCluster`](https://docs.aws.amazon.com/sagemaker/latest/APIReference/API_CreateCluster.html) and [`UpdateCluster`](https://docs.aws.amazon.com/sagemaker/latest/APIReference/API_UpdateCluster.html) APIs properly take and apply the user input through `ThreadsPerCore`. This fix is effective on HyperPod clusters created after April 24, 2024. If you had issues with this bug and want to get this fix applied to your cluster, you need to create a new cluster. Make sure that you back up and restore your work while moving to a new cluster following the instructions at [Use the backup script provided by SageMaker HyperPod](./sagemaker-hyperpod-operate-slurm-cli-command.html#sagemaker-hyperpod-operate-slurm-cli-command-update-cluster-software-backup). @@ -397 +423 @@ SageMaker HyperPod releases the following for [Orchestrating SageMaker HyperPod - * HyperPod now properly supports passing partition names provided through `provisioning_params.json` and creates partitions appropriately based on provided inputs. For more information about `provisioning_params.json`, see [SageMaker HyperPod forms](./sagemaker-hyperpod-ref.html#sagemaker-hyperpod-ref-provisioning-forms) and [Customize SageMaker HyperPod clusters using lifecycle scripts](./sagemaker-hyperpod-lifecycle-best-practices.html). + * HyperPod now properly supports passing partition names provided through `provisioning_parameters.json` and creates partitions appropriately based on provided inputs. For more information about `provisioning_parameters.json`, see [SageMaker HyperPod forms](./sagemaker-hyperpod-ref.html#sagemaker-hyperpod-ref-provisioning-forms) and [Customize SageMaker HyperPod clusters using lifecycle scripts](./sagemaker-hyperpod-lifecycle-best-practices-slurm.html). @@ -415 +441 @@ SageMaker HyperPod releases the following for [Orchestrating SageMaker HyperPod - * Added a new `UpdateClusterSoftware` API for SageMaker HyperPod security patching. When security patches become available, we recommend you to update existing SageMaker HyperPod clusters in your account by running `aws sagemaker update-cluster-software --cluster-name `your-cluster-name``. To follow up with future security patches, keep tracking this Amazon SageMaker HyperPod release notes page. To learn how the `UpdateClusterSoftware` API works, see [Update the SageMaker HyperPod platform software of a cluster](./sagemaker-hyperpod-operate-cli-command.html#sagemaker-hyperpod-operate-cli-command-update-cluster-software). + * Added a new `UpdateClusterSoftware` API for SageMaker HyperPod security patching. When security patches become available, we recommend you to update existing SageMaker HyperPod clusters in your account by running `aws sagemaker update-cluster-software --cluster-name `your-cluster-name``. To follow up with future security patches, keep tracking this Amazon SageMaker HyperPod release notes page. To learn how the `UpdateClusterSoftware` API works, see [Update the SageMaker HyperPod platform software of a cluster](./sagemaker-hyperpod-operate-slurm-cli-command.html#sagemaker-hyperpod-operate-slurm-cli-command-update-cluster-software).