Live input redundancy AWS Elemental MediaPackage processing flow - AWS Elemental MediaPackage

Live input redundancy AWS Elemental MediaPackage processing flow

Achieve input redundancy in MediaPackage by sending two streams to separate input URLs on a channel in MediaPackage. One of the streams becomes the primary, active source of content for the endpoints, while the other continues to passively receive content. If MediaPackage stops receiving content from the active stream, it switches over to the other input stream so that content playback isn't interrupted.

If you use MediaPackage with AWS Elemental MediaLive (for example), here is the flow of input redundancy:

  1. You create a channel in MediaPackage, as described in Creating a channel. When MediaPackage provisions the channel, it creates two input URLs for the channel. If you're not using input redundancy, you can send a stream to either input URL. There is no requirement that you send content to both URLs.


    When input redundancy became available, MediaPackage added a second input URL to existing channels and updated the existing URL to a new format. You can use either the existing URL or the new URLs for content input.

  2. You create an endpoint in MediaPackage as described in Creating an endpoint.


    If you use short output segments, depending on your playback device, you might see buffering when MediaPackage switches inputs. You can reduce buffering by using the time delay feature on the endpoint. Be aware that using a time delay introduces latency to end-to-end delivery of the content. For information about enabling time delay, see Creating an endpoint.

  3. You create an input and channel in AWS Elemental MediaLive, and you add a MediaPackage output group to the channel in MediaLive. For more information, see Creating a Channel from Scratch in the AWS Elemental MediaLive User Guide.

    If you use an HLS output group in AWS Elemental MediaLive, the input loss action on the HLS group's settings must be set to pause the output if the service doesn't receive input. If MediaLive sends a black frame or some other filler frame when it's missing input, then MediaPackage can't tell when segments are missing, and subsequently can't perform failover. For more information about setting the input loss action in MediaLive, see Fields for the HLS Group in the AWS Elemental MediaLive User Guide.


    If you use a different encoder (not AWS Elemental MediaLive) and you send two separate streams to the same channel in AWS Elemental MediaPackage, the streams must have identical encoder settings. Otherwise, input redundancy might not work correctly and playback could be interrupted if the inputs switch.

  4. You start the channel in AWS Elemental MediaLive to send the streams to MediaPackage.

  5. MediaPackage receives content on both of the input URLs, but only one of the streams is used for source content at a time. If the active stream is missing any segments, then MediaPackage automatically fails over to the other stream. MediaPackage continues to use this stream until failover is needed again.

    The formula that is used to determine if an input is missing segments is based on the segment lengths on the inputs and the endpoints. If an input is missing segments and quickly recovers, an endpoint with longer segment lengths won't switch inputs. This might result in different endpoints on the channel using different inputs (if one endpoint switches and the other doesn't). This is expected behavior and should not affect the content workflow.