ISSUE 9670: Adds AWS credentials refresh to out_prometheus_remote_write #9765
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Handle 403 http error code when credentials expired, credentials refreshed from
~/.aws/credentials
.Fixes: #9670
Similar implementation already exists for
kinesis_streams
:fluent-bit/src/aws/flb_aws_util.c
Line 205 in 3178e6e
Steps to reproduce:
~/.aws/credentials
as default profile.#1
to refresh credentials in~/.aws/credentials
with much fresh credentials (usually done by automation):Before the PR fix: Fluent-bit keeps failing with 403 as it is using old expired credentials that is cached in memory
After the PR fix: Fluent-bit picks up fresh credentials without downtime.
Testing
Before we can approve your change; please submit the following in a comment:
If this is a change to packaging of containers or native binaries then please confirm it works for all targets.
ok-package-test
label to test for all targets (requires maintainer to do).Documentation
Backporting
Fluent Bit is licensed under Apache 2.0, by submitting this pull request I understand that this code will be released under the terms of that license.