Serverless Stack

&gt; Seed lets you store them as secret environment variables through the Seed console. Seed internally encrypts them using <https://aws.amazon.com/kms/|AWS KMS> and stores them. They are then decrypted during the build process. And upon deployment, *Seed sets them as Lambda environment variables.*
Does this only happen for SLS? SEED doesn’t seem to set them for SST functions?

Hi <@U01PSS0ETUH>, yeah that’s correct. We should’ve made this more clear in the doc <@U01J5Q8HV5Z>.

In SST, you can set the SEED secret (ie. `MY_SECRET`) as env vars for all your Lambda functions like this:
```app.addDefaultFunctionEnv({
  MY_SECRET: procress.env.MY_SECRET,
});```

Cool, yeah I figured it was a good opportunity to finally start using SSM for this

Just caught me off guard, but at least it's a chance for me to try out SQS redrives in dev, didn't know that feature existed

Updated <https://seed.run/docs/storing-secrets>