1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
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.
con risposta un anno fa
Contenuto pertinente
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 4 anni fa