# Propagate parameters into Lambda
**URL:** https://forum.serverless.com/t/propagate-parameters-into-lambda/14935
**Category:** Serverless Architectures
**Tags:** lambda
**Created:** [May 6, 2021, 10:14am UTC](https://forum.serverless.com/t/propagate-parameters-into-lambda/14935 "2021-05-06T10:14:48Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@alper](https://forum.serverless.com/u/alper)
#### Post date: [May 6, 2021, 10:14am UTC](https://forum.serverless.com/t/propagate-parameters-into-lambda/14935/1 "2021-05-06T10:14:48Z")
We see there is a way to inject parameters into Lambda on initialization as described in this post: [Sharing Secrets with AWS Lambda Using AWS Systems Manager Parameter Store | AWS Compute Blog](https://aws.amazon.com/blogs/compute/sharing-secrets-with-aws-lambda-using-aws-systems-manager-parameter-store/)
It’s not clear to me then though when and how often the Lambda would be re-initialized. So when we update a value, how do we get it to propagate into our lambdas?
Ideally we would like to have something like [`envconsul`](https://github.com/hashicorp/envconsul) do it which watches the values and when they change, forcibly restarts the process that it’s running. Is there a way to do something like this?
---
### Author:  [@iniinikoski](https://forum.serverless.com/u/iniinikoski)
#### Post date: [December 6, 2021, 2:47pm UTC](https://forum.serverless.com/t/propagate-parameters-into-lambda/14935/3 "2021-12-06T14:47:17Z")
Hi @alper ,
did you find any solution for this…? Our difference is, we use Vault - and the Lambda Extension for it ([Use AWS Lambda Extensions to Securely Retrieve Secrets From HashiCorp Vault](https://www.hashicorp.com/blog/aws-lambda-extensions-for-hashicorp-vault)). The problem with that one, is that we can use this as a proxy to Vault - or read the secrets from disk (not ideal). Really missing also something like envconsul for Lambda… 🙂