1 Answer
- Newest
- Most votes
- Most comments
0
It could be your manifest file is too big or wrong format to be processed by Rekognition. Look at this doc pages about errors on rekognition https://docs.aws.amazon.com/rekognition/latest/customlabels-dg/debugging-datasets-terminal-errors.html https://docs.aws.amazon.com/rekognition/latest/dg/error-handling.html
Relevant content
- asked 6 years ago
- asked 2 years ago
- AWS OFFICIALUpdated 2 years ago

I am not using a manifest file but the s3 bucket created during the project creation. What i found also weird is that when creating a dataset from "Upload images from your computer" i did non encounter any error.
But when creating from s3 bucket in the developper tools i found this error also : Access to XMLHttpRequest at 'https://groundtruthlabeling.prod.eu-central-1.ml-platform.aws.a2z.com/RunGenerateManifestByCrawlingJob' from origin 'https://eu-central-1.console.aws.amazon.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. main.js:2
Also i don't think that the problem concern the wrong format because when using the s3 bucket created when using the "Image Classfication" demo project given by amazon i have the same issue.