Cannot deploy to AWS about serverless-graphql-blog HOT 9 CLOSED

I am seeing the same issue. Tried several times.

from serverless-graphql-blog.

I was able to deploy successfully once and then I deleted the folder and reinstalled and now I am having the same issue

from serverless-graphql-blog.

I solved this problem by doing the following...

sls region remove -s dev -r us-west-2
sls region create

from serverless-graphql-blog.

while doing sls region create I get the following error:
An error occurred while provisioning your cloudformation: The following resource(s) failed to create: [AuthorsDynamo, CommentsDynamo, IamRoleLambda, PostsDynamo]. . Delete requested by user.

from serverless-graphql-blog.

i was able to fix the 'no lambda IAM role found' problem by deleting everything and deploying to a different region

from serverless-graphql-blog.

Yes, just had this problem myself, fixed with sls region remove and sls region create, and needed to pick a different region (was on us-east-1, changed to ap-northeast-1).

from serverless-graphql-blog.

I'm also getting this error. I was following these directions:

http://docs.serverless.com/docs/installing-serverless

And used the us-east-1 region.

Switching to us-west-2 fixed the issue for me. Interestingly, after switching from us-west-2 back to us-east-1, serverless dash deploy worked fine.

from serverless-graphql-blog.

Ok, I was having similar problems with errors like:

The following resource(s) failed to create: [IamRoleLambda]. . Delete requested by user.

I took a look at the cloudformation logs, under the "deleted" filter. I saw that the process was failing due to the resource existing, but it was under another stack. I was experimenting earlier and manually running cloudformation templates via the console.

So what I did in the command line, you must have the aws-cli installed, was aws cloudformation describe-stacks and to my surprise I found a couple of outstanding stacks with created resources associated with it. I deleted those stacks via the command line, aws cloudformation delete-stack --stack-name xyz

i ran sls project remove, I went into my console and made sure everything was deleted, i.e. dynamodb tables, topics, as you know the remove does not delete dynamodb tables, etc; make sure you are starting from a clean slate.

Then I ran sls project init, picked the defaults as usual, YMMV, and it started working again.

Hope this helps people, this was driving me nuts for a day or two.

from serverless-graphql-blog.

Just go to your account and delete the stack created by cloudformation and try again.

from serverless-graphql-blog.