Open pjuanda opened 6 years ago
To configure confd
with a ssm backend you should use the same steps as you would use to configure aws-cli
or any other app that uses AWS API, really. The steps are described here in many details: https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-getting-started.html
I can have it running btw, just wondering maybe it's better if we provide short documentation or link to aws documentation. There probably some people out there not really familiar with aws-cli
. I can help add the documentation if it's needed :D
Sure, that totally makes sense. Open a PR with the changes to docs if you want to contribute.
@okushchenko noted, i'll make the PR in this weekend :D
Was googling for confd aws ssm docs and landed here. Any reason the docs aren't merged yet?
edit: I see the docs aren't complete yet.
In particular, I want to learn how to set the prefix
when baking an AMI with confd using ssm.
Given a confd config that is executed using a systemd ExecPreStart
on the service it is generating a config for AND a situation where the paths are prefixed with the environment, e.g., /dev/app_name/db_pass
vs /prod/app_name/db_pass
... what is the best practice for injecting -prefix XXX
into the instance at run time (and not AMI build time)?
i can't find documentation on how to enable aws ssm parameter store integration with
confd
. Should we add it in the documentation ?I've found these environment variables needed to run
confd
Optionally, if you have custom path for your credential file, you should define its path.