# Configuring cross-cloud cluster via REST API **URL:** \ **Category:** Elasticsearch\ **Created:** [June 2, 2014, 10:49am UTC](https://discuss.elastic.co/t/configuring-cross-cloud-cluster-via-rest-api/17855 "2014-06-02T10:49:12Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Martin\_Harris](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/martin_harris/32/1515_2.png) [@Martin\_Harris](https://discuss.elastic.co/u/Martin_Harris)\ **Post date:** [June 2, 2014, 10:49am UTC](https://discuss.elastic.co/t/configuring-cross-cloud-cluster-via-rest-api/17855/1 "2014-06-02T10:49:12Z")
Hi Folks, I'm trying to setup a cross-cloud elastic-search cluster. As it's cross-cloud, the usual discovery will not work, so I've started elasticsearch on three nodes with multicast disabled (discovery.zen.ping.multicast.enabled=false) and unicast enabled (discovery.zen.ping.multicast.enabled=false). I then try to enable the cluster by running the following against one (or all) of the nodes: curl -XPUT [http://localhost:9200/\_cluster/settings](http://localhost:9200/_cluster/settings) -d '{ "persistent" : { "discovery.zen.ping.unicast.hosts":"37.58.110.34:9200,37.58.110.35:9200,37.58.110.36:9200"}}' The curl commands returns the following: {"acknowledged":true,"persistent":{},"transient":{}} But when I check the status of the cluster with the following: curl [http://localhost:9200/\_cluster/settings](http://localhost:9200/_cluster/settings) The curl command returns this: {"acknowledged":true,"persistent":{},"transient":{}}{"acknowledged":true,"persistent":{},"transient":{}} And the cluster has not been initialized The following is also added to the log: [WARN][action.admin.cluster.settings] [elasticsearch-1] ignoring transient setting [discovery.zen.ping.unicast.hosts], not dynamically updateable Any help would be appreciated Cheers Martin Harris -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/ee89982f-0bc3-456b-a9e4-2a06a0b6b0c6%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/ee89982f-0bc3-456b-a9e4-2a06a0b6b0c6%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Itamar\_Syn\_Hershko](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/itamar_syn_hershko/32/725_2.png) [@Itamar\_Syn\_Hershko](https://discuss.elastic.co/u/Itamar_Syn_Hershko)\ **Post date:** [June 2, 2014, 10:57am UTC](https://discuss.elastic.co/t/configuring-cross-cloud-cluster-via-rest-api/17855/2 "2014-06-02T10:57:21Z")
This will not work, discovery is done on port 9300 (by default) and cannot be done over HTTP I think what you are looking for is tribe node - > **[Elasticsearch Platform — Find real-time answers at scale](https://www.elastic.co)** > > Power insights and outcomes with the Elasticsearch Platform and AI. See into your data and find answers that matter with enterprise solutions designed to help you build, observe, and protect. Try Elasticsearch free today. You'll then have 2 separate clusters but you can talk to both as one -- Itamar Syn-Hershko [http://code972.com](http://code972.com) | @synhershko [https://twitter.com/synhershko](https://twitter.com/synhershko) Freelance Developer & Consultant Author of RavenDB in Action [http://manning.com/synhershko/](http://manning.com/synhershko/) On Mon, Jun 2, 2014 at 1:49 PM, Martin Harris \< [martin.harris@cloudsoftcorp.com](mailto:martin.harris@cloudsoftcorp.com)\> wrote: > Hi Folks, > > I'm trying to setup a cross-cloud elastic-search cluster. As it's > cross-cloud, the usual discovery will not work, so I've started > elasticsearch on three nodes with multicast disabled > (discovery.zen.ping.multicast.enabled=false) and unicast enabled > (discovery.zen.ping.multicast.enabled=false). I then try to enable the > cluster by running the following against one (or all) of the nodes: > > curl -XPUT [http://localhost:9200/\_cluster/settings](http://localhost:9200/_cluster/settings) -d '{ "persistent" : { > "discovery.zen.ping.unicast.hosts":"37.58.110.34:9200,37.58.110.35:9200, > 37.58.110.36:9200"}}' > > The curl commands returns the following: > > {"acknowledged":true,"persistent":{},"transient":{}} > > But when I check the status of the cluster with the following: > > curl [http://localhost:9200/\_cluster/settings](http://localhost:9200/_cluster/settings) > > The curl command returns this: > > {"acknowledged":true,"persistent":{},"transient":{}}{"acknowledged":true,"persistent":{},"transient":{}} > > And the cluster has not been initialized > > The following is also added to the log: > > [WARN][action.admin.cluster.settings] [elasticsearch-1] ignoring > transient setting [discovery.zen.ping.unicast.hosts], not dynamically > updateable > > Any help would be appreciated > > Cheers > > Martin Harris > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/ee89982f-0bc3-456b-a9e4-2a06a0b6b0c6%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/ee89982f-0bc3-456b-a9e4-2a06a0b6b0c6%40googlegroups.com) > [https://groups.google.com/d/msgid/elasticsearch/ee89982f-0bc3-456b-a9e4-2a06a0b6b0c6%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/ee89982f-0bc3-456b-a9e4-2a06a0b6b0c6%40googlegroups.com?utm_medium=email&utm_source=footer) > . > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAHTr4Ztc%2BvBDrZt3ApVD%2B%3DCeH-ODh2J%2BtHVFDdyTK3vcsDSoVQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAHTr4Ztc%2BvBDrZt3ApVD%2B%3DCeH-ODh2J%2BtHVFDdyTK3vcsDSoVQ%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Martin\_Harris](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/martin_harris/32/1515_2.png) [@Martin\_Harris](https://discuss.elastic.co/u/Martin_Harris)\ **Post date:** [June 2, 2014, 11:08am UTC](https://discuss.elastic.co/t/configuring-cross-cloud-cluster-via-rest-api/17855/3 "2014-06-02T11:08:36Z")
Thanks Itamar, The tribe setup might work, but it may be easier if I can (at runtime) simply give elasticsearch a new IP address to add to the cluster - this will be accessible on port 9300 so the communication will not be over HTTP. Is there any way to do this? Cheers Martin On 2 June 2014 11:57, Itamar Syn-Hershko [itamar@code972.com](mailto:itamar@code972.com) wrote: > This will not work, discovery is done on port 9300 (by default) and cannot > be done over HTTP > > I think what you are looking for is tribe node - > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/modules-tribe.html) > > You'll then have 2 separate clusters but you can talk to both as one > > -- > > Itamar Syn-Hershko > [http://code972.com](http://code972.com) | @synhershko [https://twitter.com/synhershko](https://twitter.com/synhershko) > Freelance Developer & Consultant > Author of RavenDB in Action [http://manning.com/synhershko/](http://manning.com/synhershko/) > > On Mon, Jun 2, 2014 at 1:49 PM, Martin Harris \< > [martin.harris@cloudsoftcorp.com](mailto:martin.harris@cloudsoftcorp.com)\> wrote: > > > Hi Folks, > > > > I'm trying to setup a cross-cloud elastic-search cluster. As it's > > cross-cloud, the usual discovery will not work, so I've started > > elasticsearch on three nodes with multicast disabled > > (discovery.zen.ping.multicast.enabled=false) and unicast enabled > > (discovery.zen.ping.multicast.enabled=false). I then try to enable the > > cluster by running the following against one (or all) of the nodes: > > > > curl -XPUT [http://localhost:9200/\_cluster/settings](http://localhost:9200/_cluster/settings) -d '{ "persistent" : > > { "discovery.zen.ping.unicast.hosts":"37.58.110.34:9200,37.58.110.35:9200 > > ,37.58.110.36:9200"}}' > > > > The curl commands returns the following: > > > > {"acknowledged":true,"persistent":{},"transient":{}} > > > > But when I check the status of the cluster with the following: > > > > curl [http://localhost:9200/\_cluster/settings](http://localhost:9200/_cluster/settings) > > > > The curl command returns this: > > > > {"acknowledged":true,"persistent":{},"transient":{}}{"acknowledged":true,"persistent":{},"transient":{}} > > > > And the cluster has not been initialized > > > > The following is also added to the log: > > > > [WARN][action.admin.cluster.settings] [elasticsearch-1] ignoring > > transient setting [discovery.zen.ping.unicast.hosts], not dynamically > > updateable > > > > Any help would be appreciated > > > > Cheers > > > > Martin Harris > > > > -- > > You received this message because you are subscribed to the Google Groups > > "elasticsearch" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/ee89982f-0bc3-456b-a9e4-2a06a0b6b0c6%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/ee89982f-0bc3-456b-a9e4-2a06a0b6b0c6%40googlegroups.com) > > [https://groups.google.com/d/msgid/elasticsearch/ee89982f-0bc3-456b-a9e4-2a06a0b6b0c6%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/ee89982f-0bc3-456b-a9e4-2a06a0b6b0c6%40googlegroups.com?utm_medium=email&utm_source=footer) > > . > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > -- > You received this message because you are subscribed to a topic in the > Google Groups "elasticsearch" group. > To unsubscribe from this topic, visit > [https://groups.google.com/d/topic/elasticsearch/CIJ3h7Tpzt4/unsubscribe](https://groups.google.com/d/topic/elasticsearch/CIJ3h7Tpzt4/unsubscribe). > To unsubscribe from this group and all its topics, send an email to > [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/CAHTr4Ztc%2BvBDrZt3ApVD%2B%3DCeH-ODh2J%2BtHVFDdyTK3vcsDSoVQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAHTr4Ztc%2BvBDrZt3ApVD%2B%3DCeH-ODh2J%2BtHVFDdyTK3vcsDSoVQ%40mail.gmail.com) > [https://groups.google.com/d/msgid/elasticsearch/CAHTr4Ztc%2BvBDrZt3ApVD%2B%3DCeH-ODh2J%2BtHVFDdyTK3vcsDSoVQ%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAHTr4Ztc%2BvBDrZt3ApVD%2B%3DCeH-ODh2J%2BtHVFDdyTK3vcsDSoVQ%40mail.gmail.com?utm_medium=email&utm_source=footer) > . > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- Martin Harris Lead Software Engineer Cloudsoft Corporation Ltd [www.cloudsoftcorp.com](http://www.cloudsoftcorp.com) Mobile: +44 (0)7989 047-855 -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAEzXC-FU%2BePPU03sGjyCJmgOarL\_N%2BdQpSD4nJtiyj8V5y5opw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEzXC-FU%2BePPU03sGjyCJmgOarL_N%2BdQpSD4nJtiyj8V5y5opw%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [June 2, 2014, 11:11am UTC](https://discuss.elastic.co/t/configuring-cross-cloud-cluster-via-rest-api/17855/4 "2014-06-02T11:11:38Z")
You have to restart the whole cluster. Switching discovery while running a cluster is not possible. Jörg On Mon, Jun 2, 2014 at 12:49 PM, Martin Harris \< [martin.harris@cloudsoftcorp.com](mailto:martin.harris@cloudsoftcorp.com)\> wrote: > Hi Folks, > > I'm trying to setup a cross-cloud elastic-search cluster. As it's > cross-cloud, the usual discovery will not work, so I've started > elasticsearch on three nodes with multicast disabled > (discovery.zen.ping.multicast.enabled=false) and unicast enabled > (discovery.zen.ping.multicast.enabled=false). I then try to enable the > cluster by running the following against one (or all) of the nodes: > > curl -XPUT [http://localhost:9200/\_cluster/settings](http://localhost:9200/_cluster/settings) -d '{ "persistent" : { > "discovery.zen.ping.unicast.hosts":"37.58.110.34:9200,37.58.110.35:9200, > 37.58.110.36:9200"}}' > > The curl commands returns the following: > > {"acknowledged":true,"persistent":{},"transient":{}} > > But when I check the status of the cluster with the following: > > curl [http://localhost:9200/\_cluster/settings](http://localhost:9200/_cluster/settings) > > The curl command returns this: > > {"acknowledged":true,"persistent":{},"transient":{}}{"acknowledged":true,"persistent":{},"transient":{}} > > And the cluster has not been initialized > > The following is also added to the log: > > [WARN][action.admin.cluster.settings] [elasticsearch-1] ignoring > transient setting [discovery.zen.ping.unicast.hosts], not dynamically > updateable > > Any help would be appreciated > > Cheers > > Martin Harris > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/ee89982f-0bc3-456b-a9e4-2a06a0b6b0c6%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/ee89982f-0bc3-456b-a9e4-2a06a0b6b0c6%40googlegroups.com) > [https://groups.google.com/d/msgid/elasticsearch/ee89982f-0bc3-456b-a9e4-2a06a0b6b0c6%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/ee89982f-0bc3-456b-a9e4-2a06a0b6b0c6%40googlegroups.com?utm_medium=email&utm_source=footer) > . > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAKdsXoHpxKv\_PGYN1DuDjSRSFHAJn\_4ktHDiZ3v5x9Wyry1q7g%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoHpxKv_PGYN1DuDjSRSFHAJn_4ktHDiZ3v5x9Wyry1q7g%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Itamar\_Syn\_Hershko](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/itamar_syn_hershko/32/725_2.png) [@Itamar\_Syn\_Hershko](https://discuss.elastic.co/u/Itamar_Syn_Hershko)\ **Post date:** [June 2, 2014, 11:16am UTC](https://discuss.elastic.co/t/configuring-cross-cloud-cluster-via-rest-api/17855/5 "2014-06-02T11:16:48Z")
Just enable multicast using the plugin for your cloud provider... -- Itamar Syn-Hershko [http://code972.com](http://code972.com) | @synhershko [https://twitter.com/synhershko](https://twitter.com/synhershko) Freelance Developer & Consultant Author of RavenDB in Action [http://manning.com/synhershko/](http://manning.com/synhershko/) On Mon, Jun 2, 2014 at 2:08 PM, Martin Harris \< [martin.harris@cloudsoftcorp.com](mailto:martin.harris@cloudsoftcorp.com)\> wrote: > Thanks Itamar, > > The tribe setup might work, but it may be easier if I can (at runtime) > simply give elasticsearch a new IP address to add to the cluster - this > will be accessible on port 9300 so the communication will not be over HTTP. > Is there any way to do this? > > Cheers > > Martin > > On 2 June 2014 11:57, Itamar Syn-Hershko [itamar@code972.com](mailto:itamar@code972.com) wrote: > > > This will not work, discovery is done on port 9300 (by default) and > > cannot be done over HTTP > > > > I think what you are looking for is tribe node - > > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/modules-tribe.html) > > > > You'll then have 2 separate clusters but you can talk to both as one > > > > -- > > > > Itamar Syn-Hershko > > [http://code972.com](http://code972.com) | @synhershko [https://twitter.com/synhershko](https://twitter.com/synhershko) > > Freelance Developer & Consultant > > Author of RavenDB in Action [http://manning.com/synhershko/](http://manning.com/synhershko/) > > > > On Mon, Jun 2, 2014 at 1:49 PM, Martin Harris \< > > [martin.harris@cloudsoftcorp.com](mailto:martin.harris@cloudsoftcorp.com)\> wrote: > > > > > Hi Folks, > > > > > > I'm trying to setup a cross-cloud elastic-search cluster. As it's > > > cross-cloud, the usual discovery will not work, so I've started > > > elasticsearch on three nodes with multicast disabled > > > (discovery.zen.ping.multicast.enabled=false) and unicast enabled > > > (discovery.zen.ping.multicast.enabled=false). I then try to enable the > > > cluster by running the following against one (or all) of the nodes: > > > > > > curl -XPUT [http://localhost:9200/\_cluster/settings](http://localhost:9200/_cluster/settings) -d '{ "persistent" : > > > { "discovery.zen.ping.unicast.hosts":"37.58.110.34:9200, > > > 37.58.110.35:9200,37.58.110.36:9200"}}' > > > > > > The curl commands returns the following: > > > > > > {"acknowledged":true,"persistent":{},"transient":{}} > > > > > > But when I check the status of the cluster with the following: > > > > > > curl [http://localhost:9200/\_cluster/settings](http://localhost:9200/_cluster/settings) > > > > > > The curl command returns this: > > > > > > {"acknowledged":true,"persistent":{},"transient":{}}{"acknowledged":true,"persistent":{},"transient":{}} > > > > > > And the cluster has not been initialized > > > > > > The following is also added to the log: > > > > > > [WARN][action.admin.cluster.settings] [elasticsearch-1] ignoring > > > transient setting [discovery.zen.ping.unicast.hosts], not dynamically > > > updateable > > > > > > Any help would be appreciated > > > > > > Cheers > > > > > > Martin Harris > > > > > > -- > > > You received this message because you are subscribed to the Google > > > Groups "elasticsearch" group. > > > To unsubscribe from this group and stop receiving emails from it, send > > > an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > > > > > To view this discussion on the web visit > > > [https://groups.google.com/d/msgid/elasticsearch/ee89982f-0bc3-456b-a9e4-2a06a0b6b0c6%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/ee89982f-0bc3-456b-a9e4-2a06a0b6b0c6%40googlegroups.com) > > > [https://groups.google.com/d/msgid/elasticsearch/ee89982f-0bc3-456b-a9e4-2a06a0b6b0c6%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/ee89982f-0bc3-456b-a9e4-2a06a0b6b0c6%40googlegroups.com?utm_medium=email&utm_source=footer) > > > . > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > -- > > You received this message because you are subscribed to a topic in the > > Google Groups "elasticsearch" group. > > To unsubscribe from this topic, visit > > [https://groups.google.com/d/topic/elasticsearch/CIJ3h7Tpzt4/unsubscribe](https://groups.google.com/d/topic/elasticsearch/CIJ3h7Tpzt4/unsubscribe). > > To unsubscribe from this group and all its topics, send an email to > > [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/CAHTr4Ztc%2BvBDrZt3ApVD%2B%3DCeH-ODh2J%2BtHVFDdyTK3vcsDSoVQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAHTr4Ztc%2BvBDrZt3ApVD%2B%3DCeH-ODh2J%2BtHVFDdyTK3vcsDSoVQ%40mail.gmail.com) > > [https://groups.google.com/d/msgid/elasticsearch/CAHTr4Ztc%2BvBDrZt3ApVD%2B%3DCeH-ODh2J%2BtHVFDdyTK3vcsDSoVQ%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAHTr4Ztc%2BvBDrZt3ApVD%2B%3DCeH-ODh2J%2BtHVFDdyTK3vcsDSoVQ%40mail.gmail.com?utm_medium=email&utm_source=footer) > > . > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > -- > Martin Harris > Lead Software Engineer > Cloudsoft Corporation Ltd > [www.cloudsoftcorp.com](http://www.cloudsoftcorp.com) > Mobile: +44 (0)7989 047-855 > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/CAEzXC-FU%2BePPU03sGjyCJmgOarL\_N%2BdQpSD4nJtiyj8V5y5opw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEzXC-FU%2BePPU03sGjyCJmgOarL_N%2BdQpSD4nJtiyj8V5y5opw%40mail.gmail.com) > [https://groups.google.com/d/msgid/elasticsearch/CAEzXC-FU%2BePPU03sGjyCJmgOarL\_N%2BdQpSD4nJtiyj8V5y5opw%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAEzXC-FU%2BePPU03sGjyCJmgOarL_N%2BdQpSD4nJtiyj8V5y5opw%40mail.gmail.com?utm_medium=email&utm_source=footer) > . > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAHTr4Zsx%2B%2BbHEjHMRML91C7u83hcJfzczpkvZCs%2BLe5BU7bGFw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAHTr4Zsx%2B%2BbHEjHMRML91C7u83hcJfzczpkvZCs%2BLe5BU7bGFw%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 1:25am UTC](https://discuss.elastic.co/t/configuring-cross-cloud-cluster-via-rest-api/17855/6 "2017-07-06T01:25:15Z")