
🛡️ Insurance · Deployment · Pro
A cloud deployment for an insurance claims platform: web and mobile channels, claims microservices, document AI and a data lake.
Deployment diagrams are part of Pro. Anyone can view this one; generating and editing it needs Pro.
Drawing diagram…
Insurance claims platform deployment on AWS: customers and agents come in through CloudFront and an Application Load Balancer. Claims, policy and payment microservices run on Amazon EKS. Uploaded documents go to Amazon S3 and are processed by an OCR and document AI service on AWS Lambda. Data is in Amazon Aurora PostgreSQL, events stream through Amazon MSK (Kafka) into an S3 data lake queried with Amazon Athena.
flowchart TD
subgraph EDGE["Edge"]
CF["Amazon CloudFront"]
WAF["AWS WAF"]
end
subgraph APP["Application (Amazon EKS)"]
ALB["Application Load Balancer"]
CLAIMS["Claims Service"]
POLICY["Policy Service"]
PAYOUT["Payout Service"]
end
subgraph DATA["Data"]
AUR[("Amazon Aurora PostgreSQL")]
S3[("Amazon S3 Documents")]
MSK["Amazon MSK Kafka"]
LAKE[("S3 Data Lake")]
ATH["Amazon Athena"]
end
OCR["AWS Lambda OCR and Document AI"]
CF --> WAF --> ALB
ALB --> CLAIMS
ALB --> POLICY
CLAIMS --> AUR
POLICY --> AUR
CLAIMS --> S3
S3 --> OCR --> CLAIMS
CLAIMS --> PAYOUT
CLAIMS --> MSK --> LAKE --> ATHThe states of an insurance claim from first notice of loss to payment or closure, including investigation and appeals.
The core system of an insurer: quoting, underwriting, policy issue, billing and claims, used by customers, agents and underwriters.
How a life or health insurance proposal is underwritten: automated rules, medical tests where needed, and the underwriter's decision.
How a customer buys motor insurance online: quote, add-ons, vehicle and previous-policy checks, payment and instant policy issue.
A relational schema for an insurer: customers, policies, coverages, insured objects, premiums, claims and payments.
How an insurer scores incoming claims for fraud: data enrichment, rules, an ML model and a special investigation unit queue.