Creating a Transport Stream (TS) file input - AWS Elemental MediaLive

Creating a Transport Stream (TS) file input

Create your input before you create the channel that ingests the input.

For information about the files that MediaLive supports as Transport Stream (TS) file inputs, see Reference: Supported input containers and codecs.

You can set up a TS file source as a single-class or a standard-class input. You should have already read Implementing pipeline redundancy, to decide the class of channel and class of input that you want.

To create a TS file input

  1. You should have already arranged with the video content provider to set up the upstream system for your content. Make sure that the operator of the upstream system gives you the following information:

    • The full URLs of the locations where MediaLive will pull the TS files from. For example:



  2. If this input is being used in a multiple-input channel, you should have decided whether to set it up as a static input or a dynamic input. You might need to modify the URLs you obtained from the upstream system:

    • If the input is a static input, don't modify the URLs.

    • If the input is a dynamic input, set up the URL as an optional absolute portion and a required variable portion ($urlPath$). For examples, see the table after this procedure.

      We recommend that you use the format <protocol>/$urlPath$.

  3. Open the MediaLive console at

  4. In the navigation pane, choose Inputs.

  5. On the Inputs page, choose Create input.

  6. Complete the Input details section:

    • Input name – enter a name.

    • Input type – choose TS.

  7. In the Input class section, choose the class for this input:



  8. In the Input sources section, enter the URLs you previously obtained:

    • If the input is a standard-class input, complete both fields, to provide two URLs.

    • If the input is a single-class input, complete the first field with the URL that you obtained and leave the second field empty.

    If the upstream system requires that you provide user credentials, you must also enter the user name and password key for accessing the location. These credentials are stored on the Systems Manager Parameter Store. For more information, see About the feature for creating password parameters.

  9. In the Tags section, create tags if you want to associate tags with this input. For more information, see Tagging AWS Elemental MediaLive resources.

  10. Choose Create.

    MediaLive creates the input and adds it to the list of inputs. The input specifies either one or two sources. The sources don't appear in the list, but if you choose the Name link, the details page shows them.

    When you start the channel, MediaLive will connect to the upstream system at this source location or locations and pull the content:

    • For a standard channel, MediaLive expects the upstream system to provide two sources and will therefore attempt to pull from both source locations.

    • For a single-pipeline channel, MediaLive expects the upstream system to provide one source and will therefore attempt to pull from one source location.

Formats for the URL in a dynamic input

The following table describes the different formats for the URL in a dynamic input.

Format Description Example Example of the $urlPath$
<protocol>/$urlPath$ URL has only the protocol in the absolute portion s3ssl://$urlPath$ DOC-EXAMPLE-BUCKET/my-movie.ts
<protocol and path>/$urlPath$ URL has the protocol and path in the absolute portion emsssl://$urlPath$ my-movie.ts
$urlPath$ URL has only the variable portion $urlPath$ s3ssl://DOC-EXAMPLE-BUCKET/my-movie.ts