ooh, this looks really problematic on multiple levels (why wait for JS etc).
A simple solution, which I've used--and I think the OPs situation is similar--is to just have an additional A-record pointed to the ELB, this should work unless the OP is doing something really fancy. No need for route-53, even go-daddy will let you do this.
However, route-53 gives you much better TTL, so if you ever need to re-route..
A simple solution, which I've used--and I think the OPs situation is similar--is to just have an additional A-record pointed to the ELB, this should work unless the OP is doing something really fancy. No need for route-53, even go-daddy will let you do this.
However, route-53 gives you much better TTL, so if you ever need to re-route..