# Is it possible to persist the workspace configuration?

**URL:** <https://deeptalk.lambda.ai/t/is-it-possible-to-persist-the-workspace-configuration/4309>\
**Category:** Technical Help\
**Created:** [July 25, 2024, 9:31am UTC](https://deeptalk.lambda.ai/t/is-it-possible-to-persist-the-workspace-configuration/4309 "2024-07-25T09:31:53Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![jakobsteinbauer](https://avatars.discourse-cdn.com/v4/letter/j/57b2e6/32.png) [@jakobsteinbauer](https://deeptalk.lambda.ai/u/jakobsteinbauer)\
**Post date:** [July 25, 2024, 9:31am UTC](https://deeptalk.lambda.ai/t/is-it-possible-to-persist-the-workspace-configuration/4309/1 "2024-07-25T09:31:53Z")

</div>

When launching Lambda Cloud instances, I also connect a storage to it.  
I’ve seen that the content of the storage persists after restarting an instance, but that’s not true for my workspace configuration (like conda environments/ssh keys).  
Is there a way to make those persistent?

---

_[View the full topic](https://deeptalk.lambda.ai/t/is-it-possible-to-persist-the-workspace-configuration/4309)._
