Automated meeting notes, translation, and transcription with generative AI
This Guidance shows how you can add generative artificial intelligence (generative AI) to your virtual meetings to translate languages, summarize conversations, and capture live insights. As virtual meetings become more prevalent, retaining all the information presented can be challenging for participants. The Live Meeting Assistant (LMA) on AWS collects speaker audio and metadata from a browser-based meeting app, softphone app, or audio source. It then uses large language models (LLMs) to generate customizable transcriptions, insights, and summaries, helping participants derive more value from every meeting.
Please note: [Disclaimer]
Architecture Diagram

[Architecture diagram description]
Step 1
Your Live Meeting Assistant (LMA) administrator installs the LMA browser extension as a plugin to their browser. Meeting participants join the meeting app.
Get Started

Deploy this Guidance
Sample code
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.
-
Operational Excellence
CloudFormation creates a stack in the AWS Management Console, providing an infrastructure as code mechanism that enables updates to the deployed solution. QnABot on AWS, nested within the stack, can quickly create a meeting assistant interface, and you can version it to enable updates as new features become available. Lambda divides functions into smaller, event-driven components so that you can more efficiently track the flow of data and isolate potential issues in call processing.
-
Security
Amazon Cognito is tightly integrated within the AWS services that comprise the LMA outlined in this Guidance. The service provides authentication and authorization capabilities, so that only authorized users can access and interact with the LMA web application and the supporting Lambda functions. Through this Amazon Cognito integration, the system maintains a secure and controlled provisioning of access to its various components, aligned with the principle of least privilege, enhancing the overall confidentiality and reliability of the meeting data processed by the LMA application.
-
Reliability
Application Load Balancer routes traffic requests to the call processing functions and prevents the overload of any one container. Fargate scales audio processing as needed during call events, and its default health monitoring functionality quickly alerts you to any failure of the audio processing component. AWS AppSync provides a managed GraphQL service to provide a serverless, automatically scaling API to the frontend. Kinesis Data Streams synchronously replicates data across three Availability Zones, providing high availability and data durability.
-
Performance Efficiency
CloudFront caches assets that serve the web application on the edge so that they can quickly respond to user requests. It also supports using WebSocket, a TCP-based protocol that is useful when you need long-lived bidirectional connections between clients and servers. As a result, it can support real-time audio processing.
-
Cost Optimization
Unlike in monolithic applications, which might require you to run and pay for unnecessary resources, this Guidance breaks call processing into smaller components, using discreet Lambda functions. Additionally, the DynamoDB on-demand throughput mode conserves read and write capacity and provides pay-per-request pricing so that you only pay for what you use. Finally, Fargate scales audio processing functions up and down with demand, conserving resources and optimizing costs.
-
Sustainability
By using on-demand services so that you only use the resources you need, this Guidance conserves computational resources and minimizes your workload’s environmental impact. For example, CloudFront caches web assets on the edge, reducing the need to serve requests from the origin. Kinesis Data Streams is fully managed and can stream massive amounts of data on demand. And DynamoDB scales database functions on-demand so that its provisioned capacity matches your application’s needs.
Related Content

Live Meeting Assistant (LMA) with Amazon Transcribe, Amazon Bedrock, and Knowledge Bases for Amazon Bedrock
Live Meeting Assistant with Amazon Transcribe, Amazon Bedrock, and Knowledge Bases for Amazon Bedrock
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.