2 Answers
- Newest
- Most votes
- Most comments
1
So the issue seemed to be related to the IAM role. The default role (ModelEndpoint-Role
) does not have access to write S3 files. It worked via the SDK since it uses another role in the sagemaker studio. I did not receive any error message about this.
answered 2 years ago
0
I had the same issue, and it was also related to IAM roles, but with a slight variation. When creating my Sagemaker domain I created a role with the suggested AmazonSageMakerFullAccess
role. This role does have permission to write to S3 buckets, but only to those fulfilling any of the the patterns:
"arn:aws:s3:::*SageMaker*",
"arn:aws:s3:::*Sagemaker*",
"arn:aws:s3:::*sagemaker*",
"arn:aws:s3:::*aws-glue*"
As my bucket did not contain either of these patterns, it wasn't allowed to write to it. After renaming my bucket to contain "sagemaker" it worked.
answered 3 months ago
Relevant content
- Accepted Answerasked 2 years ago
- asked a year ago
- Accepted Answer
- asked 6 months ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated a year ago