title: How to secure an Internet-facing Elastic Search implementation in a shared hosting environment?
body: <p>I've been going over the documentation for <a href="http://www.elasticsearch.org/">Elastic Search</a> and I'm a <em>big</em> fan and I'd like to use it to handle the search for my ASP.NET MVC app.</p>
  
  <p>That introduces a few interesting twists, however.  If the ASP.NET MVC application was on a dedicated machine, it would be simple to spool up an instance of Elastic Search and use the <a href="http://www.elasticsearch.org/guide/reference/modules/transport.html">TCP Transport</a> to connect locally.</p>
  
  <p>However, I'm not on a dedicated machine for the ASP.NET MVC application, nor does it look like I'll move to one anytime soon.</p>
  
  <p>That leaves hosting Elastic Search on another machine (in the *NIX world) and I would probably go with shared hosting there.</p>
  
  <p>One of the biggest things lacking from Elastic Search, however, is the fact that it doesn't support HTTPS and basic authentication out of the box.  If it did, then this question wouldn't exist; I'd simply host it somewhere and make sure to have an incredibly secure password and HTTPS enabled (possibly with a self-signed certificate).</p>
  
  <p>But that's not the case.</p>
  
  <p>That given, what is a good way to expose Elastic Search over the Internet in a secure way?</p>
  
  <p>Note, I'm looking for something that hopefully, will not require writing code to provide shims for the methods that I want (in other words, writing forwarders).</p>