HTTP AWS SigV4 authentication strategy #22125
Labels
sink: http
Anything `http` sink related
type: feature
A value-adding code addition that introduce new functionality.
A note for the community
Use Cases
To send logs from Vector to the AWS OpenSearch Ingestion pipeline (OSIS) using the HTTP sink, similar to the approach taken by Fluent Bit, we need to ensure that the HTTP sink supports AWS SigV4 authentication. This includes utilizing
assume_role
,access_key_id
, orcredentials_file
for proper authentication.Attempted Solutions
No response
Proposal
Enable the HTTP sink to leverage AWS SigV4 authentication by configuring the
auth.strategy: aws
. This can be accomplished using eitherauth.assume_role
,auth.access_key_id
, orauth.credentials_file
,and one field for the aws service
auth.service
.References
#6204
#14150
Version
0.43.1
The text was updated successfully, but these errors were encountered: