Rules for most downstream systems - AWS Elemental MediaLive

Rules for most downstream systems

Read this section if you are setting up redundant manifests with any downstream system except Akamai. If your downstream system is an Akamai CDN, see Rules for Akamai CDNs.

The rules for downstream systems (except Akamai) are based on these requirements:

  • MediaLive pushes the files from both pipelines to the same location (protocol/domain/path).

  • Given that the location is the same, the base_filenames for the pipelines must be different.

  • If you are also implementing custom manifest paths, the URL inside the manifests must be identical.

Make sure that the downstream system can work with these restrictions.

Field Rule
Protocol/domain/path portion of the two destination URIs (A and B) Must be identical in both fields.
Base_filename portion of the two destination URIs (A and B)

Must be different in each field.

It cannot use variable identifiers that include the date or time.

Name_modifier for each output

There is only one instance of this field. Both pipelines use the same value.

It cannot use variable identifiers that include the date or time.

Segment modifier

There is only one instance of this field. Both pipelines use the same value.

It can use variable identifiers that include the date or time.

Base URL Manifest A and

Base URL Manifest B

These fields apply only if you are also implementing custom manifest paths.

Complete both fields.

Base URL Content A and

Base URL Content B

These fields apply only if you are also implementing custom manifest paths.

Complete both fields.