AWS sagemaker documentation change
Summary
Updated section headers and clarified role policy requirements for building and attaching custom images to SageMaker domains.
Security assessment
The changes are minor wording updates and clarifications about role permissions. While permissions are security-related, there is no indication of a specific security issue or new security feature being documented.
Diff
diff --git a/sagemaker/latest/dg/code-editor-custom-images-provide-access.md index 9e8f7e9a6..ea2ac3c73 100644 --- a/sagemaker/latest/dg/code-editor-custom-images-provide-access.md +++ b/sagemaker/latest/dg/code-editor-custom-images-provide-access.md @@ -5 +5 @@ -Step 1: Create the DockerfileStep 2: Build the DockerfileStep 3: Push the image to the Amazon Elastic Container Registry repositoryStep 4: Attach image to the Amazon SageMaker AI domain of your usersStep 5: Have your users access the image from their Code Editor space +Step 1: Create the DockerfileStep 2: Build the imageStep 3: Push the image to the Amazon Elastic Container Registry repositoryStep 4: Attach image to the Amazon SageMaker AI domain of your usersStep 5: Have your users access the image from their Code Editor space @@ -55 +55 @@ For sample Dockerfiles in the correct format, see [Dockerfile samples](./code-ed -## Step 2: Build the Dockerfile +## Step 2: Build the image @@ -113 +113 @@ Use the following procedure to attach the image to a SageMaker domain through th - 1. Create a SageMaker AI image. The role ARN must have the `AmazonSageMakerFullAccess` policy attached. + 1. Create a SageMaker AI image. The `AmazonSageMakerFullAccess` policy must be attached to your role as you use the following AWS CLI commands.