I’ve installed v4.6 on an internal server and tested it successfully with great ease. We were up and running before noon. With that success, and an important live event coming up, we decided to use AWS to host Wowza in the future, so proceeded with the same steps that had worked for us on the local machine.
I turned off the Windows firewall, but we were only able to stream from the server using localhost, so in the rush, we re-installed using one of the prepackaged installation packages, which worked great as well with us up and running in an hour or so.
The problem is that we have no Linux experience in-house, so need to redo the installation on Windows Server. Our first problem was understanding what size of an EC2 instance we need - the choices don’t easily translate to what Wowza recommends:
Minimum recommended production hardware
- CPU: Single quad core, 3.00 GHz or better
- RAM: 4GB
- Disk: 2 or more in RAID 0 (striping)
- Network: 1Gbps Ethernet
High-load recommended production hardware
- CPU: Dual quad-core or a single hex-core, 3.00 GHz or better
- RAM: 16-32GB
- Disk: 2 or more in RAID 0 (striping)
- Network: 10Gbps Ethernet
We stream a live event 4 or 5 times a month, with only 100-200 viewers at any time, then some VOD throughout the month, again, low usage - maybe a few hundred views per month
What EC2 instance options would be best suited for our needs?
Also, as mentioned, we couldn’t get the Windows installation to stream beyond localhost. What additional configuration changes are necessary to run Wowza from an instance of Windows 2012? - the installation set the server IP to a local/private IP of 172...*. Would changing that to the public IP of the EC2 instance have solved my initial Windows installation attempt? We had the Windows firewall off, but can’t leave it that way, so is there a list of ports somewhere that we need to have opened?
