My first serverless deploy failed with Stack XXXXX does not exist

Serverless Framework
, , ,
1

Hi all,

My Serverless.yml

service: serverless-web-forms
frameworkVersion: "2"
# Our serverless infra provider section
provider:
  name: aws
  stage: dev
  runtime: nodejs12.x
  region: us-east-1
# Serverless functions
functions:
  formSubmission:
    handler: api/form.submit
    memorySize: 128
    description: Save the form entry details to DynamoDB and send the verification email.
    events:
      - http:
          path: formSubmit
          method: post
  formVerification:
    handler: api/form.verify
    memorySize: 128
    description: Verify the GET token header from the email verification link. Create the new Ticket. Delete the form entry from DynamoDB.
    events:
      - http:
          path: formVerfiy
          method: get
plugins:
  - serverless-offline

I’m fairly new to serverless and I’m struggling with even deploying a simple API Gateway backend. I’ve run

serverless deploy -v

but I’m getting the following error:

            Set "provider.apiGateway.shouldStartNameWithService" to "true" to adapt to the new behavior now.
            More Info: https://www.serverless.com/framework/docs/deprecations/#AWS_API_GATEWAY_NAME_STARTING_WITH_SERVICE
Serverless: Packaging service...
Serverless: Excluding development dependencies...
Serverless: Creating Stack...
Serverless: Checking Stack create progress...
CloudFormation - DELETE_IN_PROGRESS - AWS::CloudFormation::Stack - serverless-web-forms-dev
CloudFormation - DELETE_COMPLETE - AWS::S3::Bucket - ServerlessDeploymentBucket
CloudFormation - DELETE_COMPLETE - AWS::CloudFormation::Stack - serverless-web-forms-dev
Serverless: Stack create finished...

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

  Stack 'serverless-web-forms-dev' does not exist

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

  Your Environment Information ---------------------------
     Operating System:          linux
     Node Version:              12.18.1
     Framework Version:         2.11.1 (standalone)
     Plugin Version:            4.1.2
     SDK Version:               2.3.2
     Components Version:        3.3.0

We’ve generated the accounts permissions using yeoman / serverless-policy. I thought that running sls with --verbose would provide some meaningful output. But all I’m seeing is that a DELETE occured with no resources / logs to show for it in the AWS account.

Any ideas on this one?

Tia,

Kyle

2

So upon further examination by a colleague with greater permissions, CloudTrail showed that the S3 deployment bucket failed to be created. Why wasn’t this shown in the verbose logs when deploying the initial stack?

BR,

Kyle

3

Thanks for the edit Kyle helped me figure it out.

CloudFormation stacks can hang IN_REVIEW specifically on the stack used to create the AWS S3 bucket.

TL:DR on quick fix: on AWS console delete the specific stack and try again

sls deploy with --verbose to see the exact stack name

For more info: CloudFormation stack stuck in REVIEW_IN_PROGRESS state

Hope this helps anyone facing this too.