AWS mediatailor documentation change
Summary
Expanded HLS manifest documentation with detailed explanations of playlist types, personalized manifest differences, and related topics
Security assessment
The changes primarily focus on clarifying HLS manifest structures and MediaTailor's personalization workflow. While terminology updates (master->multivariant) improve accuracy, there's no evidence of addressing security vulnerabilities or describing security controls. The session-specific URL mentions relate to workflow functionality rather than security mechanisms.
Diff
diff --git a/mediatailor/latest/ug/manifest-hls-example.md b/mediatailor/latest/ug/manifest-hls-example.md index e2e64dd05..b1de91bdd 100644 --- a//mediatailor/latest/ug/manifest-hls-example.md +++ b//mediatailor/latest/ug/manifest-hls-example.md @@ -5 +5 @@ -HLS origin manifest examplesHLS personalized manifest examples +Understanding HLS playlist typesHLS origin manifest examplesHLS personalized manifest examplesKey differences in personalized manifestsRelated topics @@ -9 +9,25 @@ HLS origin manifest examplesHLS personalized manifest examples -The following sections provide examples of HLS origin manifests and personalized manifests. +The following sections provide examples of HLS origin manifests and personalized manifests. Understanding these examples can help you configure and troubleshoot your MediaTailor workflows. + +## Understanding HLS playlist types + +HTTP Live Streaming (HLS) uses two primary types of playlists: + +Multivariant playlist + + +A multivariant playlist is the top-level index file that lists all available renditions of the content. It contains references to variant playlists but does not contain any media segments itself. This playlist allows players to select the most appropriate rendition based on network conditions, device capabilities, or user preferences. + +This playlist type is also known by several other names in various contexts, including master playlist, master manifest, primary playlist, main playlist, index file, or master M3U8. + +In MediaTailor workflows, the multivariant playlist is the entry point for playback requests and is where ad personalization begins. + +Variant playlist + + +A variant playlist contains the actual media segment information for a specific rendition (quality level) of the content. It includes timing information, segment URLs, and other metadata required for playback of a single rendition. + +This playlist type is also known as media playlist, child manifest, chunklist, media M3U8, or rendition playlist. + +In MediaTailor workflows, variant playlists are personalized to include both content segments and ad segments in the proper sequence. + +For more detailed information about HLS playlist types, see [HLS playlist types](./hls-playlist-types.html). @@ -13 +37 @@ The following sections provide examples of HLS origin manifests and personalized -The following example shows an HLS master manifest that AWS Elemental MediaTailor received by HLS from the content origin. +The following example shows an HLS multivariant playlist that AWS Elemental MediaTailor received by HLS from the content origin. @@ -27 +51,12 @@ The following example shows an HLS master manifest that AWS Elemental MediaTailo -The following example shows an HLS media manifest that AWS Elemental MediaTailor received by HLS from the content origin. This example uses `EXT-X-CUE-OUT` and `EXT-X-CUE-IN` tags to describe ad avail opportunities. +In this multivariant playlist example: + + * The `#EXT-X-STREAM-INF` tags define different renditions with varying resolutions and bitrates + + * Each rendition references a variant playlist (e.g., `index_1.m3u8`) + + * The `#EXT-X-MEDIA` tag defines a subtitle track + + + + +The following example shows an HLS variant playlist that AWS Elemental MediaTailor received by HLS from the content origin. This example uses `EXT-X-CUE-OUT` and `EXT-X-CUE-IN` tags to describe ad avail opportunities. @@ -65,0 +101,13 @@ The following example shows an HLS media manifest that AWS Elemental MediaTailor +In this variant playlist example: + + * The `#EXTINF` tags specify the duration of each segment + + * The `#EXT-X-CUE-OUT` tag marks the beginning of an ad break + + * The `#EXT-X-CUE-OUT-CONT` tags provide information about the ongoing ad break + + * The `#EXT-X-CUE-IN` tag marks the end of the ad break + + + + @@ -68 +116 @@ The following example shows an HLS media manifest that AWS Elemental MediaTailor -The following example shows an HLS master manifest that AWS Elemental MediaTailor personalized. +The following example shows an HLS multivariant playlist that AWS Elemental MediaTailor personalized. @@ -81,0 +130 @@ The following example shows an HLS master manifest that AWS Elemental MediaTailo +Notice how MediaTailor has modified the variant playlist URLs to include session-specific information that enables personalized ad insertion. @@ -83 +132 @@ The following example shows an HLS master manifest that AWS Elemental MediaTailo -The following example shows a media master manifest that AWS Elemental MediaTailor personalized. +The following example shows a variant playlist that AWS Elemental MediaTailor personalized. @@ -121,0 +171,56 @@ The following example shows a media master manifest that AWS Elemental MediaTail +In this personalized variant playlist example: + + * MediaTailor has inserted ad segments between the content segments + + * The `#EXT-X-DISCONTINUITY` tags mark the transitions between content and ads + + * Content segments are served from the origin server (MediaPackage in this example) + + * Ad segments are served from MediaTailor's ad segment storage + + + + +## Key differences in personalized manifests + +When MediaTailor personalizes HLS manifests, it makes several important changes: + +Multivariant playlist changes + + + * Variant playlist URLs are rewritten to point to MediaTailor-managed URLs that include session information + + * The order of tags may be reorganized for optimal playback + + + + +Variant playlist changes + + + * Ad markers (`EXT-X-CUE-OUT`, `EXT-X-CUE-IN`) are replaced with actual ad segments + + * Discontinuity markers (`EXT-X-DISCONTINUITY`) are added at content/ad boundaries + + * Content segment URLs are rewritten to point to the origin or CDN + + * Ad segment URLs are added to point to MediaTailor's ad segment storage + + + + +Understanding these changes can help you troubleshoot issues in your MediaTailor workflows and ensure proper configuration of your CDN and player. + +## Related topics + +For more information about HLS manifests and MediaTailor, see the following topics: + + * [HLS playlist types](./hls-playlist-types.html) \- Detailed explanation of HLS playlist types + + * [Using a CDN to optimize MediaTailor ad personalization and content delivery](./integrating-cdn.html) \- Information about using a CDN with MediaTailor + + * [How MediaTailor ad insertion works](./what-is-flow.html) \- Overview of how MediaTailor ad insertion works + + + +