Оффлайн
- Регистрация
- 1 Мар 2015
- Сообщения
- 1,481
- Баллы
- 155
At , we work on many AI and cloud-native projects where secret management becomes complex — especially across environments and CI/CD pipelines. We're big fans of AWS SSM for storing configuration and secrets securely, but syncing them into .env files can be painful and repetitive.
To solve this in a cleaner and more reliable way, I built a CLI tool: ?
? What does it do?
Envilder reads a mapping file that links environment variable names to AWS SSM parameter paths.
Then it fetches the values securely and writes a clean .env file.
? Example
Your param-map.json might look like this:
{
"DB_HOST": "/my-app/dev/DB_HOST",
"DB_PASSWORD": "/my-app/dev/DB_PASSWORD"
}
Run:
envilder --map=param-map.json --envfile=.env
And you get:
DB_HOST=mydb.cluster-xyz.rds.amazonaws.com
DB_PASSWORD=supersecret
You can also use different AWS CLI profiles:
AWS_PROFILE=staging envilder --map=param-map.json --envfile=.env
? Why it helps teams
This small tool makes a big difference when:
Features
npm install -g envilder
Or:
envilder --map=param-map.json --envfile=.env --profile=aws-account
? I’d love your feedback
It’s still an early-stage project, but already helpful in several real-world teams.
If this sounds familiar, or you’ve solved this differently, I’d love to hear from you.
GitHub:
To solve this in a cleaner and more reliable way, I built a CLI tool: ?
? What does it do?
Envilder reads a mapping file that links environment variable names to AWS SSM parameter paths.
Then it fetches the values securely and writes a clean .env file.
? Example
Your param-map.json might look like this:
{
"DB_HOST": "/my-app/dev/DB_HOST",
"DB_PASSWORD": "/my-app/dev/DB_PASSWORD"
}
Run:
envilder --map=param-map.json --envfile=.env
And you get:
DB_HOST=mydb.cluster-xyz.rds.amazonaws.com
DB_PASSWORD=supersecret
You can also use different AWS CLI profiles:
AWS_PROFILE=staging envilder --map=param-map.json --envfile=.env
? Why it helps teams
This small tool makes a big difference when:
- ?? Onboarding new team members: no more “what’s the DB password?”
- ? Keeping environments in sync: any change in SSM is reflected across the team
CI/CD pipelines always up-to-date: e.g. GitHub Actions, CodeBuild, GitLab- ? Centralized configuration: avoid duplication and keep secrets in one secure place
- ? Supports multiple AWS profiles: ideal for multi-account or multi-env setups
Features- Works with SecureString and plain parameters
- CLI-first, fast, and script-friendly
- Compatible with any CI system
- Supports static values and fallbacks
- AWS profile support (AWS_PROFILE)
npm install -g envilder
Or:
envilder --map=param-map.json --envfile=.env --profile=aws-account
? I’d love your feedback
It’s still an early-stage project, but already helpful in several real-world teams.
If this sounds familiar, or you’ve solved this differently, I’d love to hear from you.
GitHub: