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
The Vector docs indicate that AWS credential files are supported as an authentication method, however that doesn't seem to be the case. Attempting to use a credentials file in a sink ends up with a log message indicating an error (Overriding the credentials file is not supported.). Reading the code, it looks like the credentials provider implementation does not actually support this method.
Since this method of AWS authentication is intended to be supported, it should actually work.
It looks like when Vector converted from rusoto to the official AWS SDK
that support for AWS credentials files was dropped. The docs indicate
this is supposed to be a supported option, so this PR adds support for
AWS credentials files by adding the correct credential provider.
Closesvectordotdev#16632.
Updated the issue with a minimal example that shows how to reproduce the error. If you run that example through vector validate it shows the issue pretty clearly:
$ vector validate /tmp/vector.toml
√ Loaded ["/tmp/vector.toml"]
Component errors
----------------
x Sink "prometheus_remote_write": Overriding the credentials file is not supported.```
A note for the community
I have a PR ready to go to fix this.
Problem
The Vector docs indicate that AWS credential files are supported as an authentication method, however that doesn't seem to be the case. Attempting to use a credentials file in a sink ends up with a log message indicating an error (
Overriding the credentials file is not supported.
). Reading the code, it looks like the credentials provider implementation does not actually support this method.Since this method of AWS authentication is intended to be supported, it should actually work.
Configuration
Version
0.28.0
Debug Output
No response
Example Data
No response
Additional Context
No response
References
No response
The text was updated successfully, but these errors were encountered: