# How to Secure ElasticSearch **URL:** \ **Category:** Elasticsearch\ **Created:** [January 6, 2015, 11:21am UTC](https://discuss.elastic.co/t/how-to-secure-elasticsearch/21502 "2015-01-06T11:21:05Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Junie\_Bonifacio](https://avatars.discourse-cdn.com/v4/letter/j/8dc957/32.png) [@Junie\_Bonifacio](https://discuss.elastic.co/u/Junie_Bonifacio)\ **Post date:** [January 6, 2015, 11:21am UTC](https://discuss.elastic.co/t/how-to-secure-elasticsearch/21502/1 "2015-01-06T11:21:05Z")
Hi, We are using Google Compute Engine to deploy our applications (running on top of CentOS Linux). Is there any written reference on the best practices to secure our ElasticSearch instance running on the cloud? Best regards -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/cf257f42-f5ed-4a64-8976-04330155ce31%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/cf257f42-f5ed-4a64-8976-04330155ce31%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [January 6, 2015, 7:25pm UTC](https://discuss.elastic.co/t/how-to-secure-elasticsearch/21502/2 "2015-01-06T19:25:17Z")
Unfortunately not, this is left as an exercise to the administrator. People have used reverse proxies (nginx/apache) and iptables though, if that helps. On 6 January 2015 at 22:21, Junie Bonifacio [junie.bonifacio@gmail.com](mailto:junie.bonifacio@gmail.com) wrote: > Hi, > > We are using Google Compute Engine to deploy our applications (running on > top of CentOS Linux). > > Is there any written reference on the best practices to secure our > Elasticsearch instance running on the cloud? > > Best regards > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/cf257f42-f5ed-4a64-8976-04330155ce31%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/cf257f42-f5ed-4a64-8976-04330155ce31%40googlegroups.com) > [https://groups.google.com/d/msgid/elasticsearch/cf257f42-f5ed-4a64-8976-04330155ce31%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/cf257f42-f5ed-4a64-8976-04330155ce31%40googlegroups.com?utm_medium=email&utm_source=footer) > . > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAEYi1X9U7wfreXBcP18s54SEMjPsETbMLpQdqPxDK-SdNoyNuA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X9U7wfreXBcP18s54SEMjPsETbMLpQdqPxDK-SdNoyNuA%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Itamar\_Syn\_Hershko](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/itamar_syn_hershko/32/725_2.png) [@Itamar\_Syn\_Hershko](https://discuss.elastic.co/u/Itamar_Syn_Hershko)\ **Post date:** [January 6, 2015, 7:43pm UTC](https://discuss.elastic.co/t/how-to-secure-elasticsearch/21502/3 "2015-01-06T19:43:43Z")
There are a few transport plugins that do that as well, see [GitHub - Asquera/elasticsearch-http-basic: HTTP Basic Authentication for Elasticsearch (Discontinued)](https://github.com/Asquera/elasticsearch-http-basic) for example -- Itamar Syn-Hershko [http://code972.com](http://code972.com) | @synhershko [https://twitter.com/synhershko](https://twitter.com/synhershko) Freelance Developer & Consultant Author of RavenDB in Action [http://manning.com/synhershko/](http://manning.com/synhershko/) On Tue, Jan 6, 2015 at 1:21 PM, Junie Bonifacio [junie.bonifacio@gmail.com](mailto:junie.bonifacio@gmail.com) wrote: > Hi, > > We are using Google Compute Engine to deploy our applications (running on > top of CentOS Linux). > > Is there any written reference on the best practices to secure our > Elasticsearch instance running on the cloud? > > Best regards > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/cf257f42-f5ed-4a64-8976-04330155ce31%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/cf257f42-f5ed-4a64-8976-04330155ce31%40googlegroups.com) > [https://groups.google.com/d/msgid/elasticsearch/cf257f42-f5ed-4a64-8976-04330155ce31%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/cf257f42-f5ed-4a64-8976-04330155ce31%40googlegroups.com?utm_medium=email&utm_source=footer) > . > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAHTr4Zu%3D1GT5jM3r3uCEgj%2B%3D1cY0-xFdj1TPeiAfto-QdEezyg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAHTr4Zu%3D1GT5jM3r3uCEgj%2B%3D1cY0-xFdj1TPeiAfto-QdEezyg%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 12:40am UTC](https://discuss.elastic.co/t/how-to-secure-elasticsearch/21502/4 "2017-07-06T00:40:26Z")