AWS mediatailor documentation change
Summary
Updated title, added detailed section about parameter application in DASH manifests, and modified example URLs/parameters
Security assessment
Changes clarify how query parameters are applied to DASH manifest elements but don't address security vulnerabilities or introduce security controls. The sessionId parameter handling is operational rather than security-focused, with no mention of encryption, authentication, or vulnerability mitigation.
Diff
diff --git a/mediatailor/latest/ug/manifest-query-parameters-dash-implicit-session-initialization.md b/mediatailor/latest/ug/manifest-query-parameters-dash-implicit-session-initialization.md index 672d54f67..06cec6304 100644 --- a//mediatailor/latest/ug/manifest-query-parameters-dash-implicit-session-initialization.md +++ b//mediatailor/latest/ug/manifest-query-parameters-dash-implicit-session-initialization.md @@ -5 +5 @@ -# DASH implicit session initialization with AWS Elemental MediaTailor +# MediaTailor DASH implicit session initialization @@ -7 +7 @@ -The client makes a manifest request without a session, as shown in the following example. +AWS Elemental MediaTailor creates a session for the client and redirects it with query parameters when the client makes a manifest request without a session. The following example shows this request format: @@ -15 +15,18 @@ MediaTailor creates a session for the client and redirects it with the query par - /v1/dash/111122223333/originId/index.mpd?sessionId=session&manifest.test=123 + /v1/dash/111122223333/originId/index.mpd?sessionId=session&test=123 + +###### Parameter application in DASH + +The DASH manifest response includes the query parameters in various locations, including content segments, ad segments, and initialization URLs. MediaTailor applies parameters to the following: + + * DASH manifest Location elements + + * SegmentTemplate initialization attributes + + * SegmentTemplate media attributes + + * Content segment URLs + + * Ad segment URLs + + + @@ -23 +40 @@ When the client makes the request, MediaTailor responds with a DASH manifest sim - <Location>https://mediatailor.com/v1/dash/111122223333/originId/index.mpd?manifest.test=123&aws.sessionId=session</Location> + <Location>https://mediatailor.com/v1/dash/111122223333/originId/index.mpd?test=123&aws.sessionId=session</Location> @@ -41 +58 @@ When the client makes the request, MediaTailor responds with a DASH manifest sim - <SegmentTemplate initialization="asset_540_2_0init.mp4?manifest.test=123" media="asset_540_2_0_$Number%09d$.mp4?manifest.test=123" startNumber="1" timescale="90000"> + <SegmentTemplate initialization="asset_540_2_0init.mp4?test=123" media="asset_540_2_0_$Number%09d$.mp4?test=123" startNumber="1" timescale="90000"> @@ -58 +75 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -HLS implicit session initialization +MediaTailor HLS implicit sessions @@ -60 +77 @@ HLS implicit session initialization -HLS and DASH explicit session initialization +MediaTailor explicit session initialization