# Error during creating cluster **URL:** \ **Category:** Elastic Cloud Enterprise (ECE)\ **Created:** [June 9, 2017, 5:40am UTC](https://discuss.elastic.co/t/error-during-creating-cluster/88791 "2017-06-09T05:40:19Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![weibin.wu](https://avatars.discourse-cdn.com/v4/letter/w/4491bb/32.png) [@weibin.wu](https://discuss.elastic.co/u/weibin.wu)\ **Post date:** [June 9, 2017, 5:40am UTC](https://discuss.elastic.co/t/error-during-creating-cluster/88791/1 "2017-06-09T05:40:19Z")
Hi ECE: During creating cluster, I got this error Unexpected error during step: [ensure-s3-resources]: [java.lang.Exception: Unable to assign S3 resources: [No available resources.] I did not setup any snapshot when create cluster. Why the cluster is trying to access S3? ---
**Author:** ![uricohen](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/uricohen/32/9776_2.png) [@uricohen](https://discuss.elastic.co/u/uricohen)\ **Post date:** [June 11, 2017, 1:08pm UTC](https://discuss.elastic.co/t/error-during-creating-cluster/88791/2 "2017-06-11T13:08:48Z")
Hi @weibin.wu Which version of ECE are you using? Did you create a global snapshot repository or is this a fresh ECE installation? Thanks, Uri ---
**Author:** ![weibin.wu](https://avatars.discourse-cdn.com/v4/letter/w/4491bb/32.png) [@weibin.wu](https://discuss.elastic.co/u/weibin.wu)\ **Post date:** [June 12, 2017, 2:02am UTC](https://discuss.elastic.co/t/error-during-creating-cluster/88791/3 "2017-06-12T02:02:59Z")
Hi ECE version: 1.0 release It is a new setup ECE I create the cluster without inputing the cluster name. Full error: ```auto { "instance_count": 0, "instance_capacity": 0, "master_node_count": 0, "master_node_capacity": 0, "failover": { "skip_snapshot": false }, "plan_id": "9a345144-d5e2-4062-a6f1-ac1a8f5e8037", "source": { "facilitator": "adminconsole", "action": "elasticsearch.stop-cluster", "date": "2017-06-09T07:16:11.559Z" }, "strategy": {} } Detailed information for all steps 2017-06-09T07:16:11.604Z Starting step: [resolve-node-type]: clusterType=ElasticsearchClusterType 2017-06-09T07:16:11.607Z Completed step: [resolve-node-type] with result: None This step took 1ms. 2017-06-09T07:16:11.608Z Starting step: [plan-validator]: cluster=ElasticsearchCluster(b0d429a3ff6c4a57bd22bbeec9ab61c3), stat=12884904386,12884904386,1496992571574,1496992571574,0,0,0,0,285,0,12884904386 } 2017-06-09T07:16:11.619Z Completed step: [plan-validator] with result: ElasticsearchPlan(Some(9a345144-d5e2-4062-a6f1-ac1a8f5e8037),0,0,1,0,0,Some(false),1024,false,1024 seconds,5 seconds,ElasticsearchPlanSection(None,List(),true,List(),List(),{},{},false,None),DefaultStrategy(),Failover(false,Map(),Map(),false,List(),true,false,3,None,false,None,false,false),TransientPlanSection(None),None,None,12884904386,12884904386,1496992571574,1496992571574,0,0,0,0,285,0,12884904386 ) This step took 10ms. 2017-06-09T07:16:11.619Z Starting step: [validate-elasticsearch-plugin-versions]: [] 2017-06-09T07:16:11.619Z Completed step: [validate-elasticsearch-plugin-versions] with result: () This step took 0ms. 2017-06-09T07:16:11.620Z Starting step: [ensure-s3-resources]: [] 2017-06-09T07:16:11.626Z Unexpected error during step: [ensure-s3-resources]: [java.lang.Exception: Unable to assign S3 resources: [No available resources.] 2017-06-09T07:16:11.627Z Performing [0] rollback actions: [List()]. 2017-06-09T07:16:11.629Z Plan change failed: [An unexpected exception was raised] ``` ---
**Author:** ![Alex\_Piggott](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alex_piggott/32/11053_2.png) [@Alex\_Piggott](https://discuss.elastic.co/u/Alex_Piggott)\ **Post date:** [June 12, 2017, 12:42pm UTC](https://discuss.elastic.co/t/error-during-creating-cluster/88791/4 "2017-06-12T12:42:08Z")
Hi @weibin.wu This can happen if snapshots are enabled but a repository is not configured It's an odd state to be in though. Under the advanced view (at the bottom of the Manage page for the cluster in question) in the there are 2 JSON text boxes, the first contains the plan, the second contains cluster metadata. Can you paste the contents of the second? It should look something like: ```auto { "name": "YOUR_NAME", "found-users": { /* various internal users, ignore */ }, "snapshot": { "enabled": true|false, "supported": true|false, /* other things */ }, /* other things */ } ``` Also there is one other strange thing in your logs ... you were trying to create a cluster from scratch, but the plan says `"action": "elasticsearch.stop-cluster"` ... can you clarify how you were creating the cluster - were you just going to the cluster page, clicking create, and then filling in the fields? Alex ---
**Author:** ![weibin.wu](https://avatars.discourse-cdn.com/v4/letter/w/4491bb/32.png) [@weibin.wu](https://discuss.elastic.co/u/weibin.wu)\ **Post date:** [June 13, 2017, 3:04am UTC](https://discuss.elastic.co/t/error-during-creating-cluster/88791/5 "2017-06-13T03:04:15Z")
Hi Alex: I confirm I dont any snapshot at "advanced configuration". I think I found something. I create the cluster with 32GB / 1 TB size. However, each of the AZ only has 1TB storage maximum. So I am creating a cluster out of the capacity. After creation, I dont see the cluster appear in Platform tab. So I deleted it. And during deleting, this error comes out. Now the cluster becomes undeletable. Is there any way to resolve this problem instead of re-install the whole ECE? ---
**Author:** ![Alex\_Piggott](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alex_piggott/32/11053_2.png) [@Alex\_Piggott](https://discuss.elastic.co/u/Alex_Piggott)\ **Post date:** [June 13, 2017, 2:13pm UTC](https://discuss.elastic.co/t/error-during-creating-cluster/88791/6 "2017-06-13T14:13:35Z")
Hi @weibin.wu Can you paste the following into the "Data" block in the aforementioned "advanced cluster configuration" page. ```auto "snapshot": { "enabled": false, "suspended": {} }, ``` "Save" that, then the "Shutdown" button should work (and then the "Delete" button). What's happening is that for some reason (we can investigate that once this issue is fixed) the snapshot block is not getting written to the cluster metadata, and it defaults to true. ---
**Author:** ![weibin.wu](https://avatars.discourse-cdn.com/v4/letter/w/4491bb/32.png) [@weibin.wu](https://discuss.elastic.co/u/weibin.wu)\ **Post date:** [June 14, 2017, 9:52am UTC](https://discuss.elastic.co/t/error-during-creating-cluster/88791/7 "2017-06-14T09:52:04Z")
Thanks Alex: It works. Now i can stop and delete that cluster. ---
**Author:** ![Alex\_Piggott](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alex_piggott/32/11053_2.png) [@Alex\_Piggott](https://discuss.elastic.co/u/Alex_Piggott)\ **Post date:** [June 14, 2017, 12:50pm UTC](https://discuss.elastic.co/t/error-during-creating-cluster/88791/8 "2017-06-14T12:50:58Z")
Excellent, I'm glad. Now ... if you create another cluster (whether it succeeds or fails), you _should_ see that it always creates that `snapshot: { enabled: false }` object in the cluster metadata? (ie what you ran into was a one-off?) I have the UI team looking into why that might have happened, but it would be useful to confirm that it was intermittent and not something specific to your set up Thanks for all your help ironing out these teething troubles! Alex ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [June 28, 2017, 12:51pm UTC](https://discuss.elastic.co/t/error-during-creating-cluster/88791/9 "2017-06-28T12:51:38Z")
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.