Xray Tracing Servicemap not working as expected when we use $util.http.copyHeaders($ctx.request.headers)
After further investigation AppSync Service team confirmed that X-Amzn-Trace-Id header modification causing issue in Xray trace service mapping.
As per the documentation http-helpers-in-utils-http-js it seems to indicate that it will not forward "the restricted set of HTTP headers" but The trace header is not restricted in copyHeaders utility.
Please update the required documentation to disclose these restricted headers, which include auth and encoding headers among others.
We could use below solutions to move past this Xray trace service mapping issue.
Remove the header from the list.
Add required headers as per your use instead of forwarding all headers.
Hello Team,
Xray Tracing Servicemap not working as expected when we use $util.http.copyHeaders($ctx.request.headers)
After further investigation AppSync Service team confirmed that X-Amzn-Trace-Id header modification causing issue in Xray trace service mapping.
As per the documentation http-helpers-in-utils-http-js it seems to indicate that it will not forward "the restricted set of HTTP headers" but The trace header is not restricted in copyHeaders utility.
Please update the required documentation to disclose these restricted headers, which include auth and encoding headers among others.
We could use below solutions to move past this Xray trace service mapping issue.