404 error using CDN for video streaming using media live, media package

Question

I have set up a video workflow with an S3-stored video. I configured a MediaLive channel for retrieval and processing, then ingested the output into MediaPackage(packager type- Apple HLS). 
I am using CloudFront for multi-device delivery, but I'm facing a 404 error when trying to play the streamed content via the CloudFront URL. Also the HLS dash player from media package endpoint is giving 404 manifest error. My main concern is the 404 error using this below link(cdn url/ media package endpoint)
 
The link is: https://d17u------f0k.mediapackage.eu-west-2.amazonaws.com/out/v1/b-----------7576c7b5965/index.m3u8..
 
I will highly appreciate all your help and value your expertise and time. I am grateful for your assistance. Let me know if more details are needed.

Regards

Quental, Nuno · Answer

Hi Aman,

A few things you may check to verify if the encoding and packaging is working correctly.
Did you tried to play the live streams from MediaPackage endpoint directly? Do the streams play (HLS and DASH)?

Moving on to troubleshoot the CDN...

Do you have CloudFront logs enabled? To verify what may be causing the 404 error?
Did you create a custom error page response for a 404 HTTP Status response with a short TTL? So that further requests do not get the cached 404 error response.

See the following documentation for details on how to setup MediaPackage with CloudFront CDN: https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/live-streaming.html

You can also follow this workshop that shows how to setup a live channel with MediaPackage: https://github.com/aws-samples/aws-media-services-simple-live-workflow/blob/master/2-MediaPackage/README.md

Or you can deploy the following CloudFormation template: https://github.com/aws-solutions/live-streaming-on-aws/blob/main/README.md

Aman · Answer

Changing the policies , giving all access rights to s3 bucket and choosing the channel template correctly worked. thank you for your time and help

Liu, George · Answer

The 404 from the MediaPackage endpoint directly means MediaPackage hasn't received any content yet. This points to a MediaLive → MediaPackage connection issue.

Quick checks:

1. Does MediaLive's HLS output destination URL match the MediaPackage ingest endpoint?
2. Are the ingest credentials (username/password) correct in MediaLive?

404 error using CDN for video streaming using media live, media package

Add your answer

Relevant content