title: Support for two-way TLS/HTTPS with ELB
body: <p>One way (or server side) TLS/HTTPS with Amazon Elastic Load Balancing is <a href="http://docs.aws.amazon.com/ElasticLoadBalancing/latest/DeveloperGuide/elb-listener-config.html">well documented</a> </p>
  
  <p>Support for two-way (or client side) TLS/HTTPS is not as clear from the documentation.</p>
  
  <p>Assuming ELB is terminating a TLS/HTTPS connection:</p>
  
  <ol>
  <li>Does ELB support <a href="https://en.wikipedia.org/wiki/Transport_Layer_Security#Client-authenticated_TLS_handshake">client authenticated</a> HTTPS connections?</li>
  <li>If so, does a server served by ELB recieve a <a href="http://docs.aws.amazon.com/ElasticLoadBalancing/latest/DeveloperGuide/TerminologyandKeyConcepts.html#x-forwarded-headers">X-Forwarded-*</a> header to identify the client authenticated by ELB? </li>
  </ol>
  
  <p>ELB does support TCP forwarding so an EC2 hosted server can establish a two-way TLS/HTTPS connection but in this case I am interested in ELB terminating the TLS/HTTPS connection and identifying the client. </p>