Skip to content
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

Specify AWS identity to use for signature/request signing #1

Open
sid6mathur opened this issue Nov 29, 2017 · 0 comments
Open

Specify AWS identity to use for signature/request signing #1

sid6mathur opened this issue Nov 29, 2017 · 0 comments

Comments

@sid6mathur
Copy link

Thanks for the wonderful plugin, it works well! :)

Question: How do I explicitly set the AWS identity to use for request signing?
Scenario: We have 3 AWS users/keys setup on this server (say via profiles in ~/.aws/config) and one of them has the limited ES access that I wish to use with this plugin.

Current behaviour: It appears to use the AWS_SECRET_ACCESS_KEY and AWS_ACCESS_KEY that we set up in the environment (shell) that started the Caddyserver process. That's probably not kosher or scope-limited enough as its a webserver with its many plugins.

Desired behaviour:
a) Use a named profile as listed in ~/.aws/config to use for request signing, configurable as an option in the awses scope block in Caddyfile
b) An alternative is to list the AWS_SECRET_ACCESS_KEY and AWS_ACCESS_KEY explicitly in the awses scope block in Caddyfile, but not sure if that's a security good idea.

Thanks!
Siddharth

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant