Hi,
I want to create a Load Balancer using the AWS Management Console. When I launch a wizard I’m unsure what configuration I must use in Listener Configuration:
Load Balancer Protocol
Load Balancer Port
Instance Protocol
Instance Port
By Default, is HTTP and Port 80,so, should I add/change port 1934 of TCP for Flash? In which fields, Load Balancer or Instance fields?
And What about Health configuration? What values do you recommend me?
You can use the Load Balancer Addon and Wowza EC2 startup packages
The Load Balancer is here
https://www.wowza.com/docs/how-to-get-dynamic-load-balancing-addon
Startup packages are covered in the EC2 guide
https://www.wowza.com/resources/WowzaMediaServerForEC2_UsersGuide.pdf
Richard
You might be able to use that. I don’t have any experience with it. Wowza load balancer uses connection counts, which makes the most sense when network throughput is the limiting factor, which it is in most cases with streaming, and definitely is true with EC2.
Richard
Yes, a properly configured Load Balancer Sender/Edge server will announce itself to the LB Listener.
Richard
This means that I can’t use Amazon’s Load Balancer? 
If I use Wowza’s Dynamic Load Balancer in an instance and a “origin” server, and then use autoscaling to launch automatically a new instance, Will origin server get noticed about the new instance?
If I use Wowza’s Dynamic Load Balancer in an instance and a “origin” server, and then use autoscaling to launch automatically a new instance, Will origin server get noticed about the new instance?
We already setup an Load Balancer “listener” server instance and an “edge” server instance.
When we access to the http://[loadbalancer-ip]:1935/loadbalancer, we get a edge IP:
redirect=[edge-server]
But when we look at the “wowzamediaserver_error.log” located in the origin server, we got this:
ModuleLoadBalancerRedirector.onAppStart[Myapp/_definst_]: LoadBalancerListener not found. All connections to this application will be refused.
Why am I getting this error log even when I access to “http://[loadbalancer-ip]:1935/loadbalancer” appears the edge server properly?
Note: We are using a converted EBS-backed instances of Wowza Media Server 2 for EC2.