Channel class—implementing pipeline redundancy - AWS Elemental MediaLive

Channel class—implementing pipeline redundancy

You can set up a channel with two pipelines, to provide resiliency within the channel pipeline. You should decide whether to implement pipeline redundancy when you plan the workflow.

You set up for pipeline redundancy by setting the channel class:

  • Standard channel

  • Single-pipeline channel

You set up for pipeline redundancy by setting up the channel as a standard channel. The channel has two pipelines—pipelines 0 and 1. Both pipelines ingest, process the source content, and produce output. The downstream system handles output from one of the pipelines and ignores the other. If the current pipeline fails, the downstream system can detect that it is no longer receiving content and can switch to the other output. There is no disruption to the downstream system. MediaLive restarts the second pipeline within a few minutes.

If you don't want pipeline redundancy, you set up the channel as a single-pipeline channel. If that single pipeline fails, output to the downstream system stops.

Note

Before you decide to implement pipeline redundancy, you should read about automatic input failover, which is another form of channel resiliency. You might decide to implement one or both of these features.