Wowza Community

Live-Application vs Live HTTP Origin Application when using Cloudfront

Hi,

we are trying to find the best settings for Cloudfront streaming, since we experience a lot of buffering.

According to https://www.wowza.com/docs/how-to-integrate-your-wowza-ec2-instance-with-cloudfront and https://www.wowza.com/docs/how-to-configure-a-wowza-server-as-an-http-caching-origin it seems like it’s better to create an “Live HTTP Origin” application. (although it seems to work with a regular live-application)

What are the differences to a regular “Live” application? Does it have any restrictions, apart from the missing RTMP? What are the advantages?

I’d be happy if someone could provide more information.

Hi,

This is now being handled in the created ticket (104981).

Jason

Hi @Jason Hilton, Hi @Bernhard Schmidt

it would be nice if you could share the correct decision.

What’s the better approach for Wowza over Cloudfront? Live or LiveHTTPOrigin?

What is the key difference?

Thanks a lot for advice

  • Tom

HI @Tom Korn, that’s a fair request and here is the solution that was provided by Jason in that support ticket:

The difference between HTTP origin and regular live streaming is that HTTP origin is session-less and is restricted to HTTP protocol (RTSP and RTMP are not available).
CloudFront will cache the HTTP chunks for playback clients to play when connecting directly to the CloudFront CDN.

CloudFront will cache every request if they all have a unique session id which is why using HTTP origin makes the connections session-less.
Please see the FAQ for further information on CloudFront integration.
https://www.wowza.com/docs/frequently-asked-questions-cloudfront.

–I hope this helps.

Here is an additional CloudFront doc from the Wowza website:

https://www.wowza.com/docs/how-to-integrate-your-wowza-ec2-instance-with-cloudfront

Merci, Rose!

It helps to understand!