Getting "The serverless deployment bucket does not exist", when the bucket does exist.
See original GitHub issueRun sls deploy:
Serverless Error ---------------------------------------
The serverless deployment bucket "notes-app-2-api-dev-serverlessdeploymentbucket-n5stychfa7ue" does not exist. Create it manually if you want to reuse the CloudFormation stack "notes-app-2-api-dev", or delete the stack if it is no longer required.
Go to create new bucket:

Run sls remove:
Serverless Error ---------------------------------------
The specified bucket does not exist
Issue Analytics
- State:
- Created 4 years ago
- Reactions:8
- Comments:6
Top Results From Across the Web
Serverless: The specified bucket does not exist - Stack Overflow
So to recover the old bucket, go to the CloudFormation console for the stack in question, click the Resources tab, your bucket should...
Read more >The specified bucket does not exist error - Serverless Forums
I think I figured this out. I went in the local folders and just did sls info -v to see the detailed information...
Read more >The serverless deployment bucket does not exist - Seed.run
Delete the CloudFormation stack that has been previously deployed. You would need to manually do this by going to the CloudFormation section of...
Read more >Serverless deployment bucket
The serverless deployment bucket does not exist create it manually ... Be sure your system meets the prerequisites specified in Installing the Toolkit...
Read more >serverless-deployment-bucket - npm
Start using serverless-deployment-bucket in your project by running `npm i serverless-deployment-bucket`. There are 4 other projects in the ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Found this and wanted to add a comment with my experience. The most common cause I’ve found is when you try to delete a stack and the delete fails for some reason. If it gets to the S3 bucket resource before it gets to the failure then the bucket will get deleted producing this error if you try to redeploy because the stack already exists. You will need to manually delete the stack because to my knowledge there’s no way for serverless to recover once the bucket is gone.
Deleting the stack form the cloud formation resolved the issue for me thanks @devblueray