A note for the community
- Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
- If you are interested in working on this issue or have submitted a pull request, please leave a comment
Problem
When AWS_CONFIG_FILE contains an endpoint_url, vector ignores it, requiring manually specifying endpoint_url in the config for the aws_s3 sink.
I would instead expect vector to read the endpoint_url from AWS_CONFIG_FILE automatically, the same way that it does with the region.
Configuration
Version
0.45.0
Debug Output
Example Data
No response
Additional Context
This has been observed for Vector running in a helm chart on OpenShift, attempting to get it writing to Ceph's S3 endpoint. While we were able to get this working by manually specifying the endpoint_url in the aws_s3 sink, ideally Vector would just read it from the AWS_CONFIG_FILE instead.
References
No response
A note for the community
Problem
When AWS_CONFIG_FILE contains an endpoint_url, vector ignores it, requiring manually specifying endpoint_url in the config for the aws_s3 sink.
I would instead expect vector to read the endpoint_url from AWS_CONFIG_FILE automatically, the same way that it does with the region.
Configuration
Version
0.45.0
Debug Output
Example Data
No response
Additional Context
This has been observed for Vector running in a helm chart on OpenShift, attempting to get it writing to Ceph's S3 endpoint. While we were able to get this working by manually specifying the endpoint_url in the aws_s3 sink, ideally Vector would just read it from the AWS_CONFIG_FILE instead.
References
No response