Comments on: Load Balancing IIS Web Farm on Amazon EC2

By: Claris Opaka

Claris Opaka — Fri, 19 Mar 2010 14:47:52 +0000

Good Site on Cloud Computing and SaaS – We are periodically looking for good blog information
related to Rackspace Cloud. Also we are looking for contributors to add value to our blog.

Keep up the good work!

Thanks

By: Mickey Flauding

Mickey Flauding — Fri, 19 Feb 2010 15:28:10 +0000

I’ve just come across your site regarding Cloud Computing and Virtualization. There is some good information and we may be interested in including you in our blog. Please feel free to contact. Cheers

By: Son Nguyen

Son Nguyen — Thu, 21 Jan 2010 21:24:02 +0000

Up to the moment, EC2 LB solution still requires a CNAME record instead of mapping to an elastic IP. This is a deal breaker for many.

By: Shima Root » Balanceamento em uma Cloud EC2 da Amazon

Shima Root » Balanceamento em uma Cloud EC2 da Amazon — Mon, 06 Jul 2009 19:54:00 +0000

[...] Balancing IIS Web Farm on Amazon EC2: http://sevans.info/2009/04/20/load-balancing-iis-web-farm-on-amazon-ec2/ Categories: Sem categoria Tags: Comentários (0) Trackbacks (0) Deixar um [...]

By: Steve Trefethen

Steve Trefethen — Wed, 17 Jun 2009 06:06:19 +0000

Great post, the details are much appreciated! Now, off to your follow-up post discussing the ELB…

By: Steve

Steve — Fri, 05 Jun 2009 19:35:53 +0000

Keith,

I stopped worrying about HAProxy once Amazon released Elastic Load Balancer. It’s cheaper and a lot less work to implement. I wrote a post about it at http://sevans.info/2009/05/20/amazon-elastic-load-balancer-setup/

By: Keith B

Keith B — Fri, 05 Jun 2009 16:48:19 +0000

Excellent post. Curious if you’ve had a chance to get anything documented on more detailed steps to setup HAProxy in EC2?

By: Amazon Releases Load Balancing | Serk

Amazon Releases Load Balancing | Serk — Tue, 19 May 2009 03:19:44 +0000

[...] Load Balancing IIS Web Farm on Amazon EC2 [...]

By: Justin Couto

Justin Couto — Wed, 22 Apr 2009 16:41:24 +0000

I have not played with EC2 yet, but I would imagine you could also use Windows Server Routing & Remote Access to provide a router front-end for your load balancer. If you are going to run windows servers in with NLB, you most likely are going to need a domain controller. Your domain controller machine could second as a router and could work as follows:

Create a Domain Controller

Install Routing and Remote Access (RAS) with VPN

Install RAS on all of your Web Servers with VPN and setup a two-way constant VPN between the web servers and the domain controller. This would create a local network and provide each of the Web Servers with an internal IP (ex: 192.168.25.X).

Add an additional internal IP to the Web Server nic.

Setup NLB using a shared internal IP across all web servers

Set you domain names DNS to point to your Domain Controllers Public IP Address

Set Routing and Remote Access to route all connections on port 80 & 443 to your internal NLB load balancer IP. This would cause all web traffice to get routed to the internal address of the Windows Network Load Balance.

Again, I have not tried this scenario. However, I believe it would work as long as you can assign multiple IPs to your VMs NIC. Another drawback is that this has a single point of failure (Domain Controller), although that could be adressed.

Let me know if you get a chance to try it

Great Article by the way!