AWS medialive documentation change
Summary
Added configuration steps for pipeline locking methods (source timecode and video alignment) in channel settings, including input requirements.
Security assessment
Changes provide operational guidance for synchronization methods without mentioning security vulnerabilities, incidents, or protective features. Focus is on functionality, not security.
Diff
diff --git a/medialive/latest/ug/pipeline-locking-set-up.md b/medialive/latest/ug/pipeline-locking-set-up.md index 246bbce00..21dc07497 100644 --- a//medialive/latest/ug/pipeline-locking-set-up.md +++ b//medialive/latest/ug/pipeline-locking-set-up.md @@ -28 +28 @@ You can configure the channel as follows: -###### Configure the pipeline locking mode +###### Configure the pipeline locking mode and method @@ -35,0 +36,8 @@ You can configure the channel as follows: + 4. To configure the pipeline locking method (available only with **PIPELINE_LOCKING** mode), expand **Additional settings**. + + 5. In **Output locking settings** , locate the **Pipeline locking method** field and choose the method for synchronization: + + * **SOURCE_TIMECODE** (default): Uses embedded timecodes from the input source. Requires inputs with reliable embedded timecodes. See [Inputs must include embedded timecode (source timecode method)](./pipeline-locking-verify-input.html#pipeline-locking-embedded-tcode). + + * **VIDEO_ALIGNMENT** : Uses visual signature comparison between encoders. Does not require embedded timecodes. See [Requirements for video aligned pipeline locking](./pipeline-locking-verify-input.html#pipeline-locking-video-alignment-inputs) for input compatibility. +