# Cross-cluster search between ECE2.2 cluster and non-ECE cluster not working

**URL:** <https://discuss.elastic.co/t/cross-cluster-search-between-ece2-2-cluster-and-non-ece-cluster-not-working/183131>\
**Category:** Elasticsearch\
**Created:** [May 28, 2019, 2:40pm UTC](https://discuss.elastic.co/t/cross-cluster-search-between-ece2-2-cluster-and-non-ece-cluster-not-working/183131 "2019-05-28T14:40:01Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![jethropickering](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jethropickering/32/83736_2.png) [@jethropickering](https://discuss.elastic.co/u/jethropickering)\
**Post date:** [May 28, 2019, 2:40pm UTC](https://discuss.elastic.co/t/cross-cluster-search-between-ece2-2-cluster-and-non-ece-cluster-not-working/183131/1 "2019-05-28T14:40:01Z")

</div>

Environment:

ECE 2.2, Elastic 7.1 Cluster  
Non-ECE, Elastic 6.7.1 Cluster

So according to docs 6.7.1 should be able to CCS to 7.1. However I am getting "General SSLEngine problem" and "unable to find valid certification path to requested target".

Some of the ECE documentation says CCS only works within the same ECE environment, can anyone confirm this?

I have already confirmed that:  
Transport certs signed with the same master cert  
IP/PORT are correct  
Ports are reachable from both sides  
no filtering  
tls versions compatible

I have a theory that since ECE uses client profile, even though I am providing the public seeds, perhaps it is trying to come back from or use the local 172 client ip and port for the transport layer.

Would really appreciate any help here.

---

<div class="post-metadata">

**Author:** ![Janko](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/janko/32/26896_2.png) [@Janko](https://discuss.elastic.co/u/Janko)\
**Post date:** [May 28, 2019, 5:48pm UTC](https://discuss.elastic.co/t/cross-cluster-search-between-ece2-2-cluster-and-non-ece-cluster-not-working/183131/2 "2019-05-28T17:48:48Z")

</div>

Hi @jethropickering and welcome to the Elastic Discuss forum!

Indeed, as per the [documentation](https://www.elastic.co/guide/en/cloud-enterprise/2.2/ece-enable-ccs.html#ece-before_you_begin_23) currently, to enable CCS `All clusters must be in the same same Elastic Cloud Enterprise environment.`

At this time I am not aware of a possible workaround, but please contact your support agent to check and raise an enhancement request for this.

---

<div class="post-metadata">

**Author:** ![jethropickering](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jethropickering/32/83736_2.png) [@jethropickering](https://discuss.elastic.co/u/jethropickering)\
**Post date:** [May 28, 2019, 6:05pm UTC](https://discuss.elastic.co/t/cross-cluster-search-between-ece2-2-cluster-and-non-ece-cluster-not-working/183131/3 "2019-05-28T18:05:53Z")

</div>

Thanks for the quick reply Janko.  
Will definitely raise with the reps tomorrow, this is something that makes transitioning either a lot easier or a lot harder if like us you can't go cold turkey straight away and need to things piecemeal into ECE.  
Thanks again.

---

<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:** [June 25, 2019, 6:05pm UTC](https://discuss.elastic.co/t/cross-cluster-search-between-ece2-2-cluster-and-non-ece-cluster-not-working/183131/4 "2019-06-25T18:05:54Z")

</div>

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