# Enable Cross Cluster Search vs Monitoring

**URL:** <https://discuss.elastic.co/t/enable-cross-cluster-search-vs-monitoring/324749>\
**Category:** Elasticsearch\
**Tags:** elastic-stack-monitoring\
**Created:** [February 5, 2023, 9:50pm UTC](https://discuss.elastic.co/t/enable-cross-cluster-search-vs-monitoring/324749 "2023-02-05T21:50:17Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![stefws](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stefws/32/6442_2.png) [@stefws](https://discuss.elastic.co/u/stefws)\
**Post date:** [February 5, 2023, 9:50pm UTC](https://discuss.elastic.co/t/enable-cross-cluster-search-vs-monitoring/324749/1 "2023-02-05T21:50:17Z")

</div>

Just installed a ES cluster 8.6.1 and a Kibana 8.6.1, trying to enable cluster monitoring, but attempting to access monitoring app from kibana, it just tells me that my cluster has monitoring.ui.ccs.enabled=true. Dunno howto revert this settings and forgot if I actually did began to turn this on few days ago, when I initially considered to allow this new cluster to be Cross Cluster Searchable from a former single node PoC cluster...

Hints appreciated, TIA!

 ![Screenshot 2023-02-05 at 22.43.44](https://us1.discourse-cdn.com/elastic/original/3X/2/9/29e349ccc80bb441749445e0cadd889047f38364.png)

---

<div class="post-metadata">

**Author:** ![Venkata\_Raja](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/venkata_raja/32/114264_2.png) [@Venkata\_Raja](https://discuss.elastic.co/u/Venkata_Raja)\
**Post date:** [February 6, 2023, 5:13am UTC](https://discuss.elastic.co/t/enable-cross-cluster-search-vs-monitoring/324749/2 "2023-02-06T05:13:08Z")

</div>

Hi Steffen,

you can change configuration in .yml file if you wanted to disable CCS.  
Check whether your user has above mentioned roles or not , if not add them to access monitoring. go to Stack Management -\> users

---

<div class="post-metadata">

**Author:** ![stefws](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stefws/32/6442_2.png) [@stefws](https://discuss.elastic.co/u/stefws)\
**Post date:** [February 6, 2023, 11:16am UTC](https://discuss.elastic.co/t/enable-cross-cluster-search-vs-monitoring/324749/3 "2023-02-06T11:16:24Z")

</div>

> [@stefws](#):
>
> monitoring.ui.ccs.enabled=false

Solved with this option in kibana.yml + restart, user had required roles.

Assume default true is good to urge people to use a separate monitoring cluster maybe, but it properly confuse a lot of community lusers, maybe add default value into sample/default kibana.yml with comments on usage/purpose of setting 🙂

---

<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:** [March 6, 2023, 11:17am UTC](https://discuss.elastic.co/t/enable-cross-cluster-search-vs-monitoring/324749/4 "2023-03-06T11:17:23Z")

</div>

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