# Deploying DDB stream events to specific stage with v1

**URL:** <https://forum.serverless.com/t/deploying-ddb-stream-events-to-specific-stage-with-v1/595>\
**Category:** Serverless Framework\
**Tags:** aws\
**Created:** [October 19, 2016, 8:52pm UTC](https://forum.serverless.com/t/deploying-ddb-stream-events-to-specific-stage-with-v1/595 "2016-10-19T20:52:33Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![johncmckim](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.serverless.com/johncmckim/32/27_2.png) [@johncmckim](https://forum.serverless.com/u/johncmckim)\
**Post date:** [October 21, 2016, 6:08am UTC](https://forum.serverless.com/t/deploying-ddb-stream-events-to-specific-stage-with-v1/595/2 "2016-10-21T06:08:04Z")

</div>

@adambiggs I assume you don’t share the DynamoDB table across stages? If not, you can have different instances of your lambda connected to each tables stream.

You can use the solution I describe here - [Disable Function Per Stage?](http://forum.serverless.com/t/disable-function-per-stage/604/6?u=johncmckim). But you run the same risks by only ever executing the code in production.

---

_[View the full topic](https://forum.serverless.com/t/deploying-ddb-stream-events-to-specific-stage-with-v1/595)._
