-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Retry AWS credential load errors #9291
Comments
We have the same issue but this time for SQS,
Given that the access to SQS is granted from AWS IAM. |
We've kind of same issue with Elasticsearch sink connected to AWS Opensearch. We notice that time to time and at some point in time when log volume spikes, credential provider fails and vector drops messages even end to end acknowledgments are enabled, so missing the contract about deliver with guarantee. When enabled Notes:
In order to not duplicate a lot, I create this support question at discord: discord thread Example of logs:
|
A user reported that Vector was failing to start because it couldn't load AWS credentials in the
aws_s3
sink. They run a proxy sidecar for these credential requests, and Vector was starting up before the sidecar does. It seems reasonable to retry loading of credentials indefinitely.The text was updated successfully, but these errors were encountered: