- Newest
- Most votes
- Most comments
Dear Customer,
Thank you so much for reaching to us. I understand that you followed our AWS Comprehend documentation for annotating PDF’s, in-order to annotate your training PDFs in SageMaker Ground Truth. Further yourself and your team is working as private annotators, in-order to facilitate the task appropriately. However when you and your co-workers login to the page for annotation in Sagemaker Ground truth, the webpage does not list any pdfs and the page is blank. Hence you were looking for guidance in resolving this issue.
Thank you so much for providing the details.
To further better assist you on this issue, can you please create a Support Ticket to AWS. Below link will assist you to create the Support Ticket. [+]https://docs.aws.amazon.com/awssupport/latest/user/case-management.html [+]https://console.aws.amazon.com/support/home#/case/create
—While creating the support ticket, we kindly request you to provide the below information
- Use-case description.
- Ground Truth Job ARN details
- Screen-shots of the issue you are facing.
- Log Files for the Ground truth Job(This logs from your labeling jobs appear in Amazon CloudWatch under the /aws/sagemaker/LabelingJobs group.).
The reason behind this ask is this would help us to understand your use-case in a better way, further if we might need to deep dive and access the job created from our internal tools, we will have more visibility through the support ticket.
Rest assured we will do everything best in our abilities to assist you on this issue. Thanks.
I have found out that when this tutorial is carried out on windows, you get an error after creating the job, which is the labeling portal UI is blank. This happens because for some reason in the s3 bucket created here, when you go here comprehend-semi-structured-docs-ui-template/ and then inside the folder of your job, you will see that the name of S3 folders is having some formatting issue. Instead of '/' that represents folder layer, the bucket name is using '' and making the request failed. Thus, it is recommended to rearrange or rename your s3 bucket folders accordingly and this solves the issue.
Relevant content
- asked 2 years ago
- Accepted Answerasked a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago