You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running a Go handler with the Lambda module (github.com/aws/aws-lambda-go/lambda), setting the env var of AWS_LAMBDA_RUNTIME_API to http://localhost:2222 results in the following error:
2023/03/27 20:44:58 failed to get the next invoke: Get "http://http//localhost:2222/2018-06-01/runtime/invocation/next": dial tcp: lookup http: no such host
It appears this module does not want a URI scheme (specifically: http://) specified, which appears to be at odds with how other official AWS libraries that make use of the Lambda Runtime API (and AWS_LAMBDA_RUNTIME_API env var) seem to work.
Expected result
Whatever is found in the AWS_LAMBDA_RUNTIME_API env var is exactly the URI that should be used preceding the /2018-06-01/runtime/invocation/next (and other) endpoint(s).
Steps to reproduce
Run a module that imports github.com/aws/aws-lambda-go/lambda and ensure that your AWS_LAMBDA_RUNTIME_API starts with http://.
The text was updated successfully, but these errors were encountered:
Description of issue
When running a Go handler with the Lambda module (
github.com/aws/aws-lambda-go/lambda
), setting the env var ofAWS_LAMBDA_RUNTIME_API
tohttp://localhost:2222
results in the following error:It appears this module does not want a URI scheme (specifically:
http://
) specified, which appears to be at odds with how other official AWS libraries that make use of the Lambda Runtime API (andAWS_LAMBDA_RUNTIME_API
env var) seem to work.Expected result
Whatever is found in the
AWS_LAMBDA_RUNTIME_API
env var is exactly the URI that should be used preceding the/2018-06-01/runtime/invocation/next
(and other) endpoint(s).Steps to reproduce
Run a module that imports
github.com/aws/aws-lambda-go/lambda
and ensure that yourAWS_LAMBDA_RUNTIME_API
starts withhttp://
.The text was updated successfully, but these errors were encountered: