|
I've got a site that I'm scaling up with Amazon's EC2. I would like to use the Elastic Load Balancer service as my frontend load balancer in front of haproxy to deal with reliability and load issues. ELB currently requires a CNAME record to function (www -> http://somelongname.elb.amazonaws.com). We're already using http://www.mydomain.com because of a wildcard dns cert but I don't want to have to deal with the http://mydomain.com to http://www.mydomain.com 302 redirect. I'm already using Custom DNS for the domain. Is there any reason why I wouldn't be able to use a WebHop redirect to redirect traffic from http://mydomain.com to http://www.mydomain.com outside of EC2? |
|
Except for the fact that a WebHop isn't a CNAME you mean? That depends entirely on Amazon, though it's entirely possible that they won't know enough about WebHop to answer. I'd guess that it should work just fine - the uncloaked version is just a 302 redirect itself after all. Right. I want to use WebHop to redirect my root to a CNAME I control which points to the elastic load balancer.
Feb 02 at 05:34 PM
ryansch
|
|
So, I understand that you need to have a CNAME pointing at http://something.amazonaws.com (such as http://www.mydomain.com). And obviously, if users shall be able to reach the same site using just the base domain name (mydomain.com), you'll need to set up some sort of redirection (since you can't have a CNAME on the base domain name). I see no problem with using a WebHop like this. The target system wouldn't even know. It should work equally well with a cloaked WebHop and an uncloaked WebHop, but you probably want to keep it uncloaked. Agreed. Thanks for the feedback. I'll report back here after I test it out.
Feb 02 at 05:35 PM
ryansch
|
Question not revisited by the originator in one month. Closing to stop the forum bot bumping it.