# Serverless deploy creating empty S3 buckets

**URL:** <https://forum.serverless.com/t/serverless-deploy-creating-empty-s3-buckets/5817>\
**Category:** Serverless Framework\
**Tags:** lambda\
**Created:** [September 17, 2018, 12:32am UTC](https://forum.serverless.com/t/serverless-deploy-creating-empty-s3-buckets/5817 "2018-09-17T00:32:49Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![andrew\_lanex](https://avatars.discourse-cdn.com/v4/letter/a/b19c9b/32.png) [@andrew\_lanex](https://forum.serverless.com/u/andrew_lanex)\
**Post date:** [September 17, 2018, 12:32am UTC](https://forum.serverless.com/t/serverless-deploy-creating-empty-s3-buckets/5817/1 "2018-09-17T00:32:50Z")

</div>

Hello,

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.