# Attach inputs to the channel
Inputs part 1: Attach inputs

Before you started to create the MediaLive channel, you should have [created all of inputs](medialive-inputs.md) for all the content sources for the channel. 

You must now attach the inputs to the channel. You can attach multiple inputs to the channel. For detailed information about setting up a channel with more than one input, see [Setting up for input switching](scheduled-input-switching.md). There are [specific rules](eml-limitations-and-rules.md#limits-inputs) about the number and type (push versus pull, for example) of inputs that you can attach to one channel.

# The procedure to attach inputs
The procedure

**To attach one MediaLive input**

1. On the **Create channel** page, for **Input attachments**, choose **Add**. The **Attach input** section appears.

1. In **Input**, choose an existing input. As soon as you choose the input, information about the input appears. To review this information, see the following sections:
   + [Channel input—CDI VPC push input](input-cdi.md)

     [Channel input—Elemental Link push input](input-elink.md)
   + [Channel input—HLS pull input](input-hls-pull.md)
   + [Channel input—MediaConnect push input](input-mediaconnect-push.md)
   + [Channel input—MediaConnect Router input](input-mediaconnect-router.md)
   + [Channel input—MP4 pull input](input-mp4-pull.md)
   + [Channel input—RTMP push input](input-rtmp-push.md)
   +  [Channel input—RTMP pull input](input-rtmp-pull.md) 
   + [Channel input—RTP push input](input-rtp-push.md)
   + [Channel input—SMPTE 2110 input](input-s2110-pull.md) 
   + [Channel input—SRT caller input](input-srt-pull.md) 
   + [Channel input—SRT listener input](input-srt-push.md) 

1. Complete the **Logical interface names** fields. These fields appear only if you set up the channel to [run in a MediaLive Anywhere cluster](creating-a-channel-step1.md) and the input is a SMPTE 2110 input. 
   + You must specify the logical interface for the incoming content for the input.
   + If the channel implements SMPTE 2022-7 seamless protection switching, you must also specify the logical interface for that content. Slide the selector beside **Use 2022-7 **to enable the feature. Then select the logical interface to use.

   If you were involved in [designing the MediaLive Anywhere clusters](emla-deploy-design-cluster.md) in your organization, you should know which logical interface or interfaces to select. If you weren't involved in this design, you must obtain this information from the video engineer who was involved. 

1. Enter a name for the attachment. The default name is the name of the input itself.

1. Choose **Confirm**. The **Input attachment** section closes, and the **General input settings** section appears.

1. For information about completing the fields in the **General input settings** section, go to the [next step](creating-a-channel-step2a.md).

# Channel input—CDI VPC push input


To verify that the input is set up correctly, look at the **Input destinations** section. It shows the two locations on MediaLive that the upstream system will push the source to when the channel is running. These locations were automatically generated when you created the input:
+ If the channel is set up as a standard channel, two locations are generated. 
+ If the channel is set up as a single-pipeline channel, one location is generated. 

For example:

**10.99.39.23:5000**

**192.0.2.54:5000**

# Channel input—Elemental Link push input


To view the status of the AWS Elemental Link hardware device for this input, look at the **Details**. If the device is currently pushing content to MediaLive, the **Device** thumbnail shows the content. The device generates the thumbnails by capturing a video frame approximately every 5 seconds. 

# Channel input—HLS pull input


To verify that the input is set up correctly, look at the **Input sources** section. It shows the locations of the source video. You specified these locations when you created the input:
+ If the channel is set up as a standard channel, you specified two locations.
+ If the channel is set up as a single-pipeline channel, you specified one.

For example, for an HTTPS pull:

**https://203.0.113.13/sports/curling.m3u8** and

**https://203.0.113.54/sports/curling.m3u8** 

Or, for a pull from an AWS Elemental MediaStore container:

**mediastoressl://eri39n.data.mediastore.us-west-2.amazonaws.com/sports/canada/curling.m3u8**

 and

**mediastoressl://21lu05.data.mediastore.us-west-2.amazonaws.com/sports/canada/curling.m3u8** 

Or, for a pull from an Amazon S3 bucket:

**s3ssl://amzn-s3-demo-bucket/filler-videos/main/oceanwaves.mp4** and

**s3ssl://amzn-s3-demo-bucket/filler-videos/redundant/oceanwaves.mp4**

# Channel input—MediaConnect push input


To verify that the input is set up correctly, look at the **MediaConnect flows** section. It shows the ARNs of the AWS Elemental MediaConnect flows that are the source for this input. These ARNs were automatically generated when you created the input:
+ If the channel is set up as a standard channel, two ARNs are generated.
+ If the channel is set up as a single-pipeline channel, one ARN is generated. 

For example:

**arn:aws:mediaconnect:us-west-1:111122223333:flow:1bgf67:sports-event-A** and

**arn:aws:mediaconnect:us-west-1:111122223333:flow:9pmlk76:sports-event-B**

# Channel input—MediaConnect Router input


To verify that the input is set up and ready to use, look at the **state ** section. It should say detached if it's available to be used on a channel.

# Channel input—MP4 pull input


To verify that the input is set up correctly, look at the **Input destinations** section. It shows the locations of the source video. You specified these locations when you created the input:
+ If the channel is set up as a standard channel, you specified two locations.
+ If the channel is set up as a single-pipeline channel, you specified one. 

The format of the location depends on the type of upstream system:
+ For an upstream system that uses HTTP or HTTPS, the location is an HTTP or HTTPS URL. For example:

  **https://203.0.113.31/filler-videos/oceanwaves.mp4**

  **https://203.0.113.52/filler-videos/oceanwaves.mp4**
+ For a file that is stored on Amazon S3, the location is the bucket name and object for the file. For example:

  **s3ssl://amzn-s3-demo-bucket/filler-videos/main/oceanwaves.mp4**

  **s3ssl://amzn-s3-demo-bucket/filler-videos/redundant/oceanwaves.mp4**

# Channel input—RTMP pull input


To verify that the input is set up correctly, look at the **Input destinations** section. It shows the locations of the source video. You specified these locations when you created the input:
+ If the channel is set up as a standard channel, you specified two locations. 
+ If the channel is set up as a single-pipeline channel, you specified one. 

For example:

**rtmp://203.0.113.13:1935/live/curling/**

**rtmp://198.51.100.54:1935/live/curling/**

# Channel input—RTMP push input


Follow these guidelines to verify that the input is set up correctly.

**To verify the setup of the input**

1. Look at the **Input destinations** section. It shows the two locations on MediaLive that the upstream system will push the source to when the channel is running. These locations were automatically generated when you created the input: 
   + If the channel is set up as a standard channel, two locations are generated. 
   + If the channel is set up as a single-pipeline channel, one location is generated. 

   Each location consists of an address portion that was automatically generated, appended by a folder that you specified when you created the input. 

   For example, for an RTMP Public push input:

   **rtmp://198.51.100.99:1935/live/curling**

   **rtmp://192.0.2.18:1935/live/curling**

   For example, for an RTMP VPC push input:

   **rtmp://10.12.30.44:1935/live/curling**

   **rtmp://10.99.39.15:1935/live/curling**

1. Look again at the **Input destinations** section. 
   + If the section has an **Input security group** with a number beside it, then the input is an RTMP Public input that has a MediaLive security group. The input is correctly set up and you can continue.
   + If the section has an **Input security group** without a number beside it, then the input is an RTMP Public input that is missing a MediaLive input security group. This input isn't correctly set up. Typically, this situation occurs if, for example, you have input A attached to input security group B and then you delete B. Input A is no longer useable. You must recreate the input and attach an input security group to it before you can associate it with a channel that you are creating. 
   + If the section doesn't have an **Input security group**, then the input is an RTMP VPC push input. The input is correctly set up and you can continue.

# Channel input—RTP push input


Follow these guidelines to verify that the input is set up correctly.

**To verify the setup of the input**

1. Look at the **Input destinations** section. It shows the two locations on MediaLive that the upstream system will push the source to when the channel is running. These locations were automatically generated when you created the input:
   + If the channel is set up as a standard channel, two locations are generated. 
   + If the channel is set up as a single-pipeline channel, one location is generated. 

   For example, for an RTP Public input:

   **rtp://198.51.100.99:5000**

   **rtp://192.0.2.18:5000**

   For example, for an RTP VPC input:

   **rtp://10.12.30.44:5000**

   **rtp://10.99.39.15:5000**

1. Look again at the **Input destinations** section. 
   + If the section has an **Input security group** with a number beside it, then the input is an RTP Public input that has a MediaLive security group. The input is correctly set up and you can continue.
   + If the section has an **Input security group** without a number beside it, then the input is an RTP Public input that is missing a MediaLive input security group. This input isn't correctly set up. Typically, this situation occurs if, for example, you have input A attached to input security group B and then you delete B. Input A is no longer useable. You must recreate the input and attach an input security group to it before you can associate it with a channel that you are creating. 
   + If the section doesn't have an **Input security group**, then the input is an RTP VPC input. The input is correctly set up and you can continue.

# Channel input—SMPTE 2110 input


To verify that the input is set up correctly, look at the **SMPTE 2110 Receiver Group** section. It shows information from the SDP files that you specified when you created the input. For example:
+ **Video SDP: http://172.18.8.19/curling\$1video.sdp, Media index: 2**
+ **Audio SDPs: http://172.18.8.19/curling\$1audio\$11.sdp, Media index: 0**
  + **http://172.18.8.19/curling\$1audio\$12.sdp, Media index: 0**
  + **http://172.18.8.19/curling\$1audio\$12.sdp, Media index: 1**
+ **Ancillary SDPs: http://172.18.8.19/curling\$1ancill.sdp, Media index: 0**

  **Ancillary SDPs: http://172.18.8.19/curling\$1ancill.sdp, Media index: 1**

# Channel input—SRT caller input


To verify that the input is set up correctly, look at the **SRT caller settings** section. It shows the locations of the source video. This is the locations of the SRT listener. You specified these locations when you created the input:
+ If the channel is set up as a standard channel, you specified two locations. 
+ If the channel is set up as a single-pipeline channel, you specified one. 

For example, the information for one location, when source encryption is disabled: 
+ **SRT listener address: 192.0.2.120** 
+ **SRT listener port: 7001**
+ **Stream ID: mystream**

# Channel input—SRT listener input


Follow these guidelines to verify that the input is set up correctly.

**To verify the setup of the input**

1. Look at the **Input destinations** section. It shows the locations on MediaLive that the upstream system will push the source to when the channel is running. These locations were automatically generated when you created the input. The port is always 5050 for SRT listener inputs:
   + If the channel is set up as a standard channel, MediaLive allocated two IP addresses. 
   + If the channel is set up as a single-pipeline channel, MediaLive allocated one IP address.

   For example:

   **srt://54.123.45.67:5050**

   **srt://54.123.45.68:5050**

1. Look at the **SRT listener settings** section. It shows the configuration you specified when you created the input:
   + **Minimum latency**: The latency value in milliseconds (120 to 15000).
   + **Stream ID**: The stream ID if you specified one.
   + **Decryption**: The encryption algorithm (AES 128, AES 192, or AES 256) and the passphrase secret ARN.

1. Look again at the **Input destinations** section. 
   + The section must have an **Input security group** with a number beside it. This security group controls which IP addresses are allowed to push content to this input. If the section doesn't have an input security group, the input isn't correctly set up.