Update the channel class—pipeline resiliency - AWS Elemental MediaLive

Update the channel class—pipeline resiliency

You can change the channel class of an existing channel in order to enable or disable pipeline redundancy in the channel. For information the channel class, see Update the channel class—pipeline resiliency.

Changing the channel to a single-pipeline channel

You can change a standard channel to single-pipeline, to remove one of the pipelines in the channel and to remove pipeline redundancy.

To change the channel class, the channel must be idle (not running).

To change the channel class to a single-pipeline channel

  1. On the Channels page, choose the channel. (Don't choose the channel name.)

  2. On the menu, choose Actions, Other channel actions, Update channel class to SINGLE_PIPELINE.

  3. In the dialog box, choose Confirm. MediaLive performs the following actions:

    • It removes the second pipeline (pipeline 1) in the channel.

    • It removes the second destination address in each output group.

    • It doesn't remove the second endpoint on the inputs. The inputs aren't changed in any way. Instead, when you restart the channel, MediaLive simply ignores the second endpoint.

    While MediaLive is performing these actions, the channel has a status of UPDATING. When the update is completed, the status changes to IDLE.

  4. You might want to notify the upstream system for each push input that it no longer needs to push input to the second endpoint. You might want to notify the downstream system for each output group that it should no longer expect output at its second destination.

Changing the channel class to standard

You can change a single-pipeline channel to a standard channel, to implement pipeline redundancy. To change the channel class, the channel must be idle (not running).

There are two procedures for changing the channel class. Choose the procedure that matches how you planned the inputs and the channel.

  • Option A – You set up a single-pipeline channel with standard inputs and upgrade potential. In this case, you completed both source URLs. Therefore when you upgrade the channel, you don't need to edit the inputs to include a URL for the new pipeline.

  • Option B – You set up a single-pipeline channel with single-pipeline inputs. In this case, you specified only one URL. Therefore when you upgrade, you must edit all of the inputs to include a URL for the second pipeline.

Changing the class – option A

Follow this procedure if you set up a single-pipeline channel with standard inputs and upgrade potential. In this case, you completed both source URLs. Therefore when you upgrade the channel, you don't need to edit the inputs to include a URL for the new pipeline.

To change the channel class

  1. Obtain a second destination address for each output group. Each address is at the downstream systems of each output group.

    For example, if the channel has an HLS output group (with an HTTPS server as its downstream system) and an Archive output group (with an Amazon S3 bucket as its downstream system), you must enter the URL to a new destination address at the HTTPS server, and the URL to a new folder in the Amazon S3 bucket.

    Plan these destinations now, in the same way as you planned the destination addresses when you originally set up the channel. You might need to contact the owner of each downstream system.

  2. On the Channels page, choose the channel. (Don't choose the channel name.)

  3. On the menu, choose Actions, Other channel actions, Update channel class to STANDARD.

  4. In the dialog box, choose Confirm.

  5. On the Update channel class to STANDARD page, enter the destination addresses that you identified in step 1. There is one field for each output group in the channel.

  6. Choose Submit. MediaLive updates the channel and creates a new pipeline called pipeline 1. The source for this pipeline is the previously dormant URL. When you start the channel, MediaLive ingests content from that URL, produces output, and sends the output to the new destinations in every output group.

Changing the class—option B

Follow this procedure if you set up a single-pipeline channel with single-pipeline inputs. In this case, you specified only one URL. Therefore when you upgrade, you must edit all of the inputs to include a URL for the second pipeline.

To change the channel class

  1. Obtain a second destination address for each output group. Each address is at the downstream systems of each output group.

    For example, if the channel has an HLS output group (with an HTTPS server as its downstream system) and an archive output group (with an Amazon S3 bucket as its downstream system), you must enter the URL to a new destination address at the HTTPS server, and the URL to a new folder in the Amazon S3 bucket.

    Plan these destinations now, in the same way as you planned the destination addresses when you originally set up the channel. You might need to contact the owner of each downstream system.

  2. Edit the URLs in every input to include a second URL, for the second source that will provide content to the newly added pipeline.

    • For a push input, edit the input to include an address for the second input source. Give that address to the owner of the upstream system, so that they can push source content to that address. You should also find out from the upstream system the address that the new source will be pushed from. Make sure that this address is covered by the input security group for the channel.

    • For a pull input, obtain a new address from the owner of the downstream system. Edit the input to include that address. After the second pipeline is created, MediaLive will be able to pull the second source content (for the second pipeline).

  3. On the Channels page, choose the channel. (Don't choose the channel name.)

  4. On the menu, choose Actions, Other channel actions, Update channel class to STANDARD.

  5. In the dialog box, choose Confirm.

  6. On the Update channel class to STANDARD page, enter the destination addresses that you identified in step 1. There is one field for each output group in the channel.

  7. Choose Submit. MediaLive updates the channel and creates a new pipeline called pipeline 1. When you start the channel, MediaLive sends the output from this pipeline to the new destinations in every output group.