aws / aws/amazon-sagemaker-examples
tune_r_bring_your_own.ipyng notebook threw a permission error on the Publish step
- Dominant language
- Jupyter Notebook
- Stars
- 11k
- Forks
- 7k
- Avg merge
- 8h 29m
- Merged PRs (30d)
- 8
Description
WARNING! Using --password via the CLI is insecure. Use --password-stdin.
WARNING! Your password will be stored unencrypted in /home/ec2-user/.docker/config.json.
Configure a credential helper to remove this warning. See
https://docs.docker.com/engine/reference/commandline/login/#credentials-store
denied: User: arn:aws:sts::109225375568:assumed-role/AmazonSageMaker-ExecutionRole-20200213T151637/SageMaker is not authorized to perform: ecr:InitiateLayerUpload on resource: arn:aws:ecr:us-east-2:109225375568:repository/rmars
Contributor guide
Research direction
Open the tune_r_bring_your_own.ipyng notebook and inspect the Publish step that attempts to upload to the rmars ECR repository. Start by reviewing the displayed SageMaker execution-role error and verify the expected outcome by rerunning the Publish step without the ecr:InitiateLayerUpload denial.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, docker, jupyter-notebook
- Domain
- cloud, devops, machine-learning
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100