MediaLive Archive output not creating manifest .m3u8 file

Question

Hi there,  
  
I have set up an Archive Output group on my MediaLive channel, saving files to an S3 bucket.  In Output settings, I have added Output name and Name Modifier; all other settings are blank/default.  
  
The output is correct saving .ts files to S3 as the stream proceeds.  However, it does not create the manifest .m3u8 file.  
  
In case it's relevant, I am streaming from OBS using RTMP_PUSH.  When I stop the stream, the .ts files continue to save (presumably black screen).  They only stop being created once I stop the entire channel.  
  
Could you please help me understand how to have the manifest files created/saved alongside .ts files, upon completion of stream?  
  
Thank you!  
  
gDk

Accepted Answer

gDk7  
  
https://docs.aws.amazon.com/medialive/latest/ug/outputs-supported-containers.html  
Archive does not create content in an HLS format and therefore does not create an m3u8 manifest file, instead it creates TS chunks used for archive purposes. To create HLS content to be written to S3, instead use the HLS Output Group and set the destination to your S3 bucket, e.g. s3://your_bucket_name/your/folder/Name, where Name is the base name you want to assign to the HLS content.

Answer

Thank you so much fxeataws!    
  
This is exactly the information I needed.  Everything worked when I changed the type from Archive to HLS, thank you for your help.  
  
Just out of interest - if I am storing relatively small .ts chunks + m3u8 file on S3, is there any requirement for CloudFront / MediaStore?  Or could S3 happily handle high levels of traffic without those services?  
  
Thank you!  
  
Edited by: gDk7 on Jan 12, 2021 9:07 AM  
  
PS. I've noticed that only full-res video seems to be saved in the .ts files.  Does this seem correct?  And does it mean there's no way for HLS to jump between quality levels without a streaming server?  
  
Thank you once again!

Answer

gDk7  
  
If multiple entities are going to consume the content from this S3 bucket then it is best to use CloudFront to serve that content to your viewers.   
  
A better solution would be to use a MediaLive - MediaPackage - Cloudfront workflow. See https://aws.amazon.com/cloudfront/streaming/ for more detail on this. MediaPackage can create the different output packages (DASH, HLS, etc) to support all of the devices you may want to send data to. MediaPackage also can create the CloudFront instance and set it up for you to make the workflow just work.

MediaLive Archive output not creating manifest .m3u8 file

Relevant content