Assess source formats and packaging - AWS Elemental MediaLive

Assess source formats and packaging

Consult the following table for information about how to assess the source formats and packaging. Read across each row.

Information to obtain Verify the following
Number of sources that the content provider can provide. If you plan to implement a resiliency feature, make sure that your content provider can deliver the required inputs:
  • For automatic input failover, they must deliver two identical instances of the same source content.

  • For pipeline redundancy, they must deliver two identical instances of the same source content.

  • If you plan to implement both features, they must deliver four instances.

Delivery formats and protocols Find out what format and protocol the upstream system supports for delivery.

Make sure that this format is listed in the table in Supported input formats and protocols. If it is not listed, speak to your content provider about how they can add support for MediaLive.

Note that you don't need to verify this information for content delivered over CDI or content delivered from an AWS Elemental Link. MediaLive can always handle these input types.

Whether the upstream system is using the latest SDK Make sure that the content provider is using the latest version of the AWS CDI SDK on their upstream CDI source device.
Whether the source content is a stream or VOD asset Find out if the source content is a live stream or a VOD asset.

Make sure that MediaLive supports the delivery for the format that you identified. See the table in Support for live and file inputs.

Whether the content is encrypted MediaLive can ingest encrypted content only from HLS content.

If the source content is HLS and it is encrypted, make sure that it is encrypted in a format that MediaLive supports. See Handling encrypted source content in an HLS source. If MediaLive doesn't support the available encryption format, find out if you can obtain the content in unencrypted form.

Only if the source content is RTP, whether it includes FEC.

We recommend that the source content include FEC because it is less likely to result in an output that has visual disruptions.