Wowza Community

how many individual streams can be run through Wowza on an EC2 instance?

I’m currently streaming twenty webcams through FMS (480 x 360 @ 250K each). Each webcam “pushes” a permanent stream to FMS, which is routed to the client after they request the stream from a website.

Can I replicate this on Wowza/EC2? If so, what kind of instance would be required? (small, medium, large).

Maximum usage at any one time would be twenty consecutive inbound streams (all at 250K, ie 5K inbound), and up to 300 outbound streams, being any configuration of the twenty inbound streams - so around 75MB outbound (although it’s usually much lower than this). Additionally, I’d like to transcode the inbound H.264 stream in real time for rtmp and http delivery.

A small instance should be able to handle this. The latest AMI running Wowza Server 2 will stream out to RTMP clients and HTTP Apple (Cupertino) and Silverlight clients (it’s not actually transcoding). Wowza does not handle progressive download over http (but the Wowza EC2 instances do have an apache server on them used for Cacti)


The current pricing posted is correct. There are not charges for inbound data transfer.


The license is unlimited connections. The real limit is bandwidth, about 150mbs on a small instance


Yes, bandwidth charges apply also.

For RTMP streaming Wowza does not shutdown incoming stream if no client is connected. So if you have a rtmp stream running 24/7 with no clients, it will rack-up charges.

For re-streaming rtsp streams it should be true that if no clients are connected that there will not be bandwidth charges for incoming rtsp stream.

You really have to test your use case on small instance or any instance type.


There isn’t updated info. Running the Wowza load test tool is the best way to get a real idea what the capacity is on any server.


Along this same line, if a small instance is adequate for the example in this thread and it is expected to be available 24/7, the cost would be around $110/month for that small instance on EC2 as I understand it, correct?

Could you explain in this case of live streaming, must the cost of Data Transfer In at $0.10/GB and Data Transfer Out at $0.15/GB be added to this monthly total since the live streaming is data coming in and immediately going back out each time a connection (client) is made, unlike VOD that is stored? So overall would it be a true assumption that live streaming is more costly per GB than VOD streaming?

Also I assume that EC2 for Wowza reacts the same as Wowza Server does otherwise, in that if no client is requesting a connection then Wowza kills the data stream coming in also correct?

Just attempting to characterize monthly costs for live video streaming utilizing a small instance similar to described above.

Thanks for any info.

Thanks Richard. How many streams can each license of Wowza handle? Is there a fixed number, or is the number dependent on the combined bandwidth throughput?

Great… thanks Richard.

Has the pricing changed since this post? Currently it indicates no charge for inbound data.

I am about to go live with a solution that would publish a live stream 24/7, and this thread had me a bit scared, but seems no longer relevant.

Just wanted to bump this thread real quick. I’m creating live streams on wowza using VOD content. Do you have a specs on how many streams can be ran concurrently on a wowza server depending on what kind of EC2 instance i’m running?

Right now i have 9 Applications running each with individual stream on a m1.medium instance and the CPU usage is through the roof (100%). Just wanted to get more understanding to launch a proper PROD stack. Thanks again for the help

We are trying to estimate cost for our application. If there is 1 viewer per input stream, how many streams (N input +N output) a wowza instance on c3.large instance can support?

Thank you!