On Feb 8, 2012, at 2:49 AM, Baptiste wrote: > Hi, > > This kind of scenario is really dependent from your configuration. > Basically, you want to configure HAProxy to load-balance SSL services > hosted by your application servers.
That is correct. > Persistence based on SSLID into HAProxy, sharing the stick-table > between both haproxy. Right, that way any one of the pair of HAProxy server would know where to send the request from client. > This may work, but be carefull with the "peers" section, since your LB > will change their IP addresses each time they'll reboot... Right, the internal IP changes since it is on DHCP. But I was thinking of assigning static IP (EIP in Amazon term) to the HAProxies. And then refer to each other via those EIP. Here is a quick and dirty diagram of howI am thinking of implementing. Ofcourse the main cost is the static IP addresses that I have to get from Amazon. Thanks Baptiste.
PastedGraphic-1.pdf
Description: Adobe PDF document
> > cheers > > > On Tue, Feb 7, 2012 at 1:56 AM, Mir Islam <[email protected]> wrote: >> Hi, I am thinking of the following scenario to implement in AWS. >> >> Two HAProxies with SSL stickiness, TCP pass through and in peer mode. Using >> Amazon ELB to do round robin load balance between the two server. Basically >> the idea is to create automatic failover for HA proxy servers. Theoretically >> it should work since both of the servers have the same session information. >> Am I wrong on this assumption? >> >> Thanks >> Mir
