AWS mediatailor documentation change
Summary
Added explicit session initialization methods (POST/GET), parameter immutability details, and reporting mode. Clarified parameter processing flow and configuration alias resolution.
Security assessment
The documentation emphasizes that manifest parameters are immutable after initialization, preventing post-initialization tampering. While this is a security control, there's no explicit mention of addressing a specific vulnerability. The 'reportingMode' addition and immutability guidance enhance security documentation.
Diff
diff --git a/mediatailor/latest/ug/manifest-query-parameters-hls-and-dash-explicit-session-initialization.md b/mediatailor/latest/ug/manifest-query-parameters-hls-and-dash-explicit-session-initialization.md index b15368050..d9b35f099 100644 --- a//mediatailor/latest/ug/manifest-query-parameters-hls-and-dash-explicit-session-initialization.md +++ b//mediatailor/latest/ug/manifest-query-parameters-hls-and-dash-explicit-session-initialization.md @@ -5 +5,21 @@ -# HLS and DASH explicit session initialization with AWS Elemental MediaTailor +# MediaTailor HLS and DASH explicit session initialization + +AWS Elemental MediaTailor includes the `manifestParams` as query parameters in the multivariant playlist and tracking URLs in the response when the client makes an explicit session initialization request. + +###### Session initialization methods + +For explicit session initialization, you can use either POST with request body or GET with query parameters: + + 1. **POST with Request Body:** + + POST /v1/session/111122223333/originId/index.m3u8 + { + "adsParams": {"param1": "value1", "param2": "value2", "param3": "value3"}, + "manifestParams": {"test": "123"} + } + + 2. **GET with Query Parameters:** + + GET /v1/session/111122223333/originId/index.m3u8?ads.param1=value1&ads.param2=value2&manifestParams.test=123 + + @@ -7 +26,0 @@ -When the client makes an explicit session initialization request, MediaTailor includes the `manifestParams` as query parameters in the parent manifest and tracking URLs in the response. @@ -21 +40,2 @@ When the client makes an explicit session initialization request, MediaTailor in - } + }, + "reportingMode": "client" @@ -32 +52,5 @@ When the client makes an explicit session initialization request, MediaTailor in -Manifest responses for the session have the specific `manifestParams` in MediaTailor URLs similar to the previously described implicit session-initialization workflows. The key difference is that the manifest parameters for explicit session initialization don't start with `manifest.`. +Manifest responses for the session have the specific `manifestParams` in MediaTailor URLs similar to the previously described implicit session-initialization workflows. The key difference is that manifest parameters for explicit session initialization don't start with `manifest.`. + +Manifest query parameters are immutable and you can only set them on session initialization. If a client makes multiple multivariant playlist requests for a single session, MediaTailor doesn't update the manifest query parameters after the first request. + +###### Parameter processing flow @@ -34 +58 @@ Manifest responses for the session have the specific `manifestParams` in MediaTa -Manifest query parameters are immutable and only set on session initialization. If a client makes multiple parent manifest requests for a single session, MediaTailor doesn't update the manifest query parameters after the first request. +You can only specify parameters once, at initialization time. Configuration aliases resolve to actual values before forwarding. For example: `player_params.ad_type=customized` resolves to `ad_type=abc12345` based on the ConfigurationAliases configuration. @@ -42 +66 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -DASH implicit session initialization +MediaTailor DASH implicit sessions @@ -44 +68 @@ DASH implicit session initialization -Reporting ad tracking data +MediaTailor protocol-specific behavior