# Disable Elastic Security Plugin in ECE **URL:** \ **Category:** Elastic Cloud Enterprise (ECE)\ **Created:** [September 30, 2019, 1:47pm UTC](https://discuss.elastic.co/t/disable-elastic-security-plugin-in-ece/201650 "2019-09-30T13:47:45Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![robrotheram](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/robrotheram/32/27262_2.png) [@robrotheram](https://discuss.elastic.co/u/robrotheram)\ **Post date:** [September 30, 2019, 1:47pm UTC](https://discuss.elastic.co/t/disable-elastic-security-plugin-in-ece/201650/1 "2019-09-30T13:47:46Z")
Hi, I am trialing out ECE and we have a our own custom plugin that implements the rest filter class. This is incompatible with elastic security plugin since it seems that only one plugin can implement the rest filter class. In our clusters we just disable the plugin and run the cluster in its own VLAN can we do this in ECE ---
**Author:** ![Alex\_Piggott](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alex_piggott/32/11053_2.png) [@Alex\_Piggott](https://discuss.elastic.co/u/Alex_Piggott)\ **Post date:** [September 30, 2019, 2:15pm UTC](https://discuss.elastic.co/t/disable-elastic-security-plugin-in-ece/201650/2 "2019-09-30T14:15:15Z")
There is no way of disabling the security plugin in ECE unfortunately - there are lots of internal service accounts that use the basic authentication and authorization features of the security plugin, and the nodes communication to each other are encrypted using the plugins' certificate infrastructure Did you 100% confirm (eg via the elasticsearch forum - I don't think we have the required knowledge here) that there is no workaround for the "two rest filter classes" problem Alex ---
**Author:** ![robrotheram](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/robrotheram/32/27262_2.png) [@robrotheram](https://discuss.elastic.co/u/robrotheram)\ **Post date:** [September 30, 2019, 2:46pm UTC](https://discuss.elastic.co/t/disable-elastic-security-plugin-in-ece/201650/3 "2019-09-30T14:46:53Z")
I found nothing on the forum but the elastic error is reported in other places e.g > **[How to make ReadonlyREST compatible with x-pack plugin?](https://forum.readonlyrest.com/t/how-to-make-readonlyrest-compatible-with-x-pack-plugin/24)** > > I am trying to upgrade ES cluster from 2.4 to 5.2. It seems that x-pack (security) plugin and ReadonlyREST are conflicting each other. We are not using security plugin with our licence. I get the following exceptions on node startup: ... This is for a 6.x Cluster ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [October 14, 2019, 2:46pm UTC](https://discuss.elastic.co/t/disable-elastic-security-plugin-in-ece/201650/4 "2019-10-14T14:46:59Z")
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.