2 Answers
0
First of all, please do not make your S3 bucket public. Doing this way, anybody in the world can access your bucket. Please remove public access immediately from your S3 bucket.
Now coming to the actual problem, while you create the groundtruth labeling job, you need to provide an execution role. That execution role must have access to s3 bucket where you are storing the unlabeled data. If you want to simplify things, you can add a policy to the execution role, which provides access to any s3 bucket in your account. While this will solve it temporarily, as a best practice, please always use only least required permissions in your role policies. Hope this helps.
answered 6 months ago
Relevant questions
Trigger and/or monitor Automated Data Labeling Job
asked 2 months agoObjects Not Visible Within S3 Bucket for GroundTruth Labeling Job
asked 6 months agoError in Creation of dataset using Manifest File in AWS Rekognition
asked 10 months agoS3 Bucket cannot be reached in GroundTruth Labeling
asked 6 months agoNetwork error when creating a labeling job - S3 bucket in input dataset location cannot be reached
asked 2 months agoError when creating new labeling job in Ground Truth
asked 4 months agoCustom entity annotation with groundtruth
asked 3 years agoTraining Job Failed "ClientError: Mask image is not a 8-bit"
asked 2 years agoProvide Autopilot own data
asked 2 years agoGroundTruth Text labeling tasks failing
asked 4 months ago
I have already created the execution role as shown in 4:02 in the tutorial link: https://www.youtube.com/watch?v=_FPI6KjDlCI&t=217s
Somehow it does not work for my case.
Another strange thing is that at 3:25 in the video, I was able to see my bucket, but I could not see the contents of my bucket. I was still able to successfully create a manifest file however.