Fields for the output destination - AWS Elemental MediaLive

Fields for the output destination

The following fields configure the location and names of the archive output files (the destination).

  • Output groupArchive group destination section

  • Output groupArchive settingsCDN settings

  • Output groupAdditional settingsRollover interval

  • Archive outputsName modifier

  • Archive outputsExtension

You must design the destination path or paths for the output. You must then enter the different portions of the path into the appropriate fields on the console.

Design the path for the output destination

As part of the planning for this output group, you discussed your requirements with the Amazon S3 user. You should already have the following information:

  • The bucket names portion of the path for the output

  • Or the full path for the output.

To design the path

If you haven't yet designed the destination path, design them now. If you've already designed the paths, go to Complete the fields on the console.

  • Design the destination path or paths, following this syntax:

    protocol bucket folders baseFilename nameModifier counter extension

    For example, for a standard channel:



The following table maps each portion in the example to the portion in the syntax.

Portion of the URL Example Comment
protocol s3ssl:// The protocol is always s3ssl:// because the destination for an Archive output is always an S3 bucket.
bucket portion of the path DOC-EXAMPLE-BUCKET When you planned the workflow for the channel, you should have made sure that the S3 bucket or buckets exist.

With MediaLive, the S3 bucket name must not use dot notation. For example, mycompany-videos is acceptable but mycompany.videos isn't.

folders portion of the path channel59/delivery/ The folders can be present or not, and can be as long as you want.

The folders must always end with a slash.

baseFilename curling Don't terminate the file name with a slash.
nameModifier -20171012T033162 The modifier is optional for an archive output.
delimiter before the counter . MediaLive automatically inserts this delimiter.
counter 000000 MediaLive automatically generates this counter. Initially, this is a six-digit number starting at 000000, and increasing by 1. So 000000, 000001, 000002 and so on. After 999999, the next number is 1000000 (seven digits), then 1000001, 1000002, and so on. Then from 9999999 to 10000000 (eight digits), and so on.
dot before the extension . MediaLive automatically inserts this dot.
extension m2ts Always m2ts.

Complete the fields on the console

To specify the location for the output

  1. Enter the different portions of the destination in the appropriate fields.

    Portion of the destination URL Field Example
    protocol, bucket, folders, baseFilename The two URL fields in the Archive group destinations section.

    The data before the first slash is the bucket name. The data after the last slash is the baseFilename. The data in between is the folders.

    Specify two destinations when the channel is set up as a standard channel, or one destination when it is set up as a single-pipeline channel.

    nameModifier The Name modifier field in the Archive outputs section.

    If you choose to include a modifier, you can enter a string such as -high, to indicate a high-resolution output.

    Or you can enter a variable ID (such as $dt$) to ensure that the modifier is different for each file segment. For a list of variable data identifiers, see Reference: identifiers for variable data.

    extension The Extension field in the Archive outputs.

    Always leave the default, m2ts.

  2. Leave the Credentials section blank in both the Archive group destinations sections. MediaLive has permission to write to the S3 bucket via the trusted entity. Someone in your organization should have already set up these permissions. For more information, see Reference: summary of requirements for the MediaLive trusted entity.

  3. Complete the CDN settings field only if MediaLive must set a canned ACL whenever it sends this output to the Amazon S3 bucket.

    Use of a canned ACL typically only applies if your organization is not the owner of the Amazon S3 bucket. You should have discussed the use of a canned ACL with the bucket owner when you discussed the destination for the output.

  4. Complete the Rollover interval field in the Archive settings section.

    For example, 300 divides the output into separate files, each with a 300 second (5 minutes) long duration.

    Each time the rollover expires, MediaLive closes the current file on Amazon S3 and starts a new file using the baseFilename, the nameModifier, and a sequential counter.

    The current file is visible on Amazon S3 only after it has closed.

For more information, see the examples.