Skip to main content

Guidance for Livestreams Hosted with Digital Humans on AWS

Overview

This Guidance helps you build a digital human that can livestream content on demand through cloud rendering, cloud livestreaming, and artificial intelligence (AI) services. You can use this Guidance to quickly build and manage the system that will control the digital human’s language, voice, and intonation based on business scenarios. Additionally, you can push the livestream video to a variety of terminals based on Amazon Interactive Video Service (Amazon IVS). The livestream is distributed through edge networks and has the ability to scale to up to 10,000 viewers.

How it works

These technical details feature an architecture diagram to illustrate how to effectively use this solution. The architecture diagram shows the key components and their interactions, providing an overview of the architecture's structure and functionality step-by-step.

Deploy with confidence

Ready to deploy? Review the sample code on GitHub for detailed deployment instructions to deploy as-is or customize to fit your needs.

Go to sample code

Well-Architected Pillars

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.

CloudWatch continually monitors the steps and performance of Lambda and API Gateway. This helps you to know when steps are blocked or have the potential to be blocked in addition to which services are causing a delay in response. Monitoring through CloudWatch helps you optimize your system over time.

Read the Operational Excellence whitepaper 

AWS Identity and Access Management (IAM) access replaces credential access between services to improve system security. With IAM, you should limit role access to the minimum permissions within the system without storing any credential information in the code and configuration. Amazon S3 blocks public access, and you can access S3 buckets with Amazon CloudFront , which protects unauthorized access from public networks.

Read the Security whitepaper 

API Gateway, Lambda, and DynamoDB support a serverless architecture. Serverless services can automatically scale horizontally based on the actual workload. This improves reliability by reducing the chance of application failure within the livestream system.

Read the Reliability whitepaper 

Amazon IVS helps the system provide high-performance service to the end user. Amazon IVS achieves this through real-time streaming with latency that can be under 300 milliseconds from host to viewer, allowing you to create an engaging live video experience. Amazon IVS also provides high concurrency, allowing digital human livestream audiences of up to 10,000 viewers.

Read the Performance Efficiency whitepaper 

DynamoDB has a Time to Live (TTL) feature that can delete expired items from your DynamoDB table, reducing overall costs. For Lambda, your cost is based on the amount of time your code runs. You can also use timeout features with Lambda to minimize ephemeral storage.

Read the Cost Optimization whitepaper 

Amazon S3 provides lifecycle configuration, a set of rules that define actions for Amazon S3 to apply to a group of objects. You can set an “expiration” feature, which configures Amazon S3 to automate the removal of retired data, reducing storage resources and effectively minimizing your workload’s environmental impact.

Read the Sustainability whitepaper 

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.