AWS mediaconnect documentation change
Summary
Updated documentation to include instructions for connecting router inputs to MediaLive channel outputs, added a new configuration section for MediaLive channel integration, and updated cross-references to the integration guide.
Security assessment
The change adds documentation for a new integration feature (router input to MediaLive channel output) and includes details about encryption configuration ('Source transit decryption key type') that must match between services. This documents a security feature (encryption in transit) but does not indicate a fix for a specific security vulnerability or incident.
Diff
diff --git a/mediaconnect/latest/ug/creating-router-io.md b/mediaconnect/latest/ug/creating-router-io.md index 3a606a489..eb6225274 100644 --- a//mediaconnect/latest/ug/creating-router-io.md +++ b//mediaconnect/latest/ug/creating-router-io.md @@ -49 +49,3 @@ You can configure router I/Os with either a Regional routing scope or a global r - * If you want to connect your router output to a MediaLive input, your MediaLive input must be set up for router integration. For more information, see [Integrating router outputs with MediaLive inputs](./integrate-eml-with-router.html). + * If you want to connect your router output to a MediaLive input, your MediaLive input must be set up for router integration. For more information, see [Integrating router I/Os with MediaLive](./integrate-eml-with-router.html). + + * If you want to connect your router input to a MediaLive channel output, your MediaLive channel must have a MediaConnect Router output group configured. For more information, see [Integrating router I/Os with MediaLive](./integrate-eml-with-router.html). @@ -178 +180,17 @@ The content of the secret must be an AES-256 key in hexadecimal format. The key - 3. **Failover** \- For failover configuration, follow these steps: + 3. **MediaLive channel** \- To receive content from a MediaLive channel output, follow these steps. + +###### Note + +This option requires a MediaLive channel with a MediaConnect Router output group. For more information, see [Integrating router I/Os with MediaLive](./integrate-eml-with-router.html). + +If you want to create the router input and connect the channel at a later time, select the **Do not connect to a MediaLive channel** option and then select the Availability Zone where the router input will be placed in. Both the router input and the MediaLive channel pipeline must be in the same Availability Zone. + + 1. Under **MediaLive channel ARN** , specify the channel that you want to connect to. + + 2. Under **Pipeline** , specify the pipeline ID of the channel output. + + 3. Under **Output name** , specify the name of the channel output within the MediaConnect Router output group. + + 4. Under **Source transit decryption key type** , choose how to decrypt content as it moves from the MediaLive channel to the router input. This must match the encryption type configured on the MediaLive channel output. For details about the available options, see [Encryption options](./integrate-eml-with-router.html#eml-router-encryption). + + 4. **Failover** \- For failover configuration, follow these steps: @@ -254 +272 @@ For example, if you specify port 2000 for the input, MediaConnect will also rese - 4. **Merge** \- For merge configuration, follow these steps: + 5. **Merge** \- For merge configuration, follow these steps: @@ -443 +461 @@ The content of the secret must be an AES-256 key in hexadecimal format. The key -This option requires a MediaLive input that's been set up for router integration. For more information, see [Integrating router outputs with MediaLive inputs](./integrate-eml-with-router.html). +This option requires a MediaLive input that's been set up for router integration. For more information, see [Integrating router I/Os with MediaLive](./integrate-eml-with-router.html).