Overview
This Guidance demonstrates how to facilitate Intelligent Document Processing to accelerate your business processes and reduce the overall costs associated with your document workflows. The process begins with documents uploaded to a storage bucket, triggering an asynchronous Amazon Textract detection job. The extracted text is then classified and enriched using artificial intelligence and machine learning (AI/ML) technology, with the results stored in the storage bucket. Automated validation and review steps are performed next, with human review facilitated through Amazon Augmented AI (A2I) when necessary. Finally, the verified data is stored in a fully managed NoSQL database service where it is readily available for downstream applications.
How it works
These technical details feature an architecture diagram to illustrate how to effectively use this solution. The architecture diagram shows the key components and their interactions, providing an overview of the architecture's structure and functionality step-by-step.
Deploy with confidence
Ready to deploy? Review the sample code on GitHub for detailed deployment instructions to deploy as-is or customize to fit your needs.
Well-Architected Pillars
The architecture diagram above is an example of a Solution created with Well-Architected best practices in mind. To be fully Well-Architected, you should follow as many Well-Architected best practices as possible.
Related content
Intelligent document processing with AWS AI services: Part 1
This blog post demonstrates how intelligent document processing (IDP) helps automate information extraction from documents of different types and formats, quickly and with high accuracy.
Disclaimer
The sample code; software libraries; command line tools; proofs of concept; templates; or other related technology (including any of the foregoing that are provided by our personnel) is provided to you as AWS Content under the AWS Customer Agreement, or the relevant written agreement between you and AWS (whichever applies). You should not use this AWS Content in your production accounts, or on production or other critical data. You are responsible for testing, securing, and optimizing the AWS Content, such as sample code, as appropriate for production grade use based on your specific quality control practices and standards. Deploying AWS Content may incur AWS charges for creating or using AWS chargeable resources, such as running Amazon EC2 instances or using Amazon S3 storage.
References to third-party services or organizations in this Guidance do not imply an endorsement, sponsorship, or affiliation between Amazon or AWS and the third party. Guidance from AWS is a technical starting point, and you can customize your integration with third-party services when you deploy the architecture.
Did you find what you were looking for today?
Let us know so we can improve the quality of the content on our pages