Step 2: Complete the fields on the console
After you have designed the output names and destination paths, you can set up the HLS output group.
The following fields configure the location and names of the HLS media and manifest files (the destination).
-
Output group – HLS group destination section
-
Output group – HLS settings – CDN section
-
Output group – Location – Directory structure
-
Output group – Location – Segments per subdirectory
-
HLS outputs – Output settings – Name modifier
-
HLS outputs – Output settings – Segment modifier
To set the destination for most downstream systems
-
Complete the URL fields in the HLS group destinations section. Specify two destinations if the channel is set up as a standard channel, or one destination if it is set up as a single-pipeline channel.
Portion of the destination path Location of the Field Description protocol URL in HLS group destinations section s3ssl://domain URL in HLS group destinations section The bucket name path URL in HLS group destinations section The optional path of folders Always terminate with a slash
baseFilename URL in HLS group destinations section Required Don't terminate the baseFilename with a slash.
modifier Name modifier in each HLS outputs section Required Make sure the modifiers are unique across all outputs in the output group
segmentModifier Segment modifier in each HLS outputs section Optional Keep in mind that this field exists for each output.
-
Leave the Credentials section blank in both the HLS 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.
-
In the CDN settings section, choose
Hls S3. -
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.
