I'm trying to figure out a way to get high availability with the Wowza DevPay AMIs. The load balancing is fine (haven't implemented it yet), but it's a single point of failure. I figured I'd get around that by putting an Elastic Load Balancer in front of a Wowza load balancer in multiple availability zones. However, I'm unable to add the Wowza DevPay AMI instances to the ELB.
What's the best way of setting up Wowza to use multiple availability zones, without a single point of failure?
Should I use a regular license for the load balancing instances in each availability zone, then use the DevPay AMIs for handing the recording of streams?
You can configure multiple Load Balancer Listeners for an edge by adding additional lines to the loadbalancertargets.txt file when configuring the Load Balancer sender on each edge.
You can have multiple pipe delimited Liverepeater origin servers defined either in Application.xml /originURL "rtmp://[wowza-address]:1935/origin1|rtmp://[wowza-address]:1935/origin2", or in a .stream file, also pipe delimited, but including stream name. "rtmp://[wowza-address]:1935/origin1/stream1|rtmp://[wowza-address]:1935/origin2/stream1"
For failing over listeners you could look at something like
LVS for a ip based failover. You could likely handle specific redirect IP's by modifying the existing load balancer (via ModuleLoadBalancerRedirector.java for rtmp connections etc).