AWS SDK: Add an option to add tracing information to request headers instead of message attributes

[gillesbergerp]

This concerns the AWS SDK instrumentation

Right now, the instrumentation injects the tracing information in SNS/SQS message attributes. If you want to make use of SNS active tracing in X-Ray, tracing information is only passed along if it is in the request header.

We could introduce a configuration option for giving the user control whether it should be injected in the message attributes or as request header.

[github-actions]

👋 This issue has been marked as stale because it has been open with no activity. You can: comment on the issue or remove the stale label to hold stale off for a while, add the keep label to hold stale off permanently, or do nothing. If you do nothing this issue will be closed eventually by the stale bot.

[xuan-cao-swi]

Hi @gillesbergerp , I am currently trying to figure out the context here as someone is not familiar with sns and xray.

If you want to make use of SNS active tracing in X-Ray, tracing information is only passed along if it is in the request header.

Do you mean only pass tracing information (e.g. traceparent generated from otel) to message_attributes if xray id is in request header from context?