Hey guys I was wondering if this seems like a viable solution to the age old problem of Amazon Elastic Load Balancer's lacking a dedicated IP, and thus A record support.

What if I created a micro/small instance and hooked it to an elastic IP. I can then use that IP as my A record address for my website. That instance will forward 100% of its traffic to an ELB load balancer address (Haproxy?), which will then operate normally and forward that traffic to my server pool.

With this architecture I can use my A-record and an ELB. 

* Are there any downsides to this aside from the cost of the initial instance that forwards its traffic to the ELB?
* Will this double forwarding create too much lag or is it really negligible since they're all in AWS?

Thanks for feedback.