# AWS Lambda Versioning and Serverless Env Staging (serverless.env.yml)

**URL:** <https://forum.serverless.com/t/aws-lambda-versioning-and-serverless-env-staging-serverless-env-yml/146>\
**Category:** Serverless Architectures\
**Tags:** aws\
**Created:** [August 18, 2016, 9:25pm UTC](https://forum.serverless.com/t/aws-lambda-versioning-and-serverless-env-staging-serverless-env-yml/146 "2016-08-18T21:25:24Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![ponyengine](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.serverless.com/ponyengine/32/66_2.png) [@ponyengine](https://forum.serverless.com/u/ponyengine)\
**Post date:** [August 18, 2016, 9:25pm UTC](https://forum.serverless.com/t/aws-lambda-versioning-and-serverless-env-staging-serverless-env-yml/146/1 "2016-08-18T21:25:24Z")

</div>

I would like to get an understanding of how Serverless is meant to interact with the AWS Versioning Process/Policy. ([http://docs.aws.amazon.com/lambda/latest/dg/versioning-intro.html#versioning-intro-publish-version](http://docs.aws.amazon.com/lambda/latest/dg/versioning-intro.html#versioning-intro-publish-version)) Is the serverless.env.yml supposed to be another way to stage our functions or does it suppose to connect with the methodology in the versioning and alias document.

What I have noticed is that setting the stages create separate instances of the functions and then one can apply versioning on top of them with aliases. I would just like to get an understanding or example behind this in order to have an awesome version management of my code.

---

<div class="post-metadata">

**Author:** ![flomotlik](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.serverless.com/flomotlik/32/3_2.png) [@flomotlik](https://forum.serverless.com/u/flomotlik)\
**Post date:** [August 22, 2016, 10:28am UTC](https://forum.serverless.com/t/aws-lambda-versioning-and-serverless-env-staging-serverless-env-yml/146/2 "2016-08-22T10:28:41Z")

</div>

We’re still discussing the details behind Versioning and Alias and how we want to implement this in Serverless. You can stay up to date on the issue here: [https://github.com/serverless/serverless/issues/1457](https://github.com/serverless/serverless/issues/1457)

At the moment we don’t support versioning or aliasing at all and we’re not sure if we should in the future.

---

<div class="post-metadata">

**Author:** ![fsantana](https://avatars.discourse-cdn.com/v4/letter/f/34f0e0/32.png) [@fsantana](https://forum.serverless.com/u/fsantana)\
**Post date:** [December 21, 2016, 5:49pm UTC](https://forum.serverless.com/t/aws-lambda-versioning-and-serverless-env-staging-serverless-env-yml/146/3 "2016-12-21T17:49:38Z")

</div>

Is versioning and alias function ready to use?

---

<div class="post-metadata">

**Author:** ![rowanu](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.serverless.com/rowanu/32/75_2.png) [@rowanu](https://forum.serverless.com/u/rowanu)\
**Post date:** [December 21, 2016, 9:29pm UTC](https://forum.serverless.com/t/aws-lambda-versioning-and-serverless-env-staging-serverless-env-yml/146/4 "2016-12-21T21:29:21Z")

</div>

Yes, new versions are now created since [this PR was merged](https://github.com/serverless/serverless/pull/2676).