AWS sagemaker documentation change
Summary
Added note about Dockerfile application type consistency and streamlined instructions for custom image attachment
Security assessment
Changes focus on procedural accuracy for custom image configuration rather than addressing security vulnerabilities. While Dockerfile consistency is important, the change doesn't explicitly mention security implications.
Diff
diff --git a/sagemaker/latest/dg/studio-updated-byoi-how-to-attach-to-domain.md b/sagemaker/latest/dg/studio-updated-byoi-how-to-attach-to-domain.md index 1cabcb683..c5c744163 100644 --- a//sagemaker/latest/dg/studio-updated-byoi-how-to-attach-to-domain.md +++ b//sagemaker/latest/dg/studio-updated-byoi-how-to-attach-to-domain.md @@ -53 +53 @@ New image - 9. Follow the rest of the instructions provided by the UI. + 9. Follow the rest of the instructions to attach your custom image. @@ -57 +57 @@ New image -During the instructions, the Amazon EFS mount path must be `/home/sagemaker-user`. +Ensure that you are using the application type consistent with your `Dockerfile`. For more information, see [Dockerfile samples](./studio-updated-byoi-specs.html#studio-updated-byoi-specs-dockerfile-templates). @@ -87 +87,5 @@ If you are unable to view your image version, you may need to create an image ve - 9. Verify your configurations and then choose **Next**. + 9. Follow the rest of the instructions to attach your custom image. + +###### Note + +Ensure that you are using the application type consistent with your `Dockerfile`. For more information, see [Dockerfile samples](./studio-updated-byoi-specs.html#studio-updated-byoi-specs-dockerfile-templates).