Hi there ... I've waited for this feature for a while. I'm wondering if you have any agreement with AWS for caching live streaming using a CloudFront CDN and Wowza instance as origin.
As http traffic, caching should work just setting it up as http download and using wowza as origing, but Cloudfront has specific ways of setting their CDN when you'll do live streaming using Adobe Flash or IIS7 smooth streaming. They say it's an improved pre-configuration they have created for better performance.
I'm wondering if something like this exists for Wowza
Just to add to the discussion, as I've kept working on this on my own
I have right now working HDS and HLS out of Wowza server into Cloudfront. As it's HTTP streaming, which is based on files, it shouldn't be much of a difference than caching any http object. It works conceptually, but performance is not good.
On Wowza, I can see there's only one concurrent session even when there's more than one user streaming. But, CF doesn't perform very well as others CDNs. Most CDN, when it comes to http live streaming, they implement it in a different way than regular http object caching.
CF says they have an implementation for Smooth Streaming out of IIS and RTMP streaming out of Adobe Flash Server, developped to provide a reliable streaming experience (it involves the process of lighting up the server in paralell, etc).
I hope they work with Wowza to develop something similar. Meanwhile, I'm moving out of CF for my http streaming to other CDN. It's convenient, but not reliable.
Hi there .... actually, I've abandoned RTMP streaming a while ago. I've focused on HTTP streaming only, through Wowza or not
For what I know, RTMP using CF is only available when you use Adobe Flash Server. CF has a streamig service pre-defined for that (CF Streaming Distribution)
In general, my experience with CF for HLS is not good. Latency (as you say) is high in general, and I have performance issues in Europe (in North America is quite stable in terms of performance, but Europe is really bad)
I'm using Wowza for HLS and HDS. So, I've a couple of EC2 Wowza instances, running latest Wowza version that let you set Wowza as origin for CDN. Then, I've a couple of CF distributions for HTTP download pointing to Wowza servers as origin. Quite straight forward setting.
Again, CF performance is not good in general, so I'm testing other CDNs as I'm not happy with CF reliability for streaming
hi duxmedia ... thanks for sharing your test. I had my setup similar to yours. Difference was my origins were in Sao Paulo. Streaming to North America throught CF distributions worked pretty well, but when I tested from Europe is when it failed. Not everywhen in Europe. For instance, it worked fine in UK and Germany, but badly in Spain and Italy. I tried to reach out to CF to understand how they distribute, what's their transit, etc with no luck
We also checked we were being sent to right POP based on location, and we were. In Spain we were sent to Madrid's POP. I'm in NA, so manually tweak my DNS to connect to the POPs where my testers were reporting as failing. And here's the weird. From NA, connecting to Frankfurt POP, I had no problem streaming (neither testers in the area), but when connecting to Spain, I saw the fails right there.
Anyway, just wanted to share the long test we did before jumping out to another CDN