aws medialive pipeline details not updating active inputs

What data do you expect?

Here is what I have when execute this command

aws medialive describe-channel --channel-id 111111

...

"Name": "test_channel",

"PipelineDetails": [],

"PipelinesRunningCount": 0,

"RoleArn": "arn:aws:iam::1111111111:role/MediaLiveAccessRole",

"State": "IDLE",

"Tags": {}

...

Or

...

"Name": "test_channel",

"PipelineDetails": [

{"ActiveInputAttachmentName": "mp4_file_test",

"PipelineId": "0"} ],

"PipelinesRunningCount": 1,

"RoleArn": "arn:aws:iam::1111111111:role/MediaLiveAccessRole",

"State": "RUNNING",

"Tags": {}

....

It sounds like you're experiencing an issue with AWS MediaLive where the pipeline details are not updating to reflect active inputs, and the DescribeChannel command is not providing all the expected information for your OBS (Open Broadcaster Software) channel. This can indeed cause problems when trying to update your user page with current channel information.

There are a few things to consider in this situation:

1. Input detection: Make sure that your source is properly contributing content to MediaLive. Sometimes, MediaLive may have trouble detecting audio and video in the input, which can lead to incomplete channel information.

2. Channel status: Ensure that your channel is in the correct state. Some information may not be available or may not update when the channel is in an idle state.

3. API response timing: There might be a slight delay between changes occurring in the channel and those changes being reflected in the API response. You may need to implement a retry mechanism or periodic polling to get the most up-to-date information.

4. Permissions: Verify that your IAM entity has the necessary permissions to access all the required information from the MediaLive channel.

5. Input attachments: Check if the active input attachment is correctly configured and recognized by the channel.

To troubleshoot this issue:

1. Review your channel's input metrics to confirm that content is arriving at MediaLive as expected.

2. Ensure your channel is in the running state if you're expecting to see active input information.

3. Check your IAM permissions to make sure you have full access to describe the channel and its details.

4. If using MediaConnect as a source, verify that the IP address contributing content is specified in the Allowlist CIDR block.

5. Consider implementing a retry mechanism in your application to call the DescribeChannel API multiple times with a short delay between calls to capture any updates that might be delayed.

If the issue persists after trying these steps, you may need to contact AWS support for further assistance, as there could be an underlying service issue or a more complex configuration problem that requires deeper investigation.
Sources
AWS Elemental Medialive Support Playbook | AWS re:Post
Channels - AWS Elemental MediaLive API Reference

I have tried to send stream from OBS (OBS -> RTMP -> MediaLive) to reproduce what you see.

But it's working for me:

"Name": "rtmp",

"PipelineDetails": [ {

"ActiveInputAttachmentName": "",

"ActiveInputSwitchActionName": "",

"ActiveMotionGraphicsActionName": "",

"ActiveMotionGraphicsUri": "",

"PipelineId": "0"

}

],

"PipelinesRunningCount": 1,

"RoleArn": "arn:aws:iam::111111111:role/MediaLiveAccessRole",

"State": "RUNNING",

Could you please check status of MediaLive channel from AWS console?

Is it working for you from web side?

If not, this looks like wrong EML configuration.

If you see status in console I would suggest to update cli to newest version.

If it doesn't help open ticket in AWS support.