AWS medialive documentation change
Summary
Added three new alert IDs (6704, 6707, 6751) with descriptions for pipeline locking synchronization issues in MediaLive.
Security assessment
These are operational alerts for pipeline locking synchronization issues in MediaLive. They describe technical problems with content synchronization and configuration mismatches, not security vulnerabilities or security-related features.
Diff
diff --git a/medialive/latest/ug/monitor-activity-types-alerts-channels.md b/medialive/latest/ug/monitor-activity-types-alerts-channels.md index 918aa73c6..817f6c3b8 100644 --- a//medialive/latest/ug/monitor-activity-types-alerts-channels.md +++ b//medialive/latest/ug/monitor-activity-types-alerts-channels.md @@ -61,0 +62,3 @@ Alert ID | Alert wording | Description +6704 | Embedded Timecodes Too Far Apart for Pipeline Locking | Pipelines in the pipeline locking pool have embedded input timecodes that are too far apart for pipeline locking synchronization. This typically occurs when pipelines are receiving content from different input sources or when input sources are not properly synchronized. +6707 | Output Configuration Mismatch Detected | Pipelines in the pipeline locking pool have incompatible output configurations and pipeline locking has been disabled. This typically occurs when channels have different output group counts, segment lengths, muxer configurations, or video encoding parameters. Ensure all channels in the pipeline locking pool have identical output configurations. +6751 | Unable to Establish Video Alignment on Input Content | MediaLive is unable to synchronize video content across pipelines in the pipeline locking pool. This typically occurs when input content differs between pipelines. Ensure that all pipelines in the pool are receiving identical source content.