Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Let say I have the website domain http://myawesomesite.com, and to start I have a ELB setup on the US-EAST Region with 2 instances running my application.

As the site becomes more awesome and I want to start serving my application faster I setup instances in the US-WEST group, with an ELB. How can I forward traffic to the nearest data center?

share|improve this question

4 Answers 4

Well, this is a common problem called Geographical Load Balancing, and I think that Amazon Web Services team have done good points with ELB.

  1. Here on the ELB Guide, you can view how to add EC2 instance and, this show too the availablity zones of your ELB:

  2. and here, you can see a detailed post about how to install ELB

Other resources to use CoyotePoint Systems Inc have a solution for this, and F5 too

regards and best wishes

share|improve this answer
1  
ELB doesn't do geographic load balancing yet. –  ceejayoz Dec 1 '11 at 17:42

You cannot do this with the ELB. Consider using a DNS provider who offers GSLB (Global Server Load Balancing) or similar services.

That said, you don't need GSLB. You can start considering GSLB when you have several hundred servers across several AZs in us-east-1. Oh, and revenue.

share|improve this answer

You can do this with Amazon Route 53 which now supports Multi-Region Latency Based Routing.

share|improve this answer

To use Route53 to do GSLB you need to :

  1. have your ELBs in the same account
  2. have your Hosted zone in that same account as the ELBs
  3. In route53 create Alias records, and choose IPv4 and choose the ELBs from the drop down list of resources to add primary and secondary (for a Failover scenario)

then add latency records on top of that if needed which all point to the same The key is to choose the ipv4 for aliases (not obvious to me)

My issue is that since my ELBs are in different accounts, and the ELBs use hostname/CNAME records, GSLB cannot point LB pool records to CNAMES, only A-Records which AWS doesn't want you to point to.
http://tools.ietf.org/html/rfc1034 section 3.6.2

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.