# Using lambda env vars encryption in transit feature

**URL:** <https://forum.serverless.com/t/using-lambda-env-vars-encryption-in-transit-feature/21073>\
**Category:** Serverless Framework\
**Tags:** aws, lambda, security\
**Created:** [March 22, 2025, 9:49am UTC](https://forum.serverless.com/t/using-lambda-env-vars-encryption-in-transit-feature/21073 "2025-03-22T09:49:21Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![yardensade](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.serverless.com/yardensade/32/8308_2.png) [@yardensade](https://forum.serverless.com/u/yardensade)\
**Post date:** [March 22, 2025, 9:49am UTC](https://forum.serverless.com/t/using-lambda-env-vars-encryption-in-transit-feature/21073/1 "2025-03-22T09:49:22Z")

</div>

AWS offers in the lambda configuration (aws console) option to encrypt the environment variables.  
Encryption in transit → Enable helpers for encryption in transit

I can’t find any reference for this in serverless framework.  
The result right now is that all env vars declared in serverless.yml are viewable to anyone with read permissions in the console, this is a bad security practice.