# Running ES on different Data Centers

**URL:** <https://discuss.elastic.co/t/running-es-on-different-data-centers/21233>\
**Category:** Elasticsearch\
**Created:** [December 12, 2014, 9:11am UTC](https://discuss.elastic.co/t/running-es-on-different-data-centers/21233 "2014-12-12T09:11:43Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mantas\_Urnieza](https://avatars.discourse-cdn.com/v4/letter/m/c5a1d2/32.png) [@Mantas\_Urnieza](https://discuss.elastic.co/u/Mantas_Urnieza)\
**Post date:** [December 12, 2014, 9:11am UTC](https://discuss.elastic.co/t/running-es-on-different-data-centers/21233/1 "2014-12-12T09:11:43Z")

</div>

Hello,

we use Amazon AWS as a hosting providers. Currently we are in single  
availability zone and have plans to scale up to more of them.

What would be the best practices to do that?  
What impact on performance shards spread on different DCs have?  
If we duplicate indexes on all DCs what would be the best way to keep them  
all in sync and up to date?

--  
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/aef004fc-2129-4971-97c7-8cbcd54beff2%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/aef004fc-2129-4971-97c7-8cbcd54beff2%40googlegroups.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, 12:43am UTC](https://discuss.elastic.co/t/running-es-on-different-data-centers/21233/2 "2017-07-06T00:43:57Z")

</div>


