You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+30Lines changed: 30 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,6 +5,36 @@ SPDX-License-Identifier: MIT-0
5
5
6
6
## [Unreleased]
7
7
8
+
## [0.4.7]
9
+
10
+
### Added
11
+
12
+
-**MCP Integration Cross-Region Support for QuickSuite Integration**
13
+
- Added cross-region support for QuickSuite integration enabling MCP connectivity across multiple AWS regions: us-east-1, us-west-2, eu-west-1, ap-southeast-2
14
+
15
+
### Fixed
16
+
17
+
-**Stack deployment failure due to MCP Integration IAM Permissions - [GitHub Issue #154](https://github.com/aws-solutions-library-samples/accelerated-intelligent-document-processing-on-aws/issues/154)**
18
+
- Fixed missing permissions in AgentCoreGatewayManagerFunctionRole by creating the AgentCoreGateway execution role explicitly in the CloudFormation template instead of dynamically in the Lambda function
- Added intermediate decompression lambda to handle document decompression before invoking custom post-processing lambdas
22
+
-**Root Cause**: After introducing document compression, the post-processing lambda hook was receiving compressed documents in the EventBridge payload, forcing external lambdas to import `idp_common` package and handle decompression manually
23
+
-**Solution**: New `PostProcessingDecompressor` lambda function intercepts EventBridge events, decompresses documents using `Document.load_document()`, and invokes custom post-processors with decompressed payload
-**Enhanced Bedrock Error Handling for Agent Companion Chat**
27
+
- Implemented robust error handling system for Bedrock API errors in Agent Companion Chat feature with automatic retry and graceful degradation
28
+
-**Automatic Retry with Exponential Backoff**: Configured boto3 with adaptive retry mode (3 attempts) and exponential back-off to prevent service overload
29
+
-**User-Friendly Error Messages**: Created `BedrockErrorMessageHandler` to convert technical errors into clear, actionable messages for service unavailable (503), throttling (429), access denied (403), validation errors (400), timeouts (408), and quota exceeded scenarios
30
+
-**Sub-Agent Error Handling**: When sub-agents (Analytics, Error Analyzer, Code Intelligence) encounter Bedrock errors, the orchestrator continues gracefully without crashing, only displaying the first error to avoid duplicates while allowing other sub-agents to complete
You are a multimodal document classification expert that analyzes business documents using both visual layout and textual content. Your task is to classify single-page documents into predefined categories based on their structural patterns, visual features, and text content. Your output must be valid JSON according to the requested format.
824
824
825
825
<variables>
826
-
DOCUMENT_TEXT: OCR-extracted text content from the document page that provides textual information for classification
827
-
DOCUMENT_IMAGE: Visual representation of the document page that provides layout, formatting, and visual structure information
828
-
CLASS_NAMES_AND_DESCRIPTIONS: List of valid document types with their descriptions that the document must be classified into
826
+
<document-ocr-data>: OCR-extracted text content from the document page that provides textual information for classification
827
+
<document-image>: Visual representation of the document page that provides layout, formatting, and visual structure information
828
+
<document-types>: List of valid document types with their descriptions that the document must be classified into
829
829
</variables>
830
830
task_prompt: >-
831
831
<reasoning-guidelines>
@@ -837,6 +837,10 @@ classification:
837
837
- Provide specific evidence from both visual and textual analysis
838
838
</reasoning-guidelines>
839
839
840
+
<document-types>
841
+
{CLASS_NAMES_AND_DESCRIPTIONS}
842
+
</document-types>
843
+
840
844
<output-format>
841
845
Return your classification as valid JSON following this exact structure:
0 commit comments