# Per/Node Ip FIlters in Cluster Settings

**URL:** <https://discuss.elastic.co/t/per-node-ip-filters-in-cluster-settings/199384>\
**Category:** Elasticsearch\
**Created:** [September 13, 2019, 8:11am UTC](https://discuss.elastic.co/t/per-node-ip-filters-in-cluster-settings/199384 "2019-09-13T08:11:42Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![willemdh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/willemdh/32/16922_2.png) [@willemdh](https://discuss.elastic.co/u/willemdh)\
**Post date:** [September 13, 2019, 8:11am UTC](https://discuss.elastic.co/t/per-node-ip-filters-in-cluster-settings/199384/1 "2019-09-13T08:11:42Z")

</div>

Hello,

Currently we are setting the `xpack.security.http.filter.allow` directive in elasticsearch.yml on all our nodes (12). The configuration is different for master / data nodes and ingest/coordination nodes.

This means that we cannot save this as a cluster setting, as that would mean all the ip's set in the cluster settings are applied to every node. Is there a way to create custom `xpack.security.http.filter.allow` cluster settings for each node? If there is currently no way to do this, would a GitHub enhancement request be an option?

Grtz

Willem

---

<div class="post-metadata">

**Author:** ![willemdh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/willemdh/32/16922_2.png) [@willemdh](https://discuss.elastic.co/u/willemdh)\
**Post date:** [October 10, 2019, 11:16am UTC](https://discuss.elastic.co/t/per-node-ip-filters-in-cluster-settings/199384/2 "2019-10-10T11:16:55Z")

</div>

Anyone?

---

<div class="post-metadata">

**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\
**Post date:** [October 11, 2019, 12:19pm UTC](https://discuss.elastic.co/t/per-node-ip-filters-in-cluster-settings/199384/3 "2019-10-11T12:19:11Z")

</div>

Hey,

this is indeed a cluster wide setting currently. Feel free to open an enhancement request though! Please elaborate a little bit more on why this is needed in the issue - I suppose you want to separate between ingest and search clients, but I am just assuming things here 🙂

Thank you!

--Alex

---

<div class="post-metadata">

**Author:** ![willemdh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/willemdh/32/16922_2.png) [@willemdh](https://discuss.elastic.co/u/willemdh)\
**Post date:** [November 6, 2019, 7:35pm UTC](https://discuss.elastic.co/t/per-node-ip-filters-in-cluster-settings/199384/4 "2019-11-06T19:35:23Z")

</div>

@spinscale See [https://github.com/elastic/elasticsearch/issues/47924](https://github.com/elastic/elasticsearch/issues/47924)

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [December 4, 2019, 7:35pm UTC](https://discuss.elastic.co/t/per-node-ip-filters-in-cluster-settings/199384/5 "2019-12-04T19:35:33Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.