Live Streaming on AWS for CN APAC

How to implement Live streaming on AWS at scale leveraging AWS Elemental MediaLive, MediaPackage and Amazon CloudFront. This repo uses the source code for the AWS solution Live Streaming on AWS as a basis and modifies it where apropriate.

Architecture Overview

AWS Elemental MediaLive
Is configured to ingest 2 live feeds and transcode the content into multiple adaptive bitrate HLS content. The solution can be configured to ingest RTP RTMP and HLS streams and will apply 1 of 3 encoding profiles which include bitrates of 720p through 270p. The encoding profile is set at launch and is based on the source resolution (See Encoding Profiles below).

AWS Elemental MediaPackage
Ingests the MediaLive Output and package the Live stream into HLS, DASH and MSS formats that are delivered through 3 MediaPackage custom endpoints.

Amazon CloudFront
Is configured with the three MediaPackage custom endpoints as the Origins for the distribution. CloudFront then enable the live stream content to be delivered globally and at scale.

Optional Demo Deployment
As part of the CloudFormation template a Demo HTML preview player is deployed to an Amazon S3 bucket which is a single page HTML/JavaScript application that will playback the HLS, DASH and MMS streams. In addition, the solution can be configured to ingest a Demo HLS feed hosted on AWS.

Adding --

SPEKE License Server
Handles AES-128 encryption of HLS live streams.

Deployment

The solution is deployed using a CloudFormation template with a lambda backed custom resource, available in both NodeJS and Python. For details on deploying the solution please see the details on the Solution home page: Live Streaming on AWS

Encoding Profiles

To solution Configures AWS Elemental MediaLive with one of three encoding profiles based on the source resolution defined at launch as a CloudFormation parameter. The three options are 1080, 720, 540 and correspond to the following encoding profiles:

1080p Profile::
REMOVED to save bitrate costs

1080p@6500kbps, 720p@5000kbps, 720p@3300kbps, 540p@2000kbps, 432p@1200kbps, 360p@800kbps, 270@400kbps, 234p@200kbps.

720p Profile::
720p@5000kbps, 720p@3300kbps, 540p@2000kbps, 432p@1200kbps, 360p@800kbps, 270@400kbps, 234p@200kbps.

540p Profile::
540p@2000kbps, 432p@1200kbps, 360p@800kbps, 270@400kbps, 234p@200kbps.

The profiles are defined in JSON and and can be found in:

  source/custom-resource-js/lib/medialive/encoding-profiles/
  source/custom-resource-py/encoding-profiles/

Source code

source/custom-resources-js::
A NodeJS based Lambda function used as a custom resource for deploying MediaLive and MediaPackage resources through CloudFormation.

source/custom-resources-py::
A Python based Lambda function used as a custom resource for deploying MediaLive and MediaPackage resources through CloudFormation.

source/console::
A single page application used to demo playback of the live stream. This is deployed to an AWS S3 bucket as part of the CloudFormation deployment.

Creating a custom Build

To solution can be deployed through the CloudFormation template available on the solution home page: Live Streaming on AWS. To make changes to the solution, download or clone this repo, update the source code and then run the deployment/build-s3-dist.sh script to deploy the updated Lambda code to an S3 bucket in your account.

Pre-requirements:

At Turner, most deployment if not all, will be based on the use of Python 3

• AWS Command Line Interface
• Node.js 8.x or Python 3.x

1. Create an Amazon S3 Bucket.

The CloudFormation template is configured to pull the Lambda deployment packages from Amazon S3 bucket in the region the template is being launched in. Create a bucket in the desired region with the region name appended to the name of the bucket. eg: for us-east-1 create a bucket named: -ap-southeast-1

aws s3api create-bucket --bucket aws-live-poc-ap-southeast-1 --region ap-southeast-1 --output json --create-bucket-configuration LocationConstraint=ap-southeast-1

{
    "Location": "http://aws-live-poc-ap-southeast-1.s3.amazonaws.com/"
}

2. Create the deployment packages:

Run the build-s3-dist.sh script, passing in 2 variables:

• CODEBUCKET = the name of the S3 bucket (do NOT include the -region extension)
• CODEVERSION = this will be the subfolder containing the code.

CODEBUCKET=aws-live-poc CODEVERSION=0.0.1

This will:

• copies the console files to ./deployment/dist/.
• copies the CloudFormation template to ./deployment/dist/ and updates the source code mappings.
• zips and copies the source code to ./deployment/dist/

Example:

  cd deployment/
  ./build-s3-dist.sh aws-live-poc 0.0.1

This will deploy the source code to:

  s3://bucket-us-east-1/live-streaming-on-aws/0.0.1/

And update the CloudFormation template mappings:

Mappings:
  SourceCode:
    General:
      S3Bucket: aws-live-poc
      KeyPrefix: live-streaming-on-aws/0.0.1

3. Upload the Code to Amazon S3.

Use the AWS CLI to sync the lambda code and demo console files to amazon S3:

  cd deployment/
  aws s3 sync .dist/ s3://aws-live-poc-ap-southeast-1/live-streaming-on-aws/0.0.1/

4. Launch the CloudFormation template.

Launch the updated CloudFormation template from deployment/dist/ folder.

aws cloudformation create-stack --stack-name 'aws-live-POC-CN' --region ap-southeast-1 --template-body file://live-streaming-on-aws.yaml  --capabilities CAPABILITY_IAM --output json

---