AWS Media Blog

Simplifying live streaming contribution with Amazon IVS

Live video isn’t just for media companies anymore. For example, ecommerce companies can offer customized applications to product sellers, which allows them to product features to their viewers. eLearning platforms can facilitate the collaboration between the participants and presenters, creating engaging virtual events.

Contributing live video to services like AWS Elemental MediaLive and Amazon Interactive Video Service (Amazon IVS) normally requires the use of professional-grade encoders or broadcast software, like Open Broadcaster Software (OBS). With the reference model in this post, we show you how to simplify video contribution using a web browser to send live streams to Amazon IVS. This removes the need to configure OBS tools, freeing up your time to focus on other projects.

Amazon IVS Simple Streaming

Amazon IVS Simple Streaming is a modular implementation with four main components:

  1. Broadcaster app: This application uses basic browser APIs to capture audio and video media, and a client web socket to send data to the server web socket. It uses AWS Amplify, which offers tools to build scalable full-stack applications.
  2. Amazon IVS: A managed live streaming solution that is quick and easy to set up and is ideal for creating interactive video experiences.
  3. Proxy video transwrap:  This application uses Node.js to open an HTTPS server for the WebSocket communication, and FFmpeg to transwrap the stream in RTMPS to Amazon IVS.
  4. Client player: This application uses Video.js player framework to decode the video streamed by Amazon IVS.

Solution architecture and components

Workflow overview:

  1. The user makes an HTTPS request the Broadcast application to an Amazon CloudFront distribution.
  2. Amazon CloudFront communicates to Amazon Simple Storage Service (Amazon S3) origin and retrieves the broadcaster app.
  3. The application asks for authentication and checks it against Amazon Cognito.
  4. The application gets parameters by communicating with API Gateway.
  5. API Gateway triggers an AWS Lambda Function.
  6. The AWS Lambda Function retrieves the data from an Amazon DynamoDB table.
  7. API Gateway triggers an AWS Lambda MetadaStore.
  8. AWS Lambda MetadaStore retrieves the public IP of the AWS Fargate tasks from the Amazon DynamoDB table backend.
  9. User starts a live stream, which is sent to the proxy transwrap running on AWS Fargate.
  10. Proxy transwrap transcodes the audio stream, repackages audio and video, and sends it via RTMPS to Amazon IVS.
  11. End users connect to Amazon IVS endpoints to watch the live stream.

Deployment steps


To deploy the transwrap container, we must install AWS Command Line Interface (AWS CLI) and the JQ tool. JQ is a command line tool for parsing JSON. Most of the AWS CLI command we use to deploy the backend relies on JSON parsing to build and adjust the files used to configure the required AWS services.

# If you are using macOS, do:
brew install jq

# If you are using Amazon Linux, do:
yum install jq

# If you are using Ubuntu Linux, do:
apt-get install jq

To build the integration with AWS components and host our web application, we use AWS Amplify. For more details on installing and configuring AWS Amplify, please visit the Amplify Documentation for React.

sudo npm install -g @aws-amplify/cli
  amplify configure

Step A – Frontend and APIs: WebRTC video capture

1. Clone the repository solution

git clone
cd aws-simple-streaming-webapp/frontend/
npm install
amplify init

As name for the environment, please select dev

? Enter a name for the environment dev
  ? Choose your default editor: Visual Studio Code
  Using default provider  awscloudformation
  ? Select the authentication method you want to use: AWS profile

With amplify init, the project and resources are initialized in the AWS Cloud environment.

As next step, we need to do an amplify push to deploy the resources in AWS Cloud.

amplify push

Note: This command deploys the following resources in your account:

  • API Gateway: To save and retrieve Amazon IVS parameters and Amazon ECS container availability information
  • DynamoDB: To store Amazon IVS and container server parameters
  • Lambda Functions: To check stored parameters and Amazon EventBridge information.

2. Publish and run the Broadcaster app

To have a full HTTPS communication, required for some access to the browser camera APIs, you can publish the app to host it in Amazon S3 and use a CloudFront distribution.

If you prefer to run the Broadcaster app locally, please see the project GitHub.

amplify publish

This command returns a CloudFront distribution. Please copy and open in your browser.

Your app is now online.

Now you can create your first account by clicking on Create account and sign up.

Step B – Proxy video transwrap with Amazon ECS container

The proxy transwapper is a compound of two containers running a Node.js web server and FFmpeg. The containers run on AWS Fargate for Amazon Elastic Container Service (Amazon ECS). AWS Fargate is a serverless compute engine for containers that work with Amazon ECS, and Amazon Elastic Kubernetes Service (Amazon EKS).

The services AWS CodeBuild and Amazon Elastic Container Registry build, store, and manage the proxy transwrap container images. AWS CodeBuild is a fully managed continuous integration service that compiles source code, runs tests, and produces software packages that are ready to deploy. Amazon Elastic Container Registry (Amazon ECR) is a fully managed container registry that makes it easy to store, manage, share, and deploy your container images and artifacts anywhere.

In Amazon ECS, you have three building blocks to run your containers successfully:

  1. Task definition: This is like a blueprint for your application, where you can define which container images to use and the resources that your container requires.
  2. Task: This is the instantiation of your task definition.
  3. Service: This launches and maintains a specified number of copies of the task definition in your cluster.

In this case, we have a service with two tasks, and each has its own public IP to receive the video stream via WebSocket.

To track each task public IP, we use Amazon EventBridge, AWS Lambda, and Amazon DynamoDB.

  • Amazon EventBridge: This is a serverless event bus that makes it easier to build event-driven applications at scale using events generated from your applications, integrated software as a service (SaaS) applications, and AWS services. In this case, we built a rule in Amazon EventBridge to track our tasks’ start and stop status and trigger the AWS Lambda function.
  • AWS Lambda: This is a serverless compute service that lets you run code without: provisioning or managing servers; creating workload-aware cluster scaling logic; maintaining event integrations; or managing runtimes. In this case, we built an AWS Lambda Function that, when triggered by the Amazon EventBridge, updates the public IP of the tasks in an Amazon DynamoDB table.
  • Amazon DynamoDB: This is a key-value and document database that delivers single-digit millisecond performance at any scale. It’s a fully managed, multi-Region, multi-active, durable database with built-in security, backup and restores, and in-memory caching for internet-scale applications. In this case, we use an Amazon DynamoDB table to store the metadata of the tasks. The public IP of the tasks is part of the metadata.

The backend deployment is built using a bash shell script located under simple-streaming-webapp/backend that runs AWS CLI commands to build the environment.

1. Deploy the backend environment

cd simple-streaming-webapp/backend

./ deploy all

Step C. Application setup

You can skip this task if you already have an Amazon IVS channel created. For more details, please visit Amazon IVS documentation.

1. Create a channel on Amazon IVS

./ ivs-webrtc

2. Copy and save the ingestEndpoint, streamKey value, and playbackUrl

Copy EndPoint: rtmps://

Copy StreamKey: sk_us-east-1_siFTKMADpmqe_dzUYPKAZjbE1lcrbQdudLA8sASWAqN

Copy playbackUrl:

3. Add the ingestEndpoint, streamKey value and playbackUrl to the interface

Step D. Test your live stream with your browser

Select your preferred camera and audio input and click on Go Live!

Step 3. Clean up: remove the provisioned AWS resources

1. Remove the Broadcaster application

If you need to remove the resources deployed by this sample, you can use the following command:

amplify delete

2. Remove the Transwrap proxy server

To remove the Transwrap proxy server, use the bash script

cd backend
./ clean all


In this blog post, we showed you how to create a serverless live stream reference architecture using AWS services Amazon IVS, AWS Lambda, Amazon EventBridge, Amazon DynamoDB, AWS Fargate, and AWS Amplify.

A reminder that this is a reference solution is not for use in a production environment, but is ideal for testing and accelerating your cloud adoption. Please reach your AWS representative, or here, for more information on architecting a custom solution for large-scale production-grade events.


If you have questions, feedback, or would like to get involved in discussions with other community members, visit the AWS Developer Forums: Media Services.