Describe the feature
According to the OpenTelemetry documentation, the environment variable AWS_LAMBDA_EXEC_WRAPPER is supposed to be set to /opt/otel-sqs-handler for SQS-triggered Lambda handlers. However, there is no corresponding element for it in the AdotLambdaExecWrapper enum.
Use Case
When enabling ADOT instrumentation for an SQS-triggered Lambda function, there is no way to set the environment variable AWS_LAMBDA_EXEC_WRAPPER to /opt/otel-sqs-handler. And using the available /opt/otel-handler (REGULAR_HANDLER) leads to issues like this one.
Proposed Solution
Add a new element to the AdotLambdaExecWrapper enum that would support /opt/otel-sqs-handler.
Other Information
No response
Acknowledgements
CDK version used
2.139
Environment details (OS name and version, etc.)
N/A
Describe the feature
According to the OpenTelemetry documentation, the environment variable
AWS_LAMBDA_EXEC_WRAPPERis supposed to be set to/opt/otel-sqs-handlerfor SQS-triggered Lambda handlers. However, there is no corresponding element for it in the AdotLambdaExecWrapper enum.Use Case
When enabling ADOT instrumentation for an SQS-triggered Lambda function, there is no way to set the environment variable
AWS_LAMBDA_EXEC_WRAPPERto/opt/otel-sqs-handler. And using the available/opt/otel-handler(REGULAR_HANDLER) leads to issues like this one.Proposed Solution
Add a new element to the
AdotLambdaExecWrapperenum that would support/opt/otel-sqs-handler.Other Information
No response
Acknowledgements
CDK version used
2.139
Environment details (OS name and version, etc.)
N/A