Serverless deploy creating empty S3 buckets


Has anybody here experienced deploying a serverless golang api to AWS lambda where it automatically created empty S3 buckets but never used it?

In my serverless.yml, I have already set the deploymentBucket to a specific S3 bucket name and it was correctly used during deployment but I am not sure why the other S3 buckets were created automatically and never used during deployment.

1 Like