Creating an MP4 pull input - AWS Elemental MediaLive

Creating an MP4 pull input

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

For information about the files that MediaLive supports as MP4 inputs, see Supported input types and upstream systems.

To create an MP4 pull input

  1. From the upstream system, obtain the full URLs of the locations where MediaLive will pull the MP4 file from. You need two URLs for an input in a standard channel, or one URL for an input in a single-pipeline channel.

    • For an upstream system that uses HTTP or HTTPS, enter an HTTP or HTTPS URL. For example:

      https://203.0.113.13/fillervideos/oceanwaves.mp4 and

      https://203.0.113.54/fillervideos/oceanwaves.mp4

    • For a file that is stored on Amazon S3, enter the protocol as s3 or s3ssl, and then enter the bucket name and object for the manifest. With MediaLive, the Amazon S3 bucket name must not use dot notation. For example, mycompany-videos is acceptable but mycompany.videos isn't.

      For example:

      s3://fillervideos/main/oceanwaves.mp4 and s3://fillervideos/redundant/oceanwaves.mp4

  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 later in this section.

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

  3. Open the MediaLive console at https://console.aws.amazon.com/medialive/.

  4. In the navigation pane, choose Inputs.

  5. On the Inputs page, choose Create input.

  6. In the Input details section, for Input name, enter a name.

  7. For Input type, choose MP4.

  8. In the Channel and input class section, choose the class for this input:

    • STANDARD

    • SINGLE-PIPELINE

    For more information, see Channel class—implementing pipeline redundancy.

  9. In the Input sources section, enter the URLs (or the modified URLs) that you previously obtained:

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

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

  10. 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.

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

  12. 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 s3://$urlPath$ movies/my-movie.mp4
<protocol and path>/$urlPath$ URL has the protocol and path in the absolute portion emsssl://movies/$urlPath$ my-movie.mp4
$urlPath$ URL has only the variable portion $urlPath$ s3://movies/my-movie.mp4