# Specify custom s3Key for package

**URL:** <https://forum.serverless.com/t/specify-custom-s3key-for-package/4532>\
**Category:** Serverless Framework\
**Created:** [May 18, 2018, 1:45pm UTC](https://forum.serverless.com/t/specify-custom-s3key-for-package/4532 "2018-05-18T13:45:34Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![areichman](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.serverless.com/areichman/32/1987_2.png) [@areichman](https://forum.serverless.com/u/areichman)\
**Post date:** [May 18, 2018, 1:45pm UTC](https://forum.serverless.com/t/specify-custom-s3key-for-package/4532/1 "2018-05-18T13:45:34Z")

</div>

Our CI/CD system currently stores our zip bundles in two locations:

- A “snapshot” bucket with all recent builds. This gets cleaned up every 30 days using S3 lifecycle rules.
- A “latest” bucket with the most recent copy of all services in our product.

The “snapshot” bucket seems to work well with what `sls package` does by default with timestamps to denote the builds. No issues here.

For our “latest” bucket, we use a flatter directory structure without any timestamps. We can specify this bucket as the deployment bucket by passing a command line option and using variables inside of our `serverless.yml` file. However, I don’t see any way to customize the s3Key that will be inserted into the compiled CloudFormation template.

Is it possible to also specify a different value for the s3Key when using `sls package`?