Skip to content

Add support for AWS Enable_Identity #10340

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

Open
max-allan-cgr opened this issue May 16, 2025 · 1 comment
Open

Add support for AWS Enable_Identity #10340

max-allan-cgr opened this issue May 16, 2025 · 1 comment

Comments

@max-allan-cgr
Copy link

Is your feature request related to a problem? Please describe.
When manually upgrading the fluent-bit version in the aws-for-fluent-bit image the new version of fluent-bit does not support Enable_Identity in the filters.

Describe the solution you'd like
Update and import the change found here to fluent-bit 1.9.10:
https://github.com/amazon-contributing/upstream-to-fluent-bit/pull/4/files
AWS seem to be keeping it to themselves and I don't see any PR for it.

Describe alternatives you've considered
Getting AWS to do this themselves. However, they seem reluctant to upgrade to a supported fluent-bit version and prefer to maintain their not-a-fork of 1.9.10. aws/aws-for-fluent-bit#885

Additional context
One can either use AWS's fluent-bit with the other bugs etc associated with 1.9.10 and the "Enable_Identity" option. Or a new version of fluent-bit and not be able to use the entity id and helm charts supplied by AWS without modifying the values. (As described here). You'd obviously need to build your own image with the new version of the fluent-bit binary too, so modifying some values as yaml is a small extra leap.

@swapneils
Copy link

We're working with Fluent Bit to merge the enable_entity feature.

Please see #10321 and #10207

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

2 participants