Closed jeanlescure closed 3 years ago
The README says:
(if you're using AWS CLI v2, you'll need to add
--cli-binary-format raw-in-base64-out
to the above command)
This is a breaking change AWS made with v2: https://docs.aws.amazon.com/cli/latest/userguide/cliv2-migration.html#cliv2-migration-binaryparam
Thank you for the fix and the context @mhart !
My bad for not reading the README thoroughly enough. I can corroborate that the --cli-binary-format raw-in-base64-out
worked for me using aws-cli v2 :smile:
Cheers :+1:
Describe the bug :bug:
When running
docker-lambda
in "stay-open" API mode, if I invoke my lambda using the AWS CLI command provided in the README, since I have AWS CLI v2.x installed, I get anUnexpected token
error and my lambda function never even tries to execute.Steps to Reproduce :memo:
Steps to reproduce the behavior:
Currently this generates the following error:
Expected behavior :thinking:
The lambda should execute normally.
Environment :computer:
Using Docker version 19.03.13-ce, build 4484c46d9d
Additional context
A workaround for this issue is to invoke the labda using aws-cli v1.x, but in my case this is not a sustainable solution as there are aws-cli v2 features I use in my day-to-day work activities.