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
Is your feature request related to a problem? Please describe.
When you have the AWS credentials file which is under rolling update by some scheduler then after some time fluent bit still working with old AWS credentials and failing with 403 when sending metrics to AWS Prometheus.
Describe the solution you'd like
fluentbit should reload these credentials out of the box.
Describe alternatives you've considered
I've used batch job which is restarting the service itself or did a hot reload
Additional context
In case if users have rolling credentials then they should prepare workarounds.
The text was updated successfully, but these errors were encountered:
ivanguravel
changed the title
AWS rolling credentials support
AWS rolling credentials from file support for Promethues
Dec 21, 2024
ivanguravel
changed the title
AWS rolling credentials from file support for Promethues
AWS rolling credentials from file support for Prometheus
Dec 21, 2024
Is your feature request related to a problem? Please describe.
When you have the AWS
credentials
file which is under rolling update by some scheduler then after some time fluent bit still working with old AWS credentials and failing with 403 when sending metrics to AWS Prometheus.Describe the solution you'd like
fluentbit should reload these credentials out of the box.
Describe alternatives you've considered
I've used batch job which is restarting the service itself or did a
hot reload
Additional context
In case if users have rolling credentials then they should prepare workarounds.
The text was updated successfully, but these errors were encountered: