# Unable to do Cross Cluster Searching in AWS with Instances in Separate Regions **URL:** \ **Category:** Elasticsearch\ **Created:** [October 20, 2020, 3:20pm UTC](https://discuss.elastic.co/t/unable-to-do-cross-cluster-searching-in-aws-with-instances-in-separate-regions/252707 "2020-10-20T15:20:05Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [November 20, 2020, 8:28am UTC](https://discuss.elastic.co/t/unable-to-do-cross-cluster-searching-in-aws-with-instances-in-separate-regions/252707/5 "2020-11-20T08:28:43Z")
This is a terrible idea: it involves exposing these unsecured clusters to the public internet. It's only a matter of time before someone [deletes all your data](https://searchsecurity.techtarget.com/news/252486611/Meow-attacks-wipe-more-than-1000-exposed-databases), or worse. Even with security enabled you should still [not expose clusters to the internet](https://discuss.elastic.co/t/is-it-safe-to-expose-elasticsearch-to-the-internet/247041). It's almost certainly a mistake to even have a public IP on the instances running Elasticsearch nodes. Instead, you should set up [VPC peering](https://docs.aws.amazon.com/vpc/latest/peering/what-is-vpc-peering.html) between your two regions so that the two clusters can see each other without also exposing them to the rest of the world. --- _[View the full topic](https://discuss.elastic.co/t/unable-to-do-cross-cluster-searching-in-aws-with-instances-in-separate-regions/252707)._