Serverless部署报错：指定存储桶不存在，如何查看目标存储桶？

I totally get how frustrating this vague error is—when you know the buckets exist but Serverless keeps claiming they don’t, not seeing the actual bucket name it’s targeting makes troubleshooting way harder. Here are a few reliable ways to uncover that critical detail:

• Enable verbose/debug logging
  This is the quickest fix to reveal the bucket name Serverless is attempting to access. Run your deployment command with the --verbose flag:

  serverless deploy --verbose
  

  Or, for even more granular logs, set the SLS_DEBUG environment variable to * before executing the command:

  SLS_DEBUG=* serverless deploy
  

  In the debug output, scan for lines related to S3 operations—you’ll find explicit references to the deployment bucket Serverless is checking.

• Inspect your serverless.yml configuration
  Double-check if you’ve explicitly defined a deploymentBucket in your serverless.yml. If you have, verify the name matches exactly with what exists in S3 (note: S3 bucket names are case-sensitive in practice, even though DNS treats them as lowercase). Here’s an example of that configuration:

  provider:
    name: aws
    deploymentBucket:
      name: my-custom-deployment-bucket-123
  

  If you haven’t defined a custom bucket, Serverless auto-generates one based on your service name, region, and AWS account ID—debug logs will show this auto-generated name clearly.

• Verify your AWS credentials and active account
  Sometimes Serverless is using a different AWS account/credentials than the one where your S3 buckets live. Run this command to confirm which account your current AWS profile is linked to:

  aws sts get-caller-identity
  

  You can also explicitly specify a profile when running Serverless to ensure it targets the right account:

  serverless deploy --aws-profile your-target-profile
  

  Additionally, test if your credentials can access the bucket directly with the AWS CLI:

  aws s3 ls s3://your-bucket-name
  

  If this fails, it points to a permissions issue rather than a bucket existence problem.

Once you have the exact bucket name Serverless is trying to use, you can easily cross-verify it against your S3 console to spot typos, region mismatches, or permission gaps.

内容的提问来源于stack exchange，提问作者JVG