S3 event notifications not propagating trace headers to SQS destination

I am working on an application where we want to integrate X-Ray traces.

The flow of services looks like:
API Gateway -> Lambda -> S3 -> SQS -> Lambda -> API Gateway

X-Ray tracing from API Gateway to Lambda works fine.

to integrate S3 I instrumented the Node.js code by doing:
```
s3 = AWSXRay.captureAWSClient(new S3({ apiVersion: '2006-03-01' }));
```
S3 now appears in the CloudWatch ServiceLens trace details.

The same S3 bucket above is configured to send S3 event notifications to SQS. According the X-Ray docs S3 passes down tracing headers to downstream services such as SQS. However this appears not to be working as SQS does not appear in the trace details, there is nothing beyond S3 in the trace details. I also could not see any tracing details in the S3 object metadata and SQS message attributes which is where I expect tracing data to be propagated to, although this is an assumption and not mentioned in the doc.