# Elasticsearch 7.0 bootstrapping in AWS **URL:** \ **Category:** Elasticsearch\ **Created:** [April 11, 2019, 7:52pm UTC](https://discuss.elastic.co/t/elasticsearch-7-0-bootstrapping-in-aws/176491 "2019-04-11T19:52:05Z")\ **Posts on this page:** 1\ **Showing post:** 15
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [May 9, 2019, 9:18pm UTC](https://discuss.elastic.co/t/elasticsearch-7-0-bootstrapping-in-aws/176491/15 "2019-05-09T21:18:29Z")
> [@bkruger](#): > > Wouldn't requiring a hard minimum number bootstrap masters fix this? I want 3 masters, 3 masters must be online to bootstrap, no exceptions. Putting a lower bound on the number of nodes needed for bootstrapping still doesn't prevent you from forming multiple clusters, because as you rightly point out you might end up with more nodes than you asked for. We're not really interested in probabilities here, because there's a lot of Elasticsearch instances out there and eventually one of them is going to hit every corner case there is. > [@bkruger](#): > > Especially since this is initial, the assumption is that there's nothing to lose data wise, game over, start again There could well be data to lose. You might not be able to tell you've formed more than one cluster until you've started indexing into them all, at which point you can't in general merge the data back together again. --- _[View the full topic](https://discuss.elastic.co/t/elasticsearch-7-0-bootstrapping-in-aws/176491)._