AWS sagemaker documentation change
Summary
Fixed broken URLs in EBS volumes documentation links
Security assessment
The changes only correct URL formatting in storage documentation references. While EBS security is important, these changes don't add security guidance or address specific vulnerabilities.
Diff
diff --git a/sagemaker/latest/dg/sagemaker-hyperpod-quickstart.md b/sagemaker/latest/dg/sagemaker-hyperpod-quickstart.md index fb395b215..f0e5828b4 100644 --- a//sagemaker/latest/dg/sagemaker-hyperpod-quickstart.md +++ b//sagemaker/latest/dg/sagemaker-hyperpod-quickstart.md @@ -56 +56 @@ Ensure that you choose the instance type with sufficient quotas in your account, - 7. For **Additional storage volume per instance (GB) - optional** , specify an integer between 1 and 16384 to set the size of an additional Elastic Block Store (EBS) volume in gigabytes (GB). The EBS volume is attached to each instance of the instance group. The default mount path for the additional EBS volume is `/opt/sagemaker`. After the cluster is successfully created, you can SSH into the cluster instances (nodes) and verify if the EBS volume is mounted correctly by running the `df -h` command. Attaching an additional EBS volume provides stable, off-instance, and independently persisting storage, as described in the [Amazon EBS volumes](https://docs.aws.amazon.com/ebs/latest/userguide/ebs-volumes.html) section in the _Amazon Elastic Block Store User Guide_. + 7. For **Additional storage volume per instance (GB) - optional** , specify an integer between 1 and 16384 to set the size of an additional Elastic Block Store (EBS) volume in gigabytes (GB). The EBS volume is attached to each instance of the instance group. The default mount path for the additional EBS volume is `/opt/sagemaker`. After the cluster is successfully created, you can SSH into the cluster instances (nodes) and verify if the EBS volume is mounted correctly by running the `df -h` command. Attaching an additional EBS volume provides stable, off-instance, and independently persisting storage, as described in the [Amazon EBS volumes](https://docs.aws.amazon.com//ebs/latest/userguide/ebs-volumes.html) section in the _Amazon Elastic Block Store User Guide_. @@ -101 +101 @@ Follow these steps to add an instance group. - 7. For **Additional storage volume per instance (GB) - optional** , specify an integer between 1 and 16384 to set the size of an additional Elastic Block Store (EBS) volume in gigabytes (GB). The EBS volume is attached to each instance of the instance group. The default mount path for the additional EBS volume is `/opt/sagemaker`. After the cluster is successfully created, you can SSH into the cluster instances (nodes) and verify if the EBS volume is mounted correctly by running the `df -h` command. Attaching an additional EBS volume provides stable, off-instance, and independently persisting storage, as described in the [Amazon EBS volumes](https://docs.aws.amazon.com/ebs/latest/userguide/ebs-volumes.html) section in the _Amazon Elastic Block Store User Guide_. + 7. For **Additional storage volume per instance (GB) - optional** , specify an integer between 1 and 16384 to set the size of an additional Elastic Block Store (EBS) volume in gigabytes (GB). The EBS volume is attached to each instance of the instance group. The default mount path for the additional EBS volume is `/opt/sagemaker`. After the cluster is successfully created, you can SSH into the cluster instances (nodes) and verify if the EBS volume is mounted correctly by running the `df -h` command. Attaching an additional EBS volume provides stable, off-instance, and independently persisting storage, as described in the [Amazon EBS volumes](https://docs.aws.amazon.com//ebs/latest/userguide/ebs-volumes.html) section in the _Amazon Elastic Block Store User Guide_.