Comments on: Amazon Elastic Load Balancer Setup

By: Steve

Steve — Fri, 18 Jun 2010 03:25:11 +0000

Unfortanently right now there is no way to determine the source IP.

By: David

David — Thu, 17 Jun 2010 11:24:34 +0000

I’m seeing that all my logs behind the scenes now register the ELB’s internal IP address 10.x.x.x instead of their public address.

Is there any way you can pass through the public IP for the ELBs request to the web server instances?

By: Steve

Steve — Fri, 26 Mar 2010 20:31:13 +0000

Geng,

Your best solution is to use DNS to route clients to the closest webfarm. So you would want a ELB instance in each region (EU-West, US-East, US-West) and have your DNS provider hand out the IP address of the ELB instance which it thinks is closest geographically to the client.

If you need some guidance around GeoDNS let me know.

By: Geng

Geng — Fri, 26 Mar 2010 17:03:56 +0000

Good article. I have instances running in all three regions (West, East and Ireland). I like requests coming from those regions to use the ELB instance close to them to reduce latency. I have one single branded URL and all users will access using that URL. Is ELB able to direct traffic based on where the request is coming from? Is that possible to do? Thanks in advance.

By: Steve

Steve — Thu, 21 Jan 2010 22:45:00 +0000

Son Nguyen,

I don’t have any details but I do know that Amazon is aware of the shortcomings of the CNAME solution and has a plan in place to resolve the issue. I have no details on how or when they are going to do that though.

By: Son Nguyen

Son Nguyen — Thu, 21 Jan 2010 21:27:00 +0000

Does anyone have an idea when Amazon will offer mapping an elastic IP to the load balancer? CNAME is not a good solution for many (those that want a hybrid solution, mixing EC2 with other clusters for HA, or those that want mapping to the main domain)

By: Steve

Steve — Tue, 19 Jan 2010 07:27:18 +0000

Robin,

Thanks for commenting. I don’t have a solution for you unfortunately. I have a few contacts at Amazon and I’ll see if I can get you an answer. At the very least hopefully they can pass the shortcoming along and it can be resolved in a future version of ELB.

By: Robin

Robin — Sun, 17 Jan 2010 23:20:31 +0000

Hi Steve,

My Colleague and I both have the same issue as Bryan. We really need to be able to lock down access to the load balancer by security group.

Not being able to do this prevents us from providing restricted scalable services!!!

Any ideas on how to get around this?

Thanks!

By: Steve

Steve — Tue, 12 Jan 2010 18:47:33 +0000

What happens if you shutdown the instance getting all the traffic? Does the traffic divert to the other instance?

My initial thought is that if it is configured correctly (which it sounds like it is, especially if the test above passes) your tests are probably just not pushing enough traffic to see it use both nodes. If your just simply hitting it with your web browser you probably are not getting enough concurrent sessions for the traffic to diverge.

By: Arnaud

Arnaud — Tue, 12 Jan 2010 12:45:10 +0000

Great post on how to setup/etc!

You mentioned in the article that balancing is done at a zone level first, then within the zone. I created a ELB with 1 server in each zone, but when testing it appears that only the first server always gets all the requests.

Healthcheck reports both instances available, and I see access to the “ping” page regularily as defined.

Is this expected behavior, or is it possible to round robin between zones ?

Thanks…