Problem is that faced was when we pointed the DNS to ELB, It was not able to get certificate validation from LetsEncrypt however it worked when we did edited DNS to EC2 servers IP. --> This is OK if we have one server but what if we have many servers it won't work. Hence, we want this LetsEncrypt to
Letsencrypt still needs to use port 80. If your ELB is only forwarding port 443 for normal traffic you can use the following approach.
For extra points you can normally have port 80 disabled on your ELB and only open it when doing the renewal request.
Example setup is here: https://blog.cloudinvaders.com/installing-a-lets-encrypt-certificate-on-an-elastic-load-balancer/