Missing notifications from MediaLive

0

Hi, I think there may be an issue with MediaLive sending inconsistent "STARTING" and "ACTIVE" channel notifications. In Cloudwatch I have the following rule: { "source": [ "aws.medialive" ], "detail-type": [ "MediaLive Channel State Change" ] }

This sends a notification to my server via an SNS topic with a HTTPS subscription. It all works well and I am receiving messages for all of the state changes except "STARTING" and "RUNNING" which are very inconsistent. They sometimes get sent and sometimes don't, whereas all the other messages arrive quickly with 100% consistency. This also happens if I receive the notification via email. I can't think of any reason why a problem with my AWS configuration or web server would mean that channel "CREATED", "DELETED", "STOPPING" and "STOPPED" work fine but "STARTING" and "RUNNING" do not. Could this be a problem with AWS?

Here is an example of a successful notification from SNS: { version: '0', id: '<id>', 'detail-type': 'MediaLive Channel State Change', source: 'aws.medialive', account: '<account>', time: '2023-03-18T20:40:36Z', region: 'eu-west-2', resources: [ '<arn>' ], detail: { pipelines_running_count: 0, state: 'STOPPED', pipeline: '0', channel_arn: '<arn>', message: 'Stop detected on pipeline' } }

Thanks

1 Answer
0

Ed, AWS MediaLive channel start up times will vary, depending on several channel and resource factors. Typically channel start times will be under a few minutes, yet can be longer in some scenarios. This would delay the 'Pipeline Running' message to CloudWatch Events. The "CREATED", "DELETED", "STOPPING" and "STOPPED" channel updates are much more deterministic.

Perhaps you could review the CloudWatch Event logs for the MediaLive channel that seemed not to provide a notification of 'Running'. If there is no log of the start, you may want to submit an AWS Support ticket, with the MediaLive Channel ARN, and Region of operation, requesting why the notification was not provided.

AWS
Mike-ME
answered a year ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions