-
Notifications
You must be signed in to change notification settings - Fork 88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use Swarm Secrets for receive AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY #30
Comments
This makes sense. Want to open a PR? 🙂 |
Ok I can, but I will need some time. 👍 |
Any progress on this? |
no sorry, very busy with other projects... at this point if other wants to open PR, please |
I think you do not need to alter the script but rather alter the readme. I solved the problem by just creating the whole credentials file as a secret and referencing the actual file with the env var AWS_SHARED_CREDENTIALS_FILE. Btw. not only for secrets but also pretty useful for local environments, if you prefer to store the credentials not within yml. i.e.:
|
Currently S3 documentation with compose file reports:
but
.env
file is not supported with a Stack deployment over Swarm. Instead, Swarm implements Secrets that would be a better solution for security purpose.Use of them have to be implemented with the application, reading for example from
/run/secrets/aws_access_key_id
and/run/secrets/aws_secret_access_key
, because secrets are not injectable directly fromdocker-stack.yml
into environemnt.The text was updated successfully, but these errors were encountered: