Guidelines for channel class - AWS Elemental MediaLive

Guidelines for channel class

Before you decide to set up a standard channel, in order to implement pipeline redundancy, you should be aware of all the requirements:

  • Contact the downstream system to determine if the downstream system can handle two sets of identical outputs from MediaLive and to switch as required.

    If the downstream system doesn't have this ability, there is not much advantage to setting up as a standard channel.

  • Contact the upstream system to determine if they can send you two source streams for each input. If the upstream system can't provide two sources, you can't set up as a standard channel.

    Furthermore, if you have more than one upstream system for the channel, every upstream system must be capable of providing two sources. If every upstream system can't do this, you can't set up as a standard channel.

  • Weigh the benefit of a standard channel against the difference in processing charges for a standard channel compared to a single-pipeline channel. For information about charges for channels, see https://aws.amazon.com/medialive/pricing/.

  • If you are sending output to AWS Elemental MediaPackage, you might want to implement pipeline redundancy in order to support input redundancy in MediaPackage. MediaLive will send two identical outputs to the two inputs on the MediaPackage channel. If there is a pipeline failure in MediaLive, MediaPackage has logic to seamlessly switch the input it uses.

  • If you decide not to implement pipeline redundancy, you should decide if you want to leave open the option of implementing it later on.

    Or if you do decide to implement pipeline redundancy, you should decide if you want to leave open the option of removing it later on.

    In both cases, you must make sure to set up the input class appropriately. See About input classes and make a note of the input class that you want to use.