Deployment considerations - Live Streaming on AWS with MediaStore

Deployment considerations

Encoding profiles

The Live Streaming on AWS with MediaStore solution configures AWS Elemental MediaLive with one of three progressive, 30 frames per second encoding profiles. Choose one of the following encoding profiles.

  • HD-1080p profile: 1920x1080, 1280x720, 960x540, 768x432, 640x360, 512x288

  • HD-720p profile: 1280x720, 960x540, 768x432, 640x360, 512x288

  • SD-540p profile: 960x540, 768x432, 640x360, 512x288

MediaStore lifecycle policy

This solution deploys an AWS Elemental MediaStore storage container with an attached lifecycle policy. By default, stored files will be deleted after five minutes, to clean up the expired HLS segments from the live stream. For more details, see lifecycle policy in the AWS Elemental MediaStore documentation.

Demo content

The solution includes a link to a demo HTTP Live Streaming (HLS) stream hosted in an Amazon Simple Storage Service (Amazon S3 bucket, which enables you to test the solution without having to set up and configure a live stream. Deploying the solution with default parameters, will launch the demo.

Solution updates

To continue using this solution with the latest features and improvements, you must deploy the latest version of the AWS CloudFormation template as a new stack. This solution does not support updating an existing stack. For information to deploy the latest AWS CloudFormation template as a new stack, refer to Launch the stack. After the new stack completes deployment, we recommend uninstalling the previous version to save on costs. Refer to Appendix E for uninstallation instructions.

Regional deployment

This solution uses AWS Elemental MediaLive and MediaStore services, which are currently available in specific AWS Regions only. Therefore, you must launch this solution in an AWS Region where these services are available. For the most current service availability by region, see AWS service offerings by Region.

To use an AWS Elemental Link device as an input, you must launch this solution in the AWS Region where the device is configured.