{"id":2048,"date":"2022-04-04T18:42:37","date_gmt":"2022-04-04T18:42:37","guid":{"rendered":"https:\/\/salarydistribution.com\/machine-learning\/2022\/04\/04\/enable-amazon-kendra-search-for-a-scanned-or-image-based-text-document\/"},"modified":"2022-04-04T18:42:37","modified_gmt":"2022-04-04T18:42:37","slug":"enable-amazon-kendra-search-for-a-scanned-or-image-based-text-document","status":"publish","type":"post","link":"https:\/\/salarydistribution.com\/machine-learning\/2022\/04\/04\/enable-amazon-kendra-search-for-a-scanned-or-image-based-text-document\/","title":{"rendered":"Enable Amazon Kendra search for a scanned or image-based text document"},"content":{"rendered":"
\n

Amazon Kendra<\/a> is an intelligent search service powered by machine learning (ML). Amazon Kendra reimagines search for your websites and applications so your employees and customers can easily find the content they\u2019re looking for, even when it\u2019s scattered across multiple locations and content repositories within your organization.<\/p>\n

Amazon Kendra supports a variety of document formats, such as Microsoft Word, PDF, and text. While working with a leading Edtech customer, we were asked to build an enterprise search solution that also utilizes images and PPT files. This post focuses on extending the document support in Amazon Kendra so you can preprocess text images and scanned documents (JPEG, PNG, or PDF format)\u00a0 to make them searchable. The solution combines Amazon Textract<\/a> for document preprocessing and optical character recognition (OCR), and Amazon Kendra for intelligent search.<\/p>\n

With the new Custom Document Enrichment feature in Amazon Kendra, you can now preprocess your documents during ingestion and augment your documents with new metadata. Custom Document Enrichment allows you to call external services like Amazon Comprehend<\/a>, Amazon Textract, and Amazon Transcribe<\/a> to extract text from images, transcribe audio, and analyze video. For more information about using Custom Document Enrichment, refer to Enrich your content and metadata to enhance your search experience with custom document enrichment in Amazon Kendra<\/a>.<\/p>\n

In this post, we propose an alternate method of preprocessing the content prior to calling the ingestion process in Amazon Kendra.<\/p>\n

Solution overview<\/h2>\n

Amazon Textract is an ML service that automatically extracts text, handwriting, and data from scanned documents and goes beyond basic OCR to identify, understand, and extract data from forms and tables. Today, many companies manually extract data from scanned documents like PDFs, images, tables, and forms through basic OCR software that requires manual configuration, which often requires reconfiguration when the form changes.<\/p>\n

To overcome these manual and expensive processes, Amazon Textract uses machine learning to read and process a wide range of documents, accurately extracting text, handwriting, tables, and other data without any manual effort. You can quickly automate document processing and take action on the information extracted, whether it\u2019s automating loans processing or extracting information from invoices and receipts.<\/p>\n

Amazon Kendra<\/a> is an easy-to-use enterprise search service that allows you to add search capabilities to your applications so that end-users can easily find information stored in different data sources within your company. This could include invoices, business documents, technical manuals, sales reports, corporate glossaries, internal websites, and more. You can harvest this information from storage solutions like Amazon Simple Storage Service<\/a> (Amazon S3) and OneDrive; applications such as Salesforce, SharePoint, and ServiceNow; or relational databases like Amazon Relational Database Service<\/a> (Amazon RDS).<\/p>\n

The proposed solution enables you to unlock the search potential in scanned documents, extending the ability of Amazon Kendra to find accurate answers in a wider range of document types. The workflow includes the following steps:<\/p>\n

    \n
  1. Upload a document (or documents of various types) to Amazon S3.<\/li>\n
  2. The event triggers an AWS Lambda<\/a> function that uses the synchronous Amazon Textract API (DetectDocumentText<\/code>).<\/li>\n
  3. Amazon Textract reads the document in Amazon S3, extracts the text from it, and returns the extracted text to the Lambda function.<\/li>\n
  4. The data source on the new text file needs to be reindexed.<\/li>\n
  5. When reindexing is complete, you can search the new dataset either via the Amazon Kendra console or API.<\/li>\n<\/ol>\n

    The following diagram illustrates the solution architecture.<\/p>\n

    \"\"<\/a><\/p>\n

    In the following sections, we demonstrate how to configure the Lambda function, create the event trigger, process a document, and then reindex the data.<\/p>\n

    Configure the Lambda function<\/h2>\n

    To configure your Lambda function, add the following code to the function Python editor:<\/p>\n

    \n
    import urllib\nimport boto3\n\ntextract = boto3.client('textract')\ndef handler(event, context):\n\tsource_bucket = event['Records'][0]['s3']['bucket']['name']\n\tobject_key = urllib.parse.unquote_plus(event['Records'][0]['s3']['object']['key'])\n\t\n\ttextract_result = textract.detect_document_text(\n\t\tDocument={\n\t\t\t'S3Object': {\n\t\t\t\t'Bucket': source_bucket,\n\t\t\t\t'Name': object_key\n\t\t\t}\n\t\t})\n\tpage=\"\"\n\tblocks = [x for x in textract_result['Blocks'] if x['BlockType'] == \"LINE\"]\n\tfor block in blocks:\n\t\tpage += \" \" + block['Text']\n        \t\n\tprint(page)\n\ts3 = boto3.resource('s3')\n\tobject = s3.Object('demo-kendra-test', 'text\/apollo11-summary.txt')\n\tobject.put(Body=page)<\/code><\/pre>\n<\/p><\/div>\n
    We use the DetectDocumentText<\/a> API to extract the text from an image (JPEG or PNG) retrieved in Amazon S3.<\/p>\n
    Create an event trigger at Amazon S3<\/h2>\n
    In this step, we create an event trigger to start the Lambda function when a new document is uploaded to a specific bucket. The following screenshot shows our new function on the Amazon S3 console.<\/p>\n
    \"\"<\/a><\/p>\n
    You can also verify the event trigger on the Lambda console.<\/p>\n
    \"\"<\/a><\/p>\n
    Process a document<\/h2>\n
    To test the process, we upload an image to the S3 folder that we defined for the S3 event trigger. We use the following sample image.<\/p>\n
    \"\"<\/a><\/p>\n
    When the Lambda function is complete, we can go to the Amazon CloudWatch<\/a> console to check the output. The following screenshot shows the extracted text, which confirms that the Lambda function ran successfully.<\/p>\n
    \"\"<\/a><\/p>\n
    Reindex the data with Amazon Kendra<\/h2>\n
    We can now reindex our data.<\/p>\n
      \n
    1. On the Amazon Kendra console, under Data management <\/strong>in the navigation pane, choose Data sources<\/strong>.<\/li>\n
    2. Select the data source demo-s3-datasource<\/code>.<\/li>\n
    3. Choose Sync now<\/strong>.<\/li>\n<\/ol>\n
      The sync state changes to Synching - crawling<\/code>.<\/p>\n
      \"\"<\/a><\/p>\n
      When the sync is complete, the sync status changes to Succeeded<\/code> and the sync state changes to Idle<\/code>.<\/p>\n
      \"\"<\/a><\/p>\n
      Now we can go back to the search console and see our faceted search in action.<\/p>\n
        \n
      1. In the navigation pane, choose Search console<\/strong>.
        \"\"<\/a><\/li>\n<\/ol>\n
        We added metadata for a few items; two of them are the ML algorithms XGBoost and BlazingText.<\/p>\n
          \n
        1. Let\u2019s try searching for Sagemaker<\/code>.
          \"\"<\/a><\/li>\n<\/ol>\n
          Our search was successful, and we got a list of results. Let\u2019s see what we have for facets.<\/p>\n
            \n
          1. Expand Filter search results<\/strong>.<\/li>\n<\/ol>\n
            We have the category<\/code> and tags<\/code> facets that were part of our item metadata.<\/p>\n
              \n
            1. Choose BlazingText<\/strong> to filter results just for that algorithm.
              \"\"<\/a><\/li>\n
            2. Now let\u2019s perform the search on newly uploaded image files. The following screenshot shows the search on new preprocessed documents.
              \"\"<\/a><\/li>\n<\/ol>\n
              Conclusion<\/h2>\n
              This blog will be helpful in improving the effectiveness of search results and search experience. You can use Amazon Textract to extract text from scanned images that are added as metadata and later available as facets to interact with the search results. This is just an illustration of how you can use AWS native services to create a differentiated search experience for your users. This also helps in unlocking the full potential of your knowledge assets.<\/p>\n
              For a deeper dive into what you can achieve by combining other AWS services with Amazon Kendra, refer to\u00a0Make your audio and video files searchable using Amazon Transcribe and Amazon Kendra<\/a>,\u00a0Build an intelligent search solution with automated content enrichment<\/a>, and other posts on the\u00a0Amazon Kendra blog<\/a>.<\/p>\n
              \n
              About of Author<\/h3>\n
              \"\"<\/a>Sanjay Tiwary<\/strong> is a Specialist Solutions Architect AI\/ML. He spends his time working with strategic customers to define business requirements, provide L300 sessions around specific use cases, and design ML applications and services that are scalable, reliable, and performant. He has helped launch and scale the AI\/ML powered Amazon SageMaker service and has implemented several proofs of concept using Amazon AI services. He has also developed the advanced analytics platform as a part of the digital transformation journey.<\/p>\n
                     \n      <\/div>\n","protected":false},"excerpt":{"rendered":"
              https:\/\/aws.amazon.com\/blogs\/machine-learning\/enable-amazon-kendra-search-for-a-scanned-or-image-based-text-document\/<\/p>\n","protected":false},"author":0,"featured_media":2049,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[3],"tags":[],"_links":{"self":[{"href":"https:\/\/salarydistribution.com\/machine-learning\/wp-json\/wp\/v2\/posts\/2048"}],"collection":[{"href":"https:\/\/salarydistribution.com\/machine-learning\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/salarydistribution.com\/machine-learning\/wp-json\/wp\/v2\/types\/post"}],"replies":[{"embeddable":true,"href":"https:\/\/salarydistribution.com\/machine-learning\/wp-json\/wp\/v2\/comments?post=2048"}],"version-history":[{"count":0,"href":"https:\/\/salarydistribution.com\/machine-learning\/wp-json\/wp\/v2\/posts\/2048\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/salarydistribution.com\/machine-learning\/wp-json\/wp\/v2\/media\/2049"}],"wp:attachment":[{"href":"https:\/\/salarydistribution.com\/machine-learning\/wp-json\/wp\/v2\/media?parent=2048"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/salarydistribution.com\/machine-learning\/wp-json\/wp\/v2\/categories?post=2048"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/salarydistribution.com\/machine-learning\/wp-json\/wp\/v2\/tags?post=2048"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}