# Running Elasticsearch on AWS - Windows Server \[Walk-trough\] **URL:** \ **Category:** Elasticsearch\ **Created:** [August 26, 2018, 10:10am UTC](https://discuss.elastic.co/t/running-elasticsearch-on-aws-windows-server-walk-trough/146063 "2018-08-26T10:10:56Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![GouravDas](https://avatars.discourse-cdn.com/v4/letter/g/51bf81/32.png) [@GouravDas](https://discuss.elastic.co/u/GouravDas)\ **Post date:** [August 26, 2018, 10:10am UTC](https://discuss.elastic.co/t/running-elasticsearch-on-aws-windows-server-walk-trough/146063/1 "2018-08-26T10:10:56Z")
Unable to find any relevant information for Running Elasticsearch on AWS - Windows Server thus as a gratitude for whether ever I have learnt from this forum, I have jotted down all the relevant steps to run your cluster in AWS for Windows Server. 1. Run min 3 EC2 instances in AWS to form a highly available cluster in same Availability Zone for simplicity [As a best practice it can be run in multiple AZs]. Put all of the instances in the same security group and make sure port no. 9200 & 9300 are allowed in the inbound rule, in the source mention only the subnet of the following Availability Zone, it shouldn’t be opened to the world as a security best practices. 2. Download ElasticSearch for windows from ([http://www.elastic.co/downloads/elasticsearch](http://www.elastic.co/downloads/elasticsearch)) & create similar folder structure in all the instances and keep the zipped file there & extract it. 3. Next we need to configure the elasticsearch.yml which is located inside config folder [Notepad++ recommended]. Kindly do the similar change in all the instances, uncomment the following parameters & write them up accordingly, make sure you mention private IP addr assigned to the instance or else it won’t work. _cluster.name: dev-cluster_ _node.name: ${HOSTNAME}_ _network.host: ["0.0.0.0"]_ _discovery.zen.ping.unicast.hosts: ["private-ip of node-1", " private-ip of node-2" , “private-ip of node-3”]_ **For e.x, discovery.zen.ping.unicast.hosts: ["172.31.56.159", "172.31.54.17" , “172.31.56.119”]** _discovery.zen.minimum\_master\_nodes: 2_ 4. Disable Windows Defender Firewall from control panel in all the EC2 instances. 5. Run the cluster one by one by from command prompt by using the following cmd “ **ElasticSearchPath** \bin\elasticsearch.bat” 6. To check if all the nodes are added to the cluster or not , run the following in any web browser **localhost:9200/\_cluster/health?pretty** 7. **Common issues,** if you get following error **[o.e.d.z.ZenDiscovery] [node-name] failed to send join request to master** , kindly stop cluster service in all the instances , delete the data folder from all the instances and re-start the service one-by-one. 8. Thanks for reading. ---
**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:** [August 27, 2018, 4:18am UTC](https://discuss.elastic.co/t/running-elasticsearch-on-aws-windows-server-walk-trough/146063/2 "2018-08-27T04:18:46Z")
We wouldn't recommend disabling the firewall entirely. > [@GouravDas](#): > > if you get following error **[o.e.d.z.ZenDiscovery] [node-name] failed to send join request to master** , kindly stop cluster service in all the instances , delete the data folder from all the instances and re-start the service one-by-one. You shouldn't need to do this. Perhaps if you share some logs we can find a better way. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [September 24, 2018, 4:21am UTC](https://discuss.elastic.co/t/running-elasticsearch-on-aws-windows-server-walk-trough/146063/3 "2018-09-24T04:21:01Z")
Closed on September 24, 2018, 4:21am UTC This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.