502 BadGateway with Amazon ELB and Spring Applicaton

I have an Amazon ELB for my domain www.example.com.At present there is only one node. No Apache, requests direcly goto Spring Application running on tomcat. Port 8443 is used for https. Default home page loads fine - that's http. Any https page throws a 502 bad gateway error. Even https based assets are not loading. Based on the review, I have set the headers as mentioned in Why am I getting a 502 bad gateway when sending a redirect from behind amazon elastic load balancer? , increased time Tomcat threads out also - Bad Gateway 502 error with Apache mod_proxy and Tomcat

Seems to be configuration issue only as suggested at http://ift.tt/1K9mC50

Any reasons to look for 502 on ELB in addition to the ones mentioned in SO links above?

Using self signed certificate as of now. Not sure if that can be a reason. Any ideas on how to cross check if ELB set up with self signed ssl certificate is correct?