Error occurred when run serverless deploy

[hengbenkeji]

I am using serverless.1.0.0-beta.1.1 and following the document.

The error report is: cannot create the S3 bucket.

Yet, there is really no setup for the S3 in serverless.yml

It is a surprise that I got stuck from the very beginning.

This error shows every time I try

[pmuens]

Hey @sdruipeng so you're deploying a simple Serverless service and are not using a S3 event?

Have you setup your AWS user so that he can create the necessary resources on your behalf as described here: https://github.com/serverless/serverless/blob/master/docs/guide/provider-account-setup.md?

[flomotlik]

@sdruipeng the bucket it needs to create is for the deployment itself. We're deploying Serverless application artefacts through an S3 bucket, so your user accounts needs to rights to create it.

As this is more a support issue and less a Serverless core problem you can also get more help in our Forum at http://forum.serverless.com

[hengbenkeji]

@pmuens
@flomotlik

Thank you for you information.
I checked my IAM user again, making sure that it all conforms to the instructions described at provider-account-setup.md. _But I got the error as follows again._

By the way, I have developed a website based on S3 and react/redux, I am planning to use the serverless to do the Login for my website. Yet, I got stuck from the very beginning at serverless.
I am using a Chinese version Win 10 and node.js 5.6.0. I have no problem when I use react or mongodb with this setup. I was wondering the coding could be a problem for serverless.

$ serverless deploy
Serverless: Zipping service...

Serverless Error ---------------------------------------

 The specified bucket does not exist

Get Support --------------------------------------------
Docs: v1.docs.serverless.com
Bugs: github.com/serverless/serverless/issues

[flomotlik]

Could you run serverless remove and then serverless deploy again. Looks like something in the Cloudformation template wasn't properly deployed. Did you potentially change the name of the bucket or change anything in S3 directly?