The specified bucket does not exist
See original GitHub issuePlease help me. I try to deploy serverless but this error appear when try to excecute
serverless --stage=production deploy
into npm run deploy:api step
here is the cli output
Serverless Error ---------------------------------------
The specified bucket does not exist
Get Support --------------------------------------------
Docs: docs.serverless.com
Bugs: github.com/serverless/serverless/issues
Your Environment Information -----------------------------
OS: darwin
Node Version: 6.2.0
Serverless Version: 1.4.0
Issue Analytics
- State:
- Created 7 years ago
- Reactions:11
- Comments:15 (3 by maintainers)
Top Results From Across the Web
AWS s3 api error: specified bucket does not exist
The error is stating that bucket does not yet exist. By the looks of your code, the bucket name is not correct, which...
Read more >Bucket does not exist · Issue #92 - GitHub
I have successfully built the template and every thing is in buckets. While creating cloud formation its failing to complete and following ...
Read more >Error putting object in S3 bucket example11225588 ... - Edureka
But I am getting this error. Error putting object in S3 bucket (example11225588): NoSuchBucket: The specified bucket does not exist status code: ...
Read more >NoSuchBucket – The specified bucket does not exist
I had it working on a test Google account and now I've moved it over to our regular account. Set it up with...
Read more >ERROR: "Bucket does not exist or User does not have access ...
Please check S3 bucket is in the same region ...
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
Try deleting the stack from CloudFormation and redeploying - that got me over this hump.
This is just a general comment but when you deliver back error messages to the user, please try to include the proper name of what doesn’t exist. That is, if a bucket doesn’t exist you should say WHAT THE BUCKET NAME IS.
Also, passing
--verbose
does nothing. A command line tool is supposed to be a user interface, not a hurdle.