-
Notifications
You must be signed in to change notification settings - Fork 95
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
instance profile credentials expiring #58
Comments
Hi @chrono , I'll look into this issue. KPL itself has |
OK, I think it'll be a bug. I'll fix it. |
Hi @chrono , I released v1.0.1 which fixes this problem. Please try this version. Thank you for reporting! After confirming your situation is resolved, I'll yank v1.0.0 from rubygems since this is a huge bug. |
I had the same problem, but using |
Yup it has been working for me for the last few days on 1.0.1. So I can ditch my custom patched 1.0.0 now :) |
Thanks for the quick turnaround! |
Great to hear from you! I'm so sorry for inconvenience. If you have any issue, feel free to submit an issue on this repository. |
The plugin (I'm using
kinesis_producer
) does not seem fetch fresh tokens from the metadata service regularly.The credentials seem to be fetched once at plugin startup in https://github.com/awslabs/aws-fluent-plugin-kinesis/blob/v1.0.0/lib/fluent/plugin/kinesis_helper/credentials.rb#L47. The name of the method
default_credentials_provider
is suggesting that it returns a provider, instead it returns credentials.The credentials are then passed in to the client which has a loop to refresh the credentials https://github.com/awslabs/aws-fluent-plugin-kinesis/blob/v1.0.0/lib/kinesis_producer/daemon.rb#L183-L192. After ~6 hours, the credentials are no longer valid and the producer stalls.
Shouldn't this use the provider instead and dereference the credentials property regularly?
[edited to replace
master
withv1.0.0
in the file links]The text was updated successfully, but these errors were encountered: