- 最新
- 投票最多
- 评论最多
Hi Simon,
The first thing that comes to mind is to check and confirm that the URL being passed to the player is pointing at the CloudFront distribution rather than directly to the MediaStore container. You can confirm this by noting whether the domain name ends in "mediastore.<region>.amazonaws.com" rather than ending in "cloudfront.net"
Regards,
Steve
I tested a bit around, and what i found out is, when i use the "Workflow Wizard" which is available in the AWS Elemental MediaLive Service, then the HLS Settings are different in the output group. CDN Settings are set to "HLS webdav". In the instructions i posted above there is mentioned setting this to "HLS media store". If i compare the files available in the mediastore, then with the instructions i only have some ".m3u8" files available there. When using the wizard, then i have these .m3u8 files (one for every resolution) and additionally tons of ".ts" files. Does this maybe have any impact related to my issue?
相关内容
- AWS 官方已更新 2 年前
- AWS 官方已更新 4 年前
So the url was https://d1gsgy4dju827a.cloudfront.net/live.m3u8
So think this should be okay?