# Setting up an ES cluster on EC2 with non EC2 fallback? **URL:** \ **Category:** Elasticsearch\ **Created:** [September 25, 2012, 11:22am UTC](https://discuss.elastic.co/t/setting-up-an-es-cluster-on-ec2-with-non-ec2-fallback/9132 "2012-09-25T11:22:46Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Derry\_O\_Sullivan](https://avatars.discourse-cdn.com/v4/letter/d/7bcc69/32.png) [@Derry\_O\_Sullivan](https://discuss.elastic.co/u/Derry_O_Sullivan)\ **Post date:** [September 25, 2012, 11:22am UTC](https://discuss.elastic.co/t/setting-up-an-es-cluster-on-ec2-with-non-ec2-fallback/9132/1 "2012-09-25T11:22:46Z")
Hi there, We're looking into setting up a production ES cluster on EC2 (thanks to the various guides/plugins, it's pretty easy to setup). EC2 has had it's fair share of publicized outages so for HA reasons, we would like to maintain our indices outside of ES also. We would be maintaining these indices across a number of regions if time/data sync performance allows The options I see are: a. Use gateway/other backup techniques to write to an S3/external data store and piggyback from that. (almost like a separate cluster) b. Maintain a separate non EC2 slave node (which would become the master on catastrophic EC2 fail?) Does anyone have any experience of doing something like this? Would really appreciate any tips/advice on this and also on experience with cluster setups on EC2 across multiple zones/regions. Thanks in advance, Derry -- ---
**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, 3:11am UTC](https://discuss.elastic.co/t/setting-up-an-es-cluster-on-ec2-with-non-ec2-fallback/9132/2 "2017-07-06T03:11:31Z")
Closed on July 6, 2017, 3:11am UTC