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

See title.

Use Cases

When AWS hosted applications don't send traces to X-Ray, Vector can act as the adapter between the sender and AWS X-Ray.

Attempted Solutions

Instead of a dedicated X-Ray sink, one can send traces to X-Ray via the HTTP sink and SigV4 signing, but that's much less elegant than directly using the AWS SDK.

Proposal

I will add a preliminary PR for the Sink that so far worked for me locally.

References

No response

Version

No response