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

aws creds in config section? #4

Open
cdenneen opened this issue Aug 25, 2016 · 3 comments
Open

aws creds in config section? #4

cdenneen opened this issue Aug 25, 2016 · 3 comments

Comments

@cdenneen
Copy link

Does this support config options like the rest of the aws plugins do with parameters in the configuration. Seems from the README all other methods are available but this.

Also when will this plugin be added to the logstash plugins list now that it's been added here?

https://www.elastic.co/guide/en/logstash/current/input-plugins.html

Not sure it's necessary but noticed with some other plugins additional creds for the other resources, so different keys for Kinesis, Dynamo, CloudWatch?

Example from: https://github.com/samcday/logstash-output-kinesis/blob/master/README.md

input {
  kinesis {
    # ...

    aws_credentials_file => "/etc/logstash/aws_credentials"
    access_key => ""
    secret_key => ""

    # You can provide specific credentials for CloudWatch metrics:
    metrics_access_key => ""
    metrics_secret_key => ""
  }
}
@codekitchen
Copy link
Collaborator

My company has a policy of never storing AWS creds in config files, so I just never implemented it. Looks like we should probably implement it for consistency with other plugins, though.

Good question about the plugins list, I'll ask around.

@nickmaccarthy
Copy link

+1 for this. Specifying the creds in the config vs trying to setting them in an env_var hoping the class picks the right ones would be much easier to manage.

@cdenneen
Copy link
Author

cdenneen commented Dec 1, 2018

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

No branches or pull requests

3 participants