By using AWS re:Post, you agree to the Terms of Use
/Vod MediaPackage with cloudfront/

Vod MediaPackage with cloudfront


I have a mediapackage configuration with Cloudfront CDN. I have few queries: 1. Is HLS packaging done during ingest process when playable URL is obtained (if yes, where is this Manisfest & .ts chunks stored?) or it is done when a playback request is received. 2. Once playback is done for the first time, is the manifest & ts chunks cached in cloudfront or packaging is done for every playback request. 3. I have done a CDN cache settings but not sure if playback is done from CDN cache or origin (mediapackage) . How to check the correct configuration.

1 Answers

AWS MediaPackage provides Just-In-Time packaging for any of its endpoints for HLS, DASH, CMAF. Thus packaging for any requested content occurs once a request has been received. For Live HLS inputs, MediaPackage will store up to 14 days of content. This can be used for allowing 'Start-Over' or 'Go-Back' features. This can be configured for each endpoint by the Startover Window. See this link for details.

If MediaPackage is used to package VOD assets, then it is made aware of those assets (Ingested from S3) previously and will pull them when requested.

When using a CDN, such as CloudFront and MediaPackage as the content origin, caching behaviors should be defined. Stream manifests or playlists (.m3u8s) should be cached for less than an HLS segment, since they are updated every segment. The content segments (.ts) can be cached for a long time. Each segment is numbered and does not change. Note that error codes from MediaPackage should also be cached in CloudFront for a short time (~1s TTL). By default these error code values are not set and will default to 10s.

answered a month ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions