This Guidance demonstrates how to implement an intelligent conversational AI chatbot that uses insurance policy, billing, and claims data from mainframe applications to receive and deliver responses using natural language. With change data capture (CDC) technology, the data is replicated from the mainframe application to AWS using low-latency, high-throughput data pipelines. The conversational AI application then reads the replicated data from the AWS data stores and provides responses to customer inquiries, such as claim status, policy status, and next premium due dates, in natural language. This Guidance can enhance your customer’s experience, reduce call center volume, and optimize your operational costs. While tailored for the insurance industry, the underlying technology used throughout this Guidance can be adopted for other industries requiring mainframe data integration on AWS.

Note: [Disclaimer]

Architecture Diagram

[Architecture diagram description]

Download the architecture diagram PDF 

Well-Architected Pillars

The AWS Well-Architected Framework helps you understand the pros and cons of the decisions you make when building systems in the cloud. The six pillars of the Framework allow you to learn architectural best practices for designing and operating reliable, secure, efficient, cost-effective, and sustainable systems. Using the AWS Well-Architected Tool, available at no charge in the AWS Management Console, you can review your workloads against these best practices by answering a set of questions for each pillar.

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.

  • Amazon CloudWatch logging capabilities facilitate the tracing and monitoring of the CDC and publishing processes. Additionally, CloudWatch logs will capture relevant information pertaining to the invocation of the Amazon Bedrock Agent and the Claim Status API, which is implemented using Lambda. CloudWatch can also assist in the troubleshooting of any issues related to the invocation of the Claim Status API through the Lambda function. Furthermore, the AWS CloudTrail service enables comprehensive operational and risk auditing, as well as governance and compliance monitoring, for your AWS accounts. 

    Read the Operational Excellence whitepaper 
  • The AWS Identity and Access Management (IAM) policies governing this Guidance are scoped down to the minimum required permissions for Amazon Bedrock, Lambda, and the AWS Mainframe Modernization services. By restricting the IAM policies to the least privileged access levels, unauthorized access to resources by any user, role, or AWS service is limited.

    Read the Security whitepaper 
  • This Guidance uses fully managed AWS services, including Amazon Bedrock for the conversational AI agent, Lambda for API invocation, DynamoDB for the claims data store, and Amazon MSK for publishing the CDC records from the mainframe application. By utilizing these fully managed services, the reliability of the conversational AI agent, the Claim Status API function, the data store, and the CDC queueing process is inherently managed and maintained by AWS.

    Read the Reliability whitepaper 
  • With this Guidance using fully managed AWS services, the conversational AI agent, Claim Status API, data store, and CDC publishing queue will automatically scale based on the number of users accessing the system to check their claim status. In addition, the CloudWatch logging and alarm features will enable the monitoring of performance and the identification of any potential bottlenecks, not only for the Precisely Apply Engine agent, but also for other AWS services used in this architecture, such as Amazon Bedrock, Lambda, DynamoDB, and Amazon MSK.

    Read the Performance Efficiency whitepaper 
  • The Amazon Bedrock and Lambda services used within this Guidance will automatically scale, both in and out, in response to the user load on the conversational AI agent. Similarly, the DynamoDB data store and Amazon MSK service will scale automatically based on the CDC data being applied from the mainframe by the Precisely Apply Engine agent. The automated scaling of the AWS services used in this architecture helps to optimize costs by dynamically adjusting resource consumption to match actual usage patterns.

    Read the Cost Optimization whitepaper 
  • AWS continuously innovates to counterbalance its operational carbon footprint through energy-efficient data center design, reduced reliance on fossil fuels, renewable energy procurement, and carbon offset initiatives. By utilizing fully managed AWS services which automatically scale in and out based on usage, the energy consumption can be effectively controlled. Additionally, the right-sizing of Amazon Elastic Compute Cloud (Amazon EC2) instances further contributes to the mitigation of your carbon footprint.

    Read the Sustainability whitepaper 
[Content Type]

[Title]

This [blog post/e-book/Guidance/sample code] demonstrates how [insert short description].

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.

Was this page helpful?