AWS Elemental MediaConnect
User Guide

Creating a Flow to Use as an AWS Elemental MediaLive Input

You can use AWS Elemental MediaConnect flows as inputs to AWS Elemental MediaLive. The process is the same as any other time that you create a new flow. However, the settings that you choose for your flow are dependent on how the flows will be used in MediaLive. See the sections below for setup information for redundancy and input switching.

Redundancy setup

Each AWS Elemental MediaLive input requires two sources for redundancy. As a result, you create two flows for each MediaLive input. For this setup, remember the following:

  • Choose a different Availability Zone for each flow. (If you choose the same Availability Zone for both flows, MediaLive doesn't allow you to create the input.)

  • Specify flow names that will help you differentiate the flows from one another. For example, name your primary flow sports_event_A and your backup flow sports_event_B. Using a naming convention will help you match the flows to the input pipelines in MediaLive.

  • After you create each flow, make a note of the flow ARN. You need this value when you create your input in MediaLive. For example:

    arn:aws:mediaconnect:us-west-1:111122223333:flow:1:1-23aBC45dEF67hiJ8-12AbC34DE5fG:sports_event_A

    arn:aws:mediaconnect:us-west-1:111122223333:flow:1:2-3aBC45dEF67hiJ8k-2AbC34DE5fGa6:sports_event_B

The following illustration shows redundant flows that are both used as sources for the same AWS Elemental MediaLive input.


                    This illustration shows redundant AWS Elemental MediaConnect flows that are both used as sources for the same MediaLive input. The first flow
                        (sports_event_A) is created in Availability Zone 1a of the us-west-1 Region. The second flow (sports_event_B) is created in
                        Availability Zone 1b of the us-west-1 Region.

Input switching setup

In AWS Elemental MediaLive, you can specify multiple inputs to be used in sequence. MediaLive requires a redundant source for each input. As a result, you create two flows for each MediaLive input. For this setup, remember the following:

  • Choose the same Availability Zone for each flow. In addition, for each flow you need to create a redundant flow in a different Availability Zone.

  • Specify flow names that will help you differentiate the flows from one another. Remember, for each sequential flow you need a redudant flow as backup. This means that if you have two sequential flows, you need to create four flows total. Consider adding markers to your flow names to help you remember the order (such as part1 and part2) and to help you differentiate your primary and backup flows (such as A and B). Using a naming convention will help you match the flows to the input pipelines in MediaLive.

  • After you create each flow, make a note of the flow ARN. You need this value when you create your input in MediaLive. For example:

    arn:aws:mediaconnect:us-west-1:111122223333:flow:1:1-23aBC45dEF67hiJ8-12AbC34DE5fG:sports_event_part1_A

    arn:aws:mediaconnect:us-west-1:111122223333:flow:1:2-3aBC45dEF67hiJ8k-2AbC34DE5fGa6:sports_event_part2_A

    arn:aws:mediaconnect:us-west-1:111122223333:flow:1:3-4aBC56dEF78hiJ90-4de5fG6Hi78Jk:sports_event_part1_B

    arn:aws:mediaconnect:us-west-1:111122223333:flow:1:9-8aaa77bbb66ccc5D-4eee55ff6ggg5:sports_event_part2_B

The following illustration shows the setup for two flows (part1 and part2) that serve as sequential inputs to an AWS Elemental MediaLive channel. Both flows are created in Availability Zone 1a of the us-west-1 Region. For redundancy, these same flows are also created in Availability Zone 1b of the us-west-1 Region.


                This illustration shows redundant AWS Elemental MediaConnect flows that are both used as inputs for the same MediaLive channel. The first flow
                    (sports_event_A) is created in Availability Zone 1a of the us-west-1 Region. The second flow (sports_event_B) is created in
                    Availability Zone 1b of the us-west-1 Region.