You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I understand the needs to use SSM parameter and would be happy to see a PR!
I have a question: if we specify as you wrote, would the actual value be visible in the environment variables section of the Lambda console?(or masked?)
I don't have experience with SSM so I need to learn the best practice around that. Thank you!
Ha, me neither! Reading this article it appears that using native "SSM->ENV" is not sufficient as it would mean anyone updating the stack would need access to the SSM (I think). I guess it should be done by reading the SSM "live" in the JS code.
As he says:
But, personally I still think you should:
fetch SSM parameter values at runtime
cache these values, and hot-swap when source values change
We would like to hold the Slack webhook URL in a secure SSM parameter so it isn't in source control.
Looks like we can pass a value into Lambda using that:
Would you accept a PR for that if you agree?
The text was updated successfully, but these errors were encountered: