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

Off the back of the discussion in #23164 the http_client source currently does not use AWS authentication despite it being a valid auth strategy. This is presumably an outcome of #22744 which adds AWS authentication for the http sink and a reuse of the authentication struct in the http_client source.

Use Cases

Reading from AWS endpoints, e.g. AWS Managed Service for Prometheus.

Attempted Solutions

See the following vector.toml:

[sources.http_client]
type = "http_client"
endpoint = "<ENDPOINT>"
auth = {strategy = "aws", auth = {}, service = "aps"}
method = "POST"
headers.Content-Type = ["application/x-www-form-urlencoded"]
query.query = "up"

[sinks.blackhole]
type = "blackhole"
inputs = ["http_client"]

On using this, the connection fails with a 403 even if Vector can load the AWS profile.

Proposal

Adjust the http_client source to also honour AWS authentication.

References

No response

Version

0.48.0