AWS X-Ray trace header and has an invalid value (SNS Publish)

[men6288]

Hi All,

Has anyone came across the following error when publishing an SNS message? I am not declaring an X-Ray trace header and have never seen this before so am quite puzzled on what to do.

{ "error": "ClientError", "cause": "{\"errorMessage\": \"An error occurred (InvalidParameterValue) when calling the Publish operation: The request has a 'X-Amzn-Trace-Id' HTTP header which is reserved for AWS X-Ray trace header and has an invalid value 'redacted'\", \"errorType\": \"ClientError\", \"stackTrace\": [\" File \\\"/var/task/states.py\\\", line 128, in event_handler\\n publish_sns(event[\\\"ticket\\\"]) # Ticket.py\\n\", \" File \\\"/var/task/ticket.py\\\", line 253, in publish_sns\\n result = sns.publish(\\n\", \" File \\\"/opt/python/lib/python3.8/site-packages/botocore/client.py\\\", line 508, in _api_call\\n return self._make_api_call(operation_name, kwargs)\\n\", \" File \\\"/opt/python/lib/python3.8/site-packages/botocore/client.py\\\", line 915, in _make_api_call\\n raise error_class(parsed_response, operation_name)\\n\"]}" }

Thanks in advance

[yoonjs2]

I'm experiencing similar error when accessing SQS with lambda using boto3 apis (1.27.41). I am not declaring any X-Ray trace header and have never seen this before.

ClientError: An error occurred (InvalidParameterValue) when calling the GetQueueUrl operation: The request has a 'X-Amzn-Trace-Id' HTTP header which is reserved for AWS X-Ray trace header and has an invalid value 'Root%3D1-62e5016a-22bd960332bb27720e8f868d%3BParent%3D51e60fa209125b51%3BSampled%3D0'

[tim-finnigan]

There was a PR recently merged to fix the _X_AMZN_TRACE_ID environment variable name. The change was integrated in boto3 1.24.41 per the CHANGELOG. @men6288 are you also using boto3 v1.24.41? Do you have a value assigned to that environment variable? I'm having trouble trying to reproduce the issue. If you can provide a full code snippet and debug logs by adding boto3.set_stream_logger('') that could help give more insight into the behavior.

[men6288]

Thanks @tim-finnigan, we have ours pin to the latest version. When was 41 released?

I'll try and get an example sent over to you before the end of the weekend

[kyleknap]

This was a regression. We reverted the bad change and released it. You should no longer be impacted using versions 1.24.42 for boto3 or 1.27.42 for botocore.

[men6288]

Thanks for reverting the change. Let me know if you guys want me to debug at all and I will see if I can get the information for ya.