I've recently open-sourced a small CLI called Envilder: https://github.com/macalbert/envilder

It generates .env files by pulling parameters directly from AWS SSM Parameter Store.

I built it because I kept running into the same problem: secrets are stored securely in SSM, but syncing them into local environments or CI/CD pipelines is often manual, error-prone, or inconsistent.

With Envilder, you define a JSON map of environment variable names and their corresponding SSM paths. For example:

{ "DB_HOST": "/my-app/dev/DB_HOST", "DB_PASSWORD": "/my-app/dev/DB_PASSWORD" }

Then you run:

envilder --map=param\_map.json --envfile=.env

It outputs a .env file with all the resolved values.

The tool supports SecureString and plain parameters, static values, and fallback defaults. It’s meant to work in both local development and CI contexts like GitHub Actions or CodeBuild.

It's still in early stages, and I'd love to hear your thoughts:

- Is this something you'd find useful? - Any ideas or edge cases you'd consider?

Thanks in advance!