Select your cookie preferences

We use essential cookies and similar tools that are necessary to provide our site and services. We use performance cookies to collect anonymous statistics, so we can understand how customers use our site and make improvements. Essential cookies cannot be deactivated, but you can choose “Customize” or “Decline” to decline performance cookies.

If you agree, AWS and approved third parties will also use cookies to provide useful site features, remember your preferences, and display relevant content, including relevant advertising. To accept or decline all non-essential cookies, choose “Accept” or “Decline.” To make more detailed choices, choose “Customize.”

How manifests work

Focus mode
How manifests work - MediaLive

The following sections describe how MediaLive handles manifest paths.

How manifest paths work by default

The manifests that MediaLive creates include information about the paths to other files, specifically:

  • The content inside the main manifest includes a path to each child manifest.

    By default, the syntax of this path is the following:

    baseFilename nameModifier extension

    For example:

    curling-high.m3u8

    The path is relative to the location of the main manifest.

  • The content inside each child manifest includes a path to its media files.

    By default, the syntax of this path is the following:

    baseFilename nameModifier optionalSegmentModifier counter extension

    For example:

    curling-high-000001.ts

    The path is relative to the location of the child manifest.

How custom paths work

If the default paths inside the manifests are not suitable for the way that the downstream system handles the three sets of files, you can complete the base URL fields:

  • Complete the Base URL manifest fields so that MediaLive constructs custom paths to the child manifests.

  • Complete the Base URL content fields so that MediaLive constructs custom paths to the media files.

When you customize the paths, the syntax changes.

  • When you complete the Base URL manifest fields, the syntax for the child manifest path (inside the main manifest) is the following:

    baseURLManifest baseFilename nameModifier extension

    For example:

    http://viewing/sports/curling-high.m3u8
  • When you complete the Base URL content fields, the syntax for the media file paths (inside the child manifests) is the following:

    baseURLContent baseFilename nameModifier optionalSegmentModifier counter extension

    For example:

    http://viewing/media/sports/curling-high-000001.ts

How MediaLive constructs these paths

The custom paths to the child manifests are constructed as follows:

  • You complete the Base URL manifest fields, or the Base URL content fields, or both.

    For example:

    http://198.51.100/sports/viewing/

    Note the slash at the end of the value.

  • MediaLive prepends that value to the default path. For example:

    http://198.51.100/sports/viewing/curling-high.m3u8
PrivacySite termsCookie preferences
© 2025, Amazon Web Services, Inc. or its affiliates. All rights reserved.