Live streaming on AWS with MediaStore automatically configures AWS Elemental MediaLive, AWS Elemental MediaStore and Amazon CloudFront to ingest, encode, package and deliver a single source live stream through the AWS Cloud. The Solution provides 3 Encoding profiles to support 1080p through 288p HTTP live streaming (HLS) outputs and an Amazon CloudFront Dashboard to monitor the ingress and egress requests to MediaStore. For more details see the solution home page.
- Architecture Overview
- Encoding Profiles
- CloudWatch Dashboard
- Requirements
- Deployment
- Creating a custom Build
- License
The solution supports RTP Push, RTMP push, HLS and AWS Elemental Link input types. For more detialed instructions see the Implementation Guid on the solution home page.
- HD-1080p profile: 1920x1080, 1280x720, 960x540, 768x432, 640x360, 512x288
- HD-720p profile: 1280x720, 960x540, 768x432, 640x360, 512x288
- SD-540p profile: 960x540, 768x432, 640x360, 512x288
The solution includes an Amazon CloudWatch Dashboard that is configured to monitor the following MediaStore data points captured in Amazon CloudWatch Logs:
- Ingress TPM (Transaction Per Minute)
- Egress TPM (Transaction Per Minute)
- Put Object Latencies (Successful Requests)
- Get Object Latencies (Successful Requests)
- Ingress 2xx Status Count by Operation
- Ingress 4xx Status Count by Operation
- Ingress 5xx Status Count by Operation
- Egress 2xx Status Count by Operation
- Egress 4xx Status Count by Operation
- Egress 5xx Status Count by Operation
Before you launch the solution, you must create a MediaStore IAM Role and associated policy to allow MediaStore access to Amazon CloudWatch. The solution will launch successfully but without this Role the Amazon CloudWatch Dashboard deployed as part of the solution will not work. This is a one-time requirement, once created the role will authorize logging for all MediaStore Containers (if enabled). For details please see the MediaStore documentation
The solution can be deployed through the CloudFormation template available on the solution home page.
The CloudFormation template includes a lambda backed custom resource to configure MediaLive, define the MediaStore endpoint and create a UUID. To launch the solution the Lambda source code has to be deployed to an Amazon S3 bucket in the region you intend to deploy the solution.
- AWS Command Line Interface
- Node.js 12.x or later
Download or clone the repo and make the required changes to the source code.
Run unit tests to make sure added customization passes the tests:
cd ./deployment
chmod +x ./run-unit-tests.sh
./run-unit-tests.sh
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: my-bucket-us-east-1
aws s3 mb s3://my-bucket-us-east-1
Build the distributable:
chmod +x ./build-s3-dist.sh
./build-s3-dist.sh my-bucket live-streaming-on-aws-with-mediastore <version>
Notes: The build-s3-dist script expects the bucket name as one of its parameters, and this value should not include the region suffix
Deploy the distributable to the Amazon S3 bucket in your account:
aws s3 sync ./regional-s3-assets/ s3://my-bucket-us-east-1/live-streaming-on-aws-with-mediastore/<version>/ --acl public-read
aws s3 sync ./global-s3-assets/ s3://my-bucket-us-east-1/live-streaming-on-aws-with-mediastore/<version>/ --acl public-read
- Get the link of the live-streaming-on-aws-with-mediastore.template uploaded to your Amazon S3 bucket.
- Deploy the solution.
- This project is licensed under the terms of the Apache 2.0 license. See
LICENSE.