You can filter out HTTP PUT (and DELETE) and get a pretty good approach to not accidentally remove or overwrite anything (due to REST semantics)
Jörg On Fri, Sep 19, 2014 at 5:41 PM, Marie Jacob <[email protected]> wrote: > I'm sure that this has been asked before on the forum, but I couldn't find > an answer specifically for this one: > > Is there any way at all to disable writes over http for elasticsearch? > It's very easy for people to accidentally create indexes that they didn't > mean to create. > If there is no way, I think this would be a GREAT option to add (something > like http.writes_enabled?) ... it seems to be the most basic access control > that would be useful for many use cases. > > > > > > -- > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elasticsearch/5c472d3f-6fe6-40b7-afcf-366430a953d6%40googlegroups.com > <https://groups.google.com/d/msgid/elasticsearch/5c472d3f-6fe6-40b7-afcf-366430a953d6%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAKdsXoHO-26RspwnTYAaFAUA6T12EhjGG39JJtsKTWsT%2BA3a6g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
