You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
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.
The text was updated successfully, but these errors were encountered: