1 Answer
- Newest
- Most votes
- Most comments
0
Does your existing IAM User/Role that you are using to create the labeling job have access to the s3 bucket? Based on your comment you already have provided access to the IAM Role of the labeling job but you also need to make sure that the existing IAM User/Role you are using to create the labeling job has access as well.
answered 2 years ago
Relevant content
- asked 3 months ago
- asked a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
Not quite sure whether it would give the error message you're seeing, but did you make sure you set up the required CORS permissions on your bucket?
Does your existing IAM User/Role that you are using to create the labeling job have access to the s3 bucket? Based on your comment you already have provided access to the IAM Role of the labeling job but you also need to make sure that the existing IAM User/Role you are using to create the labeling job has access as well.
I'm having the same issue. I've granted full access to the IAM role with AmazonS3FullAccess, AmazonSageMakerFullAccess, AmazonSageMakerGroundTruthExecution, and added CORS permissions to the bucket, but I continue to see this permission error