Open ijtarano opened 5 months ago
Thanks for opening this issue, just to understand the context here, are you running sam local start-lambda
and then passing the endpoint to your script here?
Yes, of course, It works perfectly with "RequestResponse" InvocationType parameter ;)
Thanks for letting us know, this is something that we guard against since async execution isn't something that is currently implemented. I can tag this issue to a feature request instead.
As an alternative, it's possible to use our sam sync --watch
command to deploy to AWS and update code live, similar to how one would use sam local start-lambda
. This could be a workaround for now.
Description:
It seems like Event in boto3 invoke method doesn't work with SAM Local even when boto3 accept this parameter (https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/lambda/client/invoke.html)
Steps to reproduce:
Observed result:
ClientError: An error occurred (NotImplemented) when calling the Invoke operation: invocation-type: Event is not supported. RequestResponse is only supported.
Additional environment details (Ex: Windows, Mac, Amazon Linux etc)
sam --version
: SAM CLI, version 1.113.0