# Tribe node data compliance across regions

**URL:** <https://discuss.elastic.co/t/tribe-node-data-compliance-across-regions/18138>\
**Category:** Elasticsearch\
**Created:** [June 16, 2014, 7:24pm UTC](https://discuss.elastic.co/t/tribe-node-data-compliance-across-regions/18138 "2014-06-16T19:24:28Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kyle\_House](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kyle_house/32/1486_2.png) [@Kyle\_House](https://discuss.elastic.co/u/Kyle_House)\
**Post date:** [June 16, 2014, 7:24pm UTC](https://discuss.elastic.co/t/tribe-node-data-compliance-across-regions/18138/1 "2014-06-16T19:24:28Z")

</div>

We are staging a rollout of multiple ES clusters across multiple regions,  
and we have a requirement to keep data contained inside the predefined  
regions. I wanted to check on how a tribe node would impact this  
requirement. My understanding is this node would be attached to multiple  
clusters for quick searching across regions, but would not pull any data  
locally thus violating this data requirement. Any information would be  
helpful, thanks!

--Kyle

--  
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/f81460ac-d2db-4ae4-a014-29ed86c0a5de%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/f81460ac-d2db-4ae4-a014-29ed86c0a5de%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<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:** [June 16, 2014, 10:17pm UTC](https://discuss.elastic.co/t/tribe-node-data-compliance-across-regions/18138/2 "2014-06-16T22:17:45Z")

</div>

It's best explained in the docs

> **[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.

Regards,  
Mark Walkom

Infrastructure Engineer  
Campaign Monitor  
email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com)  
web: [www.campaignmonitor.com](http://www.campaignmonitor.com)

On 17 June 2014 05:24, Kyle House [kylewhouse@gmail.com](mailto:kylewhouse@gmail.com) wrote:

> We are staging a rollout of multiple ES clusters across multiple regions,  
> and we have a requirement to keep data contained inside the predefined  
> regions. I wanted to check on how a tribe node would impact this  
> requirement. My understanding is this node would be attached to multiple  
> clusters for quick searching across regions, but would not pull any data  
> locally thus violating this data requirement. Any information would be  
> helpful, thanks!
> 
> --Kyle
> 
> --  
> 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/f81460ac-d2db-4ae4-a014-29ed86c0a5de%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/f81460ac-d2db-4ae4-a014-29ed86c0a5de%40googlegroups.com)  
> [https://groups.google.com/d/msgid/elasticsearch/f81460ac-d2db-4ae4-a014-29ed86c0a5de%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/f81460ac-d2db-4ae4-a014-29ed86c0a5de%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/CAEM624a8NDBzjrUjeMMoSH7kfuGQ0u8V-z0Hh4vbFVKqmf\_sCw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624a8NDBzjrUjeMMoSH7kfuGQ0u8V-z0Hh4vbFVKqmf_sCw%40mail.gmail.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<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:** [July 6, 2017, 1:21am UTC](https://discuss.elastic.co/t/tribe-node-data-compliance-across-regions/18138/3 "2017-07-06T01:21:59Z")

</div>


