# ElasticSearch Zone Awareness in AWS

**URL:** <https://discuss.elastic.co/t/elasticsearch-zone-awareness-in-aws/75413>\
**Category:** Elasticsearch\
**Created:** [February 16, 2017, 11:35pm UTC](https://discuss.elastic.co/t/elasticsearch-zone-awareness-in-aws/75413 "2017-02-16T23:35:01Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mvz00](https://avatars.discourse-cdn.com/v4/letter/m/2acd7d/32.png) [@mvz00](https://discuss.elastic.co/u/mvz00)\
**Post date:** [February 16, 2017, 11:35pm UTC](https://discuss.elastic.co/t/elasticsearch-zone-awareness-in-aws/75413/1 "2017-02-16T23:35:01Z")

</div>

Hi,

I have set a Four Node ElasticSearch cluster up in AWS with the following config in order to ensure that replica shards are stored on the alternate AWS Availability zone in case of Network Partitioning or DR.

cloud.aws.region: "xx-southeast-1"  
node.zone: "xx-southeast-1a"  
cluster.routing.allocation.awareness.attributes: "zone"

Two things I need to validate:

1. Does the above config look correct, and would this result in Replica Shards existing on the Nodes in xx-southeast-1b AZ?

2. What command can I run to validate the the replica shards are indeed replicated to the secondard Availability Zone in AWS?

Thanks in advance.

Mike.

---

<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:** [March 16, 2017, 11:35pm UTC](https://discuss.elastic.co/t/elasticsearch-zone-awareness-in-aws/75413/2 "2017-03-16T23:35:19Z")

</div>

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