Back to catalog / Agent workflows
Process an auto claim with damage images and policy checks
Feed claim PDFs/images into the sample workflow, update a versioned claim record, and apply policy rules to determine status.
Goal
Produce a vehicle-damage estimate and claim status with an audit history using synthetic insurance data.
Steps
- Before deployment, confirm the CDK account is a test environment, notification email is yours, and review planned S3/DynamoDB/Lambda/SNS resources. [src10-aws-process-auto-claim-with-damage-image-and-policy-check]
- Upload one PDF/image from sample-claims and observe a PENDING claim enriched with policy, incident, and damage details. [src10-aws-process-auto-claim-with-damage-image-and-policy-check]
- Add evidence one file at a time; check the 30-day filing rule, required-document tracking, and damage estimate, then inspect final status and SNS notification. [src10-aws-process-auto-claim-with-damage-image-and-policy-check]
How to verify
DynamoDB claim versions should retain each incremental evidence update; verify PENDING/APPROVED/DENIED rules and notification target against known samples.
Troubleshooting
If a PDF is not recognized, inspect the S3-triggered Lambda logs; for a wrong status, check policy KB rules and incident date rather than editing adjudication.
Permissions
Prerequisites
- AWS test account, CDK/Docker/Python dependencies, Bedrock model access, synthetic sample-claims, and an address for SNS test email.
Permissions
- CDK deploys real S3, DynamoDB, Lambda, Bedrock KB, and SNS resources; uploads store files, update claims, and send email, incurring costs.
Limitations
Use synthetic data only; sample status is not an insurance determination, and final approval/payment must remain in insurer processes.
Pinned upstream source
- Repository
- aws-samples/sample-multimodal-claims-processing-recommendation-system
- File path
- README.md
- Pinned commit
6cb782225e391fb5251b88a37b4c38e31a5858aa- Source checked
- 2026-10-14 · Reviewed against the pinned upstream source
Repository metrics
These values describe the upstream repository, not popularity or likes for an individual skill or playbook.
- Stars
- Not collected
- Forks
- Not collected
- Observed at
- Not collected
No metrics snapshot is available yet.
License: Amazon permissive sample license (custom)
Main topic
Turn ecommerce campaign materials into a reviewable weekly brief