AWS mediatailor documentation change
Summary
Updated documentation structure and content about MediaTailor's handling of query parameters, including expanded explanations of CDN routing/authorization use cases, protocol differences, and integration details. Added new section links and rephrased support contact instructions.
Security assessment
While authorization is mentioned as a use case, there is no specific evidence of addressing a security vulnerability or adding new security controls. Changes focus on functionality clarification and documentation organization rather than security improvements.
Diff
diff --git a/mediatailor/latest/ug/manifest-query-parameters.md b/mediatailor/latest/ug/manifest-query-parameters.md index e15e17a5e..4722f54d0 100644 --- a//mediatailor/latest/ug/manifest-query-parameters.md +++ b//mediatailor/latest/ug/manifest-query-parameters.md @@ -5 +5 @@ -# Passing AWS Elemental MediaTailor session initialization parameters to the manifest +# MediaTailor manifest query parameters @@ -7 +7 @@ -AWS Elemental MediaTailor can preserve query parameters from session initialization and append them to the personalized manifest URL returned to the client player. Subsequent client requests also contain the appended query parameters. +AWS Elemental MediaTailor handles query parameters for different purposes: manifest query parameters for CDN routing and authorization, and other query parameters that may be used for origin-specific functionality. @@ -9 +9,3 @@ AWS Elemental MediaTailor can preserve query parameters from session initializat -Manifest query parameters are useful if you use a Content Delivery Network (CDN) between MediaTailor and the client player, where the CDN uses the query parameters for the following: +AWS Elemental MediaTailor preserves query parameters from session initialization and appends them to personalized manifest URLs and other assets. Use this functionality when you have a Content Delivery Network (CDN) between MediaTailor and the client player. + +Use manifest query parameters when your CDN needs the query parameters for the following: @@ -18 +20,5 @@ Manifest query parameters are useful if you use a Content Delivery Network (CDN) -For client-side reporting, MediaTailor appends query parameters for client-side reporting endpoints, but it doesn't append the query parameters for the CloudFront (or other CDN) segments. +###### Client-side vs CDN behavior + +MediaTailor appends query parameters for client-side reporting endpoints, but does not append them for CDN segments. The updated functionality provides more comprehensive support for query parameters across various MediaTailor assets, enhancing flexibility for CDN routing and authorization use cases. + +MediaTailor appends query parameters for client-side reporting endpoints, but it doesn't append the query parameters for the CloudFront (or other CDN) segments. @@ -20 +26 @@ For client-side reporting, MediaTailor appends query parameters for client-side -To use parameter preservation, [submit an AWS Support ticket](https://console.aws.amazon.com/support/home#/) to request for manifest query parameter pass through to be enabled. +To use parameter preservation, contact [AWS Support](https://aws.amazon.com/premiumsupport/) to request that manifest query parameter pass through be enabled. @@ -22 +28 @@ To use parameter preservation, [submit an AWS Support ticket](https://console.aw -The behavior varies between HLS and DASH, as well as with explicit and implicit session initialization. The following topics describe how to configure session initialization requests so MediaTailor will pass through parameters to the manifest. +The behavior varies between HLS and DASH, and between explicit and implicit session initialization. The following topics describe how to configure session initialization requests so that MediaTailor passes through parameters to the manifest: @@ -26 +32,5 @@ The behavior varies between HLS and DASH, as well as with explicit and implicit - * [HLS implicit session initialization](./manifest-query-parameters-hls-implicit-session-initialization.html) + * [MediaTailor HLS implicit sessions](./manifest-query-parameters-hls-implicit-session-initialization.html) + + * [MediaTailor DASH implicit sessions](./manifest-query-parameters-dash-implicit-session-initialization.html) + + * [MediaTailor explicit session initialization](./manifest-query-parameters-hls-and-dash-explicit-session-initialization.html) @@ -28 +38 @@ The behavior varies between HLS and DASH, as well as with explicit and implicit - * [DASH implicit session initialization](./manifest-query-parameters-dash-implicit-session-initialization.html) + * [MediaTailor protocol-specific behavior](./manifest-query-parameters-protocol-differences.html) @@ -30 +40 @@ The behavior varies between HLS and DASH, as well as with explicit and implicit - * [HLS and DASH explicit session initialization](./manifest-query-parameters-hls-and-dash-explicit-session-initialization.html) + * [MediaTailor CDN integration](./manifest-query-parameters-cdn-integration.html) @@ -41 +51 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Using player variables +Alias troubleshooting @@ -43 +53 @@ Using player variables -HLS implicit session initialization +Origin query parameters