# Setup Elasticsearch cluster on Multi-Cloud(AWS and GCP)

**URL:** <https://discuss.elastic.co/t/setup-elasticsearch-cluster-on-multi-cloud-aws-and-gcp/230065>\
**Category:** Elasticsearch\
**Tags:** ccs-cross-cluster-search\
**Created:** [April 28, 2020, 3:01am UTC](https://discuss.elastic.co/t/setup-elasticsearch-cluster-on-multi-cloud-aws-and-gcp/230065 "2020-04-28T03:01:12Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Taewoo](https://avatars.discourse-cdn.com/v4/letter/t/5f9b8f/32.png) [@Taewoo](https://discuss.elastic.co/u/Taewoo)\
**Post date:** [April 28, 2020, 3:01am UTC](https://discuss.elastic.co/t/setup-elasticsearch-cluster-on-multi-cloud-aws-and-gcp/230065/1 "2020-04-28T03:01:12Z")

</div>

Hello? I'm newbie to Elasticsearch.

I'm planning to manage Multi-Cloud logs using Elasticsearch.

Some of nodes are in AWS and other nodes are in GCP. (Let's assume each public cloud's instances are in same vpc)

I came here to get advise of how to make cluster. I have 2 options.

1. Make all multi cloud nodes in one elastic cluster.

- Add one Master node to AWS and set all other nodes to data nodes in aws and gcp.
- Add all those nodes(AWS and GCP) to one elastic cluster.

1. Set each public cloud to each cluster and use cross-cluster join.

- Add Master node to each aws and gcp cluster. And then make each cluster in each public cloud.
- So this scenario have 2 different elastic cluster in AWS and GCP.
- Use Cross-cluster query when we want all of documents.

Which one is better? Does each option have pros and cons?  
Or is there any good option for managing multi-cloud logs using one cluster?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [April 28, 2020, 4:25am UTC](https://discuss.elastic.co/t/setup-elasticsearch-cluster-on-multi-cloud-aws-and-gcp/230065/2 "2020-04-28T04:25:38Z")

</div>

1. Nope, you'll run into a tonne of issues with latency and network issues.
2. Ideally, yes.

You could, also, have the Elasticsearch cluster in a totally different provider, eg Azure.

---

<div class="post-metadata">

**Author:** ![Taewoo](https://avatars.discourse-cdn.com/v4/letter/t/5f9b8f/32.png) [@Taewoo](https://discuss.elastic.co/u/Taewoo)\
**Post date:** [April 28, 2020, 6:25am UTC](https://discuss.elastic.co/t/setup-elasticsearch-cluster-on-multi-cloud-aws-and-gcp/230065/3 "2020-04-28T06:25:14Z")

</div>

Thank you for your reply.

So it means that.. now there is no solution for mutli-cloud or multi-region(which communicate with public network) right?

So then best alternative solution is to construct cluster to each public cloud(aws, gcp) and query on cross cluster right?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [April 28, 2020, 7:46am UTC](https://discuss.elastic.co/t/setup-elasticsearch-cluster-on-multi-cloud-aws-and-gcp/230065/4 "2020-04-28T07:46:44Z")

</div>

The solution is cross cluster search 🙂

---

<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:** [May 26, 2020, 7:59am UTC](https://discuss.elastic.co/t/setup-elasticsearch-cluster-on-multi-cloud-aws-and-gcp/230065/5 "2020-05-26T07:59:52Z")

</div>

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