-
Notifications
You must be signed in to change notification settings - Fork 133
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
Fluent bit Cloudwatch plugin use instance role #103
Comments
Hey @glnds sorry for the delayed response. Fluent Bit can use instance profile. Please enable debug logging, the AWS credential library for the core plugins will print detailed information on where it tried to look for credentials. Instance profile requires EC2 IMDS. It does not currently support IMDSv2... that's one thing I need to work on... Make sure IMDS is enabled and reachable by Fluent Bit |
The instance was still provisioned with IMDSv1. Currently, the issue seems to be gone, no clue why. It's a pity but I had to fall back to the fluentd client because I need a recursive wildcard for the input path and that's currently unsupported by fluentbit. |
Hi, I try to run Fluent bit on a Windows server 2016, the Cloudwatch plugins seem unable to authenticate using the Instance Profile. |
@smithdebug Please share debug logs if you want help with the issue |
@PettitWesley Currently having issues with authentication too. I am running a VM hosted in Azure not sure it makes a difference. Below are the debug logs. I have created a credentials file and placed it in .aws/credentials with a config as below
I have also set up env variables as below
|
Have you managed to get it working on windows server? |
@PettitWesley i have same issue, here is the debug logs, for me IMDS returns 401
|
@lado936 What version of FB are you using? I think this might be an IMDSv2 issue which is fixed by the latest version- do you know if you are using IMDSv2? @matthewfala Is this an IMDSv2 related thing? |
@PettitWesley Yep, after one day of debugging i found out that you pushed breaking changes and i was using latest tag for my fluentbit, set it to correct version and fixed it. |
Thank you @lado936. This happens when hop limit is set to 1 since the new image uses IMDSv2 by default and the fallback to the old system on hop count 1 has a bug. Working on a fix to allow for a fallback to IMDSv1 if IMDSv2 is not available due to the hop count. Here's some information for others to help: |
Yes i figured it out, just you have to notify people when releasing changes like that, but yeah, using latest tag is quite an unproffesional from me 😁 |
Hi, I try to run Fluent bit on an Amazon Linux 2, everything works fine except that the Cloudwatch plugins seems unable to authenticate using the Instance Profile.
Any idea how I can tell the Cloudwatch plugin to use the IAM instance Profile to authenticate towards AWS?
The text was updated successfully, but these errors were encountered: