1) I have confirmed that the s3 bucket is identical to the working http cloudfront stream and is the correct bucket.

The /fcs/ident2 is pointed to the same cloudfront host as my rtmp distribution, just as it is on your demo page for your cloudfront distribution.

Currently both restrict bucket access and restrict viewer access are both disabled for testing. However I added my rtmp domain to my FV cloudfront pro settings in addition to my http distribution domain. The access restrictions are in place and working fine for the http distribution (4th video) except on my phone, but that is my other thread.

If there is a problem with the cloudfront distributions being different (I thought they were separate and unrelated) I will temporarily disable permissions on both… There, for now I have disabled bucket access and viewer access restrictions on the http distribution as well.

The changes are propagating now. I will look at the javascript errors. I’ll get back to you on these two.

2) Does HLS supersede http? What is confusing me is in the documentation I thought I understood that I am to put the HLS url into the same place where I would put the cloudfront http url.

But looking again, I guess I use ec2 to transcode the files into a new s3 bucket, then I can make an http cloudfront distribution to pull the m3u8 playlist from that new bucket, right?

Thanks for this document. I’m looking forward to encrypting the streams. This document doesn’t talk about cloudfront protection. I thought

I selected FV Player / Troubleshooting from the dropdown and watched the forum save it in the wrong folder. Mod, can you move it please?