MediaPackage example - AWS Elemental MediaLive

MediaPackage example

This example shows how to set up the destination fields if the downstream system is an Akamai server.

Assume that you want to stream the curling game and to create three outputs: high, medium, and low bitrate.

Field Value
CDN settings in HLS settings section hls webdav

This is the type of connection that MediaPackage uses. Change the other CDN fields that appear, or keep the defaults.

URL in HLS group destination A section For example, https://62e3c93793c034c.mediapackage.us-west-2.amazonaws.com/in/v1/9378dje8/channel.

The URLs are the Input URLs from the channel in AWS Elemental MediaPackage. As discussed in Setting up the downstream system, the input in MediaPackage is identical to the output from AWS Elemental MediaLive. This input URL must already exist in MediaPackage.

Note that in MediaPackage, URLs always end in channel, so the base file name in MediaLive must be channel.

Credentials in HLS group destination A section MediaPackage accepts only authenticated requests, so you must enter a user name and a password that is known to MediaPackage. For the password, enter the name of the password stored on the AWS Systems Manager Parameter Store. Don't enter the password itself. For more information, see Requirements for AWS Systems Manager—Creating Password Parameters in Parameter Store .
URL in HLS group destination B section For example, https://60dei849783734c.mediapackage.us-west-2.amazonaws.com/in/v1/6da5ba717b357a/channel.
Credentials in HLS group destination B section Enter a user name and password for the URL for destination B. The credentials are probably the same for both URLs, but they might not be.
Name modifier in HLS outputs section

Choose Add output twice: two more Output lines are added to this section, for a total of three lines. In each line, enter a modifier: _high, _medium, and _low.

Directory Structure and Segments Per Subdirectory in Location section MediaPackage does not use these fields, therefore leave them blank.

As a result, files are created with the following names:

  • One main manifest: channel.m3u8

  • One child manifest for each output: channel_high.m3u8, channel_medium.m3u8, channel_low.m3u8

  • TS files for each output:

    • channel_high_000001.ts, channel_high_000002.ts, channel_high_000003.ts, and so on

    • channel_medium_000001.ts, channel_medium_000002.ts, channel_medium_000003.ts, and so on

    • channel_low_000001.ts, channel_low_000002.ts, channel_low_000003.ts, and so on

The files will be published to both URL inputs on MediaPackage.