# Installing custom Elasticsearch plugins in Elastic Cloud **URL:** \ **Category:** Elasticsearch\ **Tags:** elastic-stack-security\ **Created:** [July 30, 2022, 8:51am UTC](https://discuss.elastic.co/t/installing-custom-elasticsearch-plugins-in-elastic-cloud/311032 "2022-07-30T08:51:36Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![Simone\_Scarduzio](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/simone_scarduzio/32/17128_2.png) [@Simone\_Scarduzio](https://discuss.elastic.co/u/Simone_Scarduzio)\ **Post date:** [August 1, 2022, 8:49am UTC](https://discuss.elastic.co/t/installing-custom-elasticsearch-plugins-in-elastic-cloud/311032/5 "2022-08-01T08:49:47Z")
Yes, what you said makes total sense. And having two clusters in CCS is equally good, if not even better in term of separation of concerns. We can keep all the data in the Elastic Cloud, and we can have a tiny ~empty cluster configured to cross-cluster search to the Cloud one, and from there we are just going to refer to indices as "cloud\_cluster:index\_xyz" instead of "index\_xyz". If this is ok for you, I think this is the way forward. So the only knot remaining here is the very "practical" format issue in the cert exchange, as I talked about [in my other topic](https://discuss.elastic.co/t/elastic-cloud-configuring-trust-with-clusters-in-a-self-managed-environment/311035). --- _[View the full topic](https://discuss.elastic.co/t/installing-custom-elasticsearch-plugins-in-elastic-cloud/311032)._