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
+49Lines changed: 49 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,6 +5,55 @@ SPDX-License-Identifier: MIT-0
5
5
6
6
## [Unreleased]
7
7
8
+
## [0.3.21]
9
+
10
+
### Added
11
+
12
+
-**Claude Sonnet 4.5 Haiku Model Support**
13
+
- Added support for Claude Haiku 4.5
14
+
- Available for configuration across all document processing steps
15
+
16
+
-**X-Ray Integration for Error Analyzer Agent**
17
+
- Integrated AWS X-Ray tracing tools to enhance diagnostic capabilities of the error analyzer agent
18
+
- X-Ray context enables better distinction between infrastructure issues and application logic failures
19
+
- Added trace ID persistence in DynamoDB alongside document status for complete traceability
20
+
- Enhanced CloudWatch error log filtering for more targeted error analysis
21
+
- Simplified CloudWatch results structure for improved readability and analysis
22
+
- Updated error analyzer recommendations to leverage X-Ray insights for more accurate root cause identification
23
+
24
+
-**EU Region Support with Automatic Model Mapping**
25
+
- Added support for deploying the solution in EU regions (eu-central-1, eu-west-1, etc.)
26
+
- Automatic model endpoint mapping between US and EU regions for seamless deployment
27
+
- Comprehensive model mapping table covering Amazon Nova and Anthropic Claude models
28
+
- Intelligent fallback mappings when direct EU equivalents are unavailable
29
+
- Quick Launch button for eu-central-1 region in README and deployment documentation
30
+
- IDP CLI now supports eu-central-1 deployment with automatic template URL selection
31
+
- Complete technical documentation in `docs/eu-region-model-support.md` with best practices and troubleshooting
32
+
33
+
### Changed
34
+
35
+
-**Migrated Evaluation from EventBridge Trigger to Step Functions Workflow**
36
+
- Moved evaluation processing from external EventBridge-triggered Lambda to integrated Step Functions workflow step
37
+
-**Race Condition Eliminated**: Evaluation now runs inside state machine before WorkflowTracker marks documents COMPLETE, preventing premature completion status when evaluation is still running
38
+
-**Config-Driven Control**: Evaluation now controlled by `evaluation.enabled` configuration setting instead of CloudFormation stack parameter, enabling runtime control without stack redeployment
39
+
-**Enhanced Status Tracking**: Added EVALUATING status to document processing pipeline for better visibility of evaluation progress
40
+
-**UI Improvements**: Added support for displaying EVALUATING status in processing flow viewer and "NOT ENABLED" badge when evaluation is disabled in configuration
41
+
-**Consistent Pattern**: Aligns evaluation with summarization and assessment patterns for unified feature control approach
42
+
43
+
44
+
-**Migrated UI Build System from Create React App to Vite**
45
+
- Upgraded to Vite 7 for faster build times
46
+
- Updated to React 18, AWS Amplify v6, react-router-dom v6, and Cloudscape Design System
47
+
- Reduced dependencies and node_modules size
48
+
- Implemented strategic code splitting for improved performance
49
+
- Environment variables now use `VITE_` prefix instead of `REACT_APP_` for local development
50
+
51
+
### Fixed
52
+
53
+
-**IDP CLI Code Cleanup and Portability Improvements** - [#91](https://github.com/aws-solutions-library-samples/accelerated-intelligent-document-processing-on-aws/issues/91), [#92](https://github.com/aws-solutions-library-samples/accelerated-intelligent-document-processing-on-aws/issues/92)
54
+
- Removed dead code from previous refactors in batch_processor.py (51 lines)
55
+
- Replaced hardcoded absolute paths with dynamic path resolution in rerun_processor.py for cross-platform compatibility
Copy file name to clipboardExpand all lines: Dockerfile.optimized
+4Lines changed: 4 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,10 @@
1
1
# Optimized Dockerfile for Lambda functions with minimal dependencies
2
2
# This builds each function with ONLY the dependencies it needs
3
3
4
+
# checkov:skip=CKV_DOCKER_3: "The Dockerfile uses the official AWS Lambda Python base image (public.ecr.aws/lambda/python:3.12-arm64), which already configures the appropriate non-root user for Lambda execution"
5
+
# checkov:skip=CKV_DOCKER_2: "The Dockerfile.optimized is specifically designed for AWS Lambda container images, which don't use Docker HEALTHCHECK instructions."
6
+
7
+
4
8
FROM public.ecr.aws/lambda/python:3.12-arm64 AS builder
| US West (Oregon) | us-west-2 |[](https://us-west-2.console.aws.amazon.com/cloudformation/home?region=us-west-2#/stacks/create/review?templateURL=https://s3.us-west-2.amazonaws.com/aws-ml-blog-us-west-2/artifacts/genai-idp/idp-main.yaml&stackName=IDP)|
72
72
| US East (N.Virginia) | us-east-1 |[](https://us-east-1.console.aws.amazon.com/cloudformation/home?region=us-east-1#/stacks/create/review?templateURL=https://s3.us-east-1.amazonaws.com/aws-ml-blog-us-east-1/artifacts/genai-idp/idp-main.yaml&stackName=IDP)|
73
+
| EU Central (Frankfurt) | eu-central-1 |[](https://eu-central-1.console.aws.amazon.com/cloudformation/home?region=eu-central-1#/stacks/create/review?templateURL=https://s3.eu-central-1.amazonaws.com/aws-ml-blog-eu-central-1/artifacts/genai-idp/idp-main.yaml&stackName=IDP)|
73
74
74
75
3. When the stack deploys for the first time, you'll receive an email with a temporary password to access the web UI
75
76
4. Use this temporary password for your first login to set up a permanent password
@@ -138,6 +139,7 @@ To update an existing GenAIIDP stack to a new version:
Copy file name to clipboardExpand all lines: config_library/pattern-1/lending-package-sample/config.yaml
+111-2Lines changed: 111 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -67,6 +67,7 @@ summarization:
67
67
system_prompt: >-
68
68
You are a document summarization expert who can analyze and summarize documents from various domains including medical, financial, legal, and general business documents. Your task is to create a summary that captures the key information, main points, and important details from the document. Your output must be in valid JSON format. \nSummarization Style: Balanced\\nCreate a balanced summary that provides a moderate level of detail. Include the main points and key supporting information, while maintaining the document's overall structure. Aim for a comprehensive yet concise summary.\n Your output MUST be in valid JSON format with markdown content. You MUST strictly adhere to the output format specified in the instructions.
69
69
evaluation:
70
+
enabled: true
70
71
llm_method:
71
72
top_p: '0.1'
72
73
max_tokens: '4096'
@@ -242,7 +243,19 @@ agents:
242
243
- Extract log_group, log_stream, and events data from tool response
243
244
- Show complete log group and log stream names without truncation
244
245
- Present actual log messages from events array in code blocks
245
-
246
+
247
+
ANALYSIS GUIDELINES:
248
+
- If has_performance_issues is false, focus on application logic errors
249
+
- Use service timeline to rule out infrastructure bottlenecks
250
+
- Service response times help eliminate timeout-related causes
251
+
- For application errors use CloudWatch error messages for recommendations
252
+
253
+
ROOT CAUSE DETERMINATION:
254
+
- Start with Step Function failure details (most specific)
255
+
- Validate with CloudWatch error logs (most detailed)
256
+
- Use X-Ray to categorize as infrastructure vs. application issue
257
+
- DynamoDB provides supporting timeline context only
0 commit comments