Step 3: Set up the output names and destination paths - AWS Elemental MediaLive

Step 3: Set up the output names and destination paths

After you have designed the output names and destination paths, you can set up the HLS output group.

To set the destination for most downstream systems

  1. Complete the URL fields in the HLS group destinations section. Specify two destinations if the channel is set up as a standard channel, or one destination if it is set up as a single-pipeline channel.

    Portion of the destination URL Example Comment
    protocol http:// The protocol that you obtained from the downstream system.
    domain 203.0.113.55 The IP address or host/domain that you obtained from the downstream system.
    path /sports/delivery/

    The path that you obtained from the downstream system.

    Always terminate with a slash.

    base_filename curling

    The name that you and the downstream system agreed on.

    Don't terminate the base_filename with a slash.

  2. In each HLS group destination section, complete the Credentials section as appropriate for the protocol that you chose.

    Protocol of the destination URL How to complete the Credentials
    http:// Typically, you don’t enter credentials
    https:// In each Credentials section, enter a user name and a password that is known to the downstream system. 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 .

    s3://

    s3ssl://

    Leave both the Credentials sections blank. MediaLive has permission to write to the Amazon S3 bucket via the trusted entity. Someone in your organization should have already set up these permissions. For more information, see Step 1: Determine the Access Requirements.
    mediastoressl:// Leave both the Credentials sections blank. MediaLive has permission to write to the Amazon S3 bucket via the trusted entity. Someone in your organization should have already set up these permissions. For more information, see Step 1: Determine the Access Requirements.
  3. In the HLS outputs section, complete the Name modifier for each output, according to your design.

  4. (Optional) In the HLS outputs section, complete the Segment modifier for outputs, according to your design.

  5. In the CDN settings section, choose the option that applies to the' downstream system.

  6. If the downstream system gave you values to configure the connection, enter those values in the fields in the CDN settings section.

To set the destination for MediaPackage

  1. Complete the HLS group destination A section:

    • For URL, enter the URL of the input in the MediaPackage channel. For example:

      https://62e3c93793c034c.mediapackage.us-west-2.amazonaws.com/in/v1/9378dje8/channel

    • For Credentials, enter the input user name. 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 .

  2. If you are setting up a standard channel, in HLS group destination B, enter the information for the other input. If you are setting up a single channel, leave this section empty.

  3. In the Location section, don't change any of the fields.

  4. In the HLS outputs section, complete Name modifier as follows:

    • For an output that contains video (and possibly other streams), you typically describe the video. For example, _high or _1920x1080_5500kpbs (to describe the resolution and the bitrate).

    • For an output that contains only audio or only captions, you typically describe the audio or captions. For example, _aac or _webVTT.

    • It’s a good idea to include an underscore, to clearly separate the base_filename from the name_modifer.

    • The name_modifier can include data variables.

  5. (Optional) In the HLS outputs section, complete Segment modifier as follows:

    • The segment_modifier is optional, but we strongly recommend that you include it.

    • A typical use case for this modifier is to use a data variable to create a timestamp, to prevent segments overriding each other if the channel restarts. For example, assume that you include the timestamp $t$_. Segment 000002 might have the name curling_120028_000002. If the output restarts a few minutes later (which causes the segment counter to restart), the new segment 000002 will have the name curling_120039_000002. The new file won't overwrite the file for the original segment 000002. Some downstream systems might prefer this behavior.

  6. In HLS settings, for CDN settings, choose Hls webdav.