Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Stack with id <STACK_NAME> does not exist

See original GitHub issue

This is a Bug Report

Description

Using AWS, recently I’ve started getting the error: Stack with id <STACK_NAME> does not exist. I am not sure why exactly it’s happening, but it might be triggered by deleting the stack in the AWS console. I think I have completely purged any reference to the stack from AWS.

The only way I found to recover from that is manually creating a stack with Cloudformation using the same name and redeploying on top of that using Serverless. How can we fix that more elegantly?

Additional Data

Serverless Framework Version: 1.15.0 I am using the serverless-aws-alias plugin, version 1.2.1

Issue Analytics

State:
Created 6 years ago
Comments:15 (5 by maintainers)

Top GitHub Comments

3reactions

joekendalcommented, Oct 24, 2020

in my case, i just needed to specify the region as well

$ serverless remove --stage $STAGE --region $REGION

2reactions

serverlessgurucommented, May 5, 2020

I’m seeing this as well, but I’m hitting too many buckets error on AWS. The terminal doesn’t send this information back.

Screen Shot 2020-05-05 at 3 40 39 PM

Top Results From Across the Web

Stack with id does not exist - Seed.run

A couple of common causes for this error: Serverless Framework was not able to find the previously deployed CloudFormation stack for your Serverless...

Stack with id does not exist? Stack definitely exists

The stack ID in question is an existing CloudFormation stack that definitely exists in the target account. I've googled high & low for...

"Stack with id X does not exist" on all sls commands after ...

The problem is that the ${cf:...} syntax requires the output of an existing CloudFormation stack and when you have not yet deployed the ......

serverless-deploy failed - ValidationError: Stack with id does ...

The error show that stack does not exist, that means it was not created. Unfortunately, I see here, it is not shown in...

Finding stack IDs - AMS Advanced User Guide

To find a Stack ID, you can use either the Amazon EC2 console, AMS console, or the AMS SKMS API/CLI. AMS Console: In...