Implementing pipeline redundancy in a new channel - AWS Elemental MediaLive

Implementing pipeline redundancy in a new channel

To implement pipeline redundancy on a new channel, you must set up the inputs and the channel in a specific way.

To implement pipeline redundancy

  1. Decide if you will set up the inputs as standard inputs or single-pipeline inputs. For more information, see About input classes.

    You must set all the inputs to the same class.

  2. Create the input or inputs that you identified when you planned the workflow. For more information about creating inputs, see Working with inputs in AWS Elemental MediaLive.

    Make sure that you set the Channel and input class field in the input to the class that you identified:

    • If you choose STANDARD, two source fields appear.

    • If you choose SINGLE-PIPELINE, one source field appears.

    (This field doesn't appear for RTP inputs—these inputs are always set up with two endpoints.)

  3. Create the channel with these special notes:

    • On the Channel and input details page, for Channel class, choose a valid value. See the table below.

    • On the Attach input page, make sure that you attach valid inputs. See the table below.

About input classes

If you decide to implement input resiliency, you must decide which input class to use for the input. There are two input classes—standard and single-pipeline.

  • With a standard input, you can specify either one source or two source URLs.

  • With a single-pipeline input, you can specify only one source URL.

You can set up the combination of channel class and input class in one of the following ways:

  • Set up a standard channel with standard inputs

  • Set up a single-pipeline channel with standard inputs and upgrade potential

  • Set up a single-pipeline channel with single-pipeline inputs

Standard channel with standard inputs

With this setup, the channel has two pipelines. This setup supports pipeline redundancy.

Set up the input with two sources—you must specify two source URLs in the input, and the upstream system must provide two sources. If one pipeline fails, the channel continues to produce output from the other pipeline.

This setup lets you later downgrade the channel to a single-pipeline channel with minimum disruption. To downgrade, you stop the channel, change the channel class, and restart. At restart, MediaLive has one pipeline and it simply ignores the second source. For more information about downgrading, see Update the channel class—pipeline resiliency.

Single-pipeline channel with standard inputs and upgrade potential

With this setup, the channel has one pipeline. This setup doesn't support pipeline redundancy, but you can easily set it up later.

Even though the channel has only one pipeline, you set up the input with two URLs. But you set up the upstream system to provide only one source. The single source provides content to the single pipeline. If the single pipeline fails, the channel stops producing output.

This setup supports upgrade to a standard channel with minimum disruption. To upgrade, you stop the channel, change the channel class, and restart. You also start providing content to the second URL, which previously had been dormant. At restart, MediaLive has two pipelines and two sources, one for each pipeline. For more information about upgrading, see Update the channel class—pipeline resiliency.

Single-pipeline channel with single-pipeline inputs

With this setup, the channel has one pipeline. This setup doesn't support pipeline redundancy.

You set up the input with one URL. You set up the upstream system to provide only one source. The single source provides content to the single pipeline. If the single pipeline fails, the channel stops producing output.

You can upgrade this channel to a standard channel, but the procedure is disruptive. You must stop the channel, change the channel class, edit each input to specify two URLs, and restart the channel. For more information about upgrading, see Update the channel class—pipeline resiliency.

We recommend that you set up in this way only if you are sure you won't want to upgrade the channel to a standard channel. You might decide that you don't need to consider upgrade because you are providing channel resiliency through automatic input failover.

Valid combinations of channel class and input class

The following table describes all the value combinations of channel class and input class. Read each row as follows. The first cell specifies a channel class. The second cell specifies the classes of inputs you can attach to the channel. The third cell describes the results.

Channel class Class of the inputs Result
STANDARD All inputs are STANDARD MediaLive implements pipeline redundancy by creating two pipelines in the channel.
SINGLE-INPUT All inputs are SINGLE-INPUT MediaLive doesn't implement pipeline redundancy. The channel has one pipeline.
All inputs are STANDARD MediaLive doesn't implement pipeline redundancy. The channel has one pipeline. However, you have set up for easy upgrade to a standard channel.
Some inputs are STANDARD and some are SINGLE-PIPELINE MediaLive doesn't implement pipeline redundancy. The channel has one pipeline. You haven't set up for easy upgrade.