Bug: AWS ADOT LAMBDA layer stuck when using local invoke about aws-sam-cli HOT 5 CLOSED

Hi, thanks for bringing up the issue. I have been able to reproduce the issue and after some investigation, I see that the code is failing within the scripts inside the Lambda Layers as if you remove the environment variables AWS_LAMBDA_EXEC_WRAPPER and OTEL_PROPAGATORS, the invocation runs properly. Unfortunately I don't have the details inside the script that is making Lambda RIE have a errResetReceived error, are you able to provide the wrapper scripts used against the Lambda function?

from aws-sam-cli.

Hi @jysheng123 , in this sample APP the AWS_LAMBDA_EXEC_WRAPPER is set to use /opt/otel-instrument in the Lambda Adot Layer, which could be found here . You can also check out the Layer's definition here

from aws-sam-cli.

I found this open issue from Google because I'm getting the same error. But I think my problem might be different. It seems errors in AWS SAM are poorly reported. @jysheng123 how did you actually figured out the problem with the environment variables in this sample project? I run sam with the --debug option, but not much useful info reported except for this Invoke failed error=errResetReceived message.

from aws-sam-cli.

It turns out for this instance of the customer, I helped him out differently so its an issue on his own side of the code, this probably isnt the best place for a discussion as I will resolve this ticket, but if you have a bug/question, feel free to open up a ticket for it.

from aws-sam-cli.

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

from aws-sam-cli.