ClusterEbsVolumeConfig
Defines the configuration for attaching an additional Amazon Elastic Block Store (EBS) volume to each instance of the SageMaker HyperPod cluster instance group. To learn more, see SageMaker HyperPod release notes: June 20, 2024.
Contents
- RootVolume
-
Specifies whether the configuration is for the cluster's root or secondary Amazon EBS volume. You can specify two
ClusterEbsVolumeConfig
fields to configure both the root and secondary volumes. Set the value toTrue
if you'd like to provide your own customer managed AWS KMS key to encrypt the root volume. WhenTrue
:-
The configuration is applied to the root volume.
-
You can't specify the
VolumeSizeInGB
field. The size of the root volume is determined for you. -
You must specify a KMS key ID for
VolumeKmsKeyId
to encrypt the root volume with your own KMS key instead of an AWS owned KMS key.
Otherwise, by default, the value is
False
, and the following applies:-
The configuration is applied to the secondary volume, while the root volume is encrypted with an AWS owned key.
-
You must specify the
VolumeSizeInGB
field. -
You can optionally specify the
VolumeKmsKeyId
to encrypt the secondary volume with your own KMS key instead of an AWS owned KMS key.
Type: Boolean
Required: No
-
- VolumeKmsKeyId
-
The ID of a KMS key to encrypt the Amazon EBS volume.
Type: String
Length Constraints: Minimum length of 0. Maximum length of 2048.
Pattern:
[a-zA-Z0-9:/_-]*
Required: No
- VolumeSizeInGB
-
The size in gigabytes (GB) of the additional EBS volume to be attached to the instances in the SageMaker HyperPod cluster instance group. The additional EBS volume is attached to each instance within the SageMaker HyperPod cluster instance group and mounted to
/opt/sagemaker
.Type: Integer
Valid Range: Minimum value of 1. Maximum value of 16384.
Required: No
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the following: