Skip to content

Use an ECR repo name containing sagemaker for streamlined IAM #3

@athewsey

Description

@athewsey

Hi all & thanks for the sample!

The default AmazonSageMakerFullAccess managed policy grants access to upload container images to ECR, but only if they match arn:aws:ecr:*:*:repository/*sagemaker*.

I suggest changing the REPO_NAME in notebook 6 to include sagemaker, to make it less likely that users run in to permissions issues there?

For e.g. I got an AccessDeniedError in a test environment, and changed my copy to:

REPO_NAME = "sagemaker-swift-json-vlm-finetuned"

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions