We have been a "Wowza EC2" user for over 3 years. We're a small publishing shop that sometimes does NO livestreaming for weeks, then some days we can stream 4 simultaneous events. As such, we find that the on-demand options of Amazon EC2 is the best choice, and not a perpetual licence, as our usage is quite sporadic.
In the past, we've only used Wowza 2 to do livestreaming, and we publish our recorded videos using Amazon Cloudfront.
99% of our livestreaming efforts are done using Wirecast 4/5, and we've not had any problems.
For the past 3 years, we've always been using the same Wowza 2 EC2 ami (ami-5c649835)- we do so for simplicity, I guess. We like the ease of use, and we really only need the Cacti logs to see how many people logged on to watch our stream. We record our streams locally on a hard drive, and then stream them via Cloudfront after the event.
Now, it seems all the Wowza 2 AMI have been retired, so to speak.
I upgraded to Wowza Streaming Engine last week, but I'm having problems.
We're on the US East Coast, so we use the US East ami-4b889222
But it isn't working (at least with the ease of use we had with the Wowza 2 licence).
I use the same settings I used for Wowza2, but Wirecast error message states "Cannot connect to RTMP/Flash Server at the given IP address. [-4018]"
I wonder if it's an issue with the way in which I upgraded from Wowza 2 to Wowza Streaming Engine?
My Amazon subscription page says I pay $5 per month for Wowza Streaming Engine - http://chilp.it/df2d7e
But the Wowza info page states that it should be $15 per month - http://goo.gl/fv01C7
Was there an error in the way I upgraded from Wowza 2 to Wowza Streaming Engine?
Last week, when we first found we couldn't use our old Wowza 3 ami, we quickly started up a Wowza 3 ami, but we found out we could only use 10 concurrent streams at one time. I've tried to upgrade to Wowza 3 as well (the way I see it, since we only use Wowza for the streaming, and not the nDVR and transcoder, it doesn't really matter if we use Streaming Engine or Wowza 3). But we can't seem to get Wowza 3 (with EC2) working for us either.
What are we doing wrong?