AWS Textract not accepting remote/non-aws document URL ??

Question

I am creating a component that extracts documents for its content. Since there are multipage pdf documents, as per my understanding I need to use 
‘**StartDocumentTextDetection**’ **async** method. This method requires the document to be part of a **S3 bucket in AWS**, Is this assumption correct? 
All my documents are in an external , non-aws location, which is basically a DELL EMC ObjectStorage. The document can be accessed via http as well.

**Can we pass byte array of an external document to the AWS Textract Async operations or a Url**? I can see bytes are accepted for Synchronous Textract operations, but not for Async. Please let me know.

Giulio Iannazzo · Answer

Hello,

For asynchronous operations like StartDocumentTextDetection, Amazon Textract requires the input document to be stored in an Amazon S3 bucket AND the asynchronous API does not support passing byte arrays or URLs directly as input. With that in mind, you have the following options: 
* Upload the document to an S3 bucket before processing (the simplest, if possible)
* If your documents are relatively small (under 5 MB) and you don't need the scalability of asynchronous processing, you can use the synchronous API (DetectDocumentText). The synchronous API accepts byte arrays, allowing you to process documents without storing them in S3

Hope that helps.

Cheers

AWS Textract not accepting remote/non-aws document URL ??

Relevant content