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

Changing credentials in logstash config file after start. #161

Closed
Abolurah opened this issue Jul 12, 2020 · 1 comment
Closed

Changing credentials in logstash config file after start. #161

Abolurah opened this issue Jul 12, 2020 · 1 comment

Comments

@Abolurah
Copy link

Hi All,
I have a question about the loading of credentials (aws_access_key_id and aws_secret_access_key) after logstash already running.
In my case I get credentials from Http poller input, saving them into @metadata , in order to use them in amazon_es output, but it's not working, I get "Got response code '403'" , but when credentials are hardcoded it works fine.
So my question is, is it possible to load amazon credentials during logstash run, or it MUST be hardcoded (or passed as environment variables) when logstash starts?

if there is another option you using/recommending I will be glad to hear about it.

Thanks in advance.

@Abolurah
Copy link
Author

After checking this issue with amazon , looks like there is no way to change credentials without logstash restart.

In general, the methods for providing credentials to the Amazon ElasticSearch plugins are as follows:

• User passed aws_access_key_id and aws_secret_access_key in amazon_es configuration
• Environment variables - AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY (RECOMMENDED since they are recognized by all the AWS SDKs and CLI except for .NET), or AWS_ACCESS_KEY and AWS_SECRET_KEY (only recognized by Java SDK)
• Credential profiles file at the default location (~/.aws/credentials) shared by all AWS SDKs and the AWS CLI
• Instance profile credentials delivered through the Amazon EC2 metadata service
Attempting to plug the data into the @metadata will not work

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