Unknown request when lambda invoke

[daoudsh]

Hello,

when deploying the lambda using chalice and using the API Gateway, I got no error and it works find. But when I invoke the same lambda from another lambda I got error "Unknown request".

After debugging, I found that the 'requestContext' is None in case of lambda invoke from another lambda.

[kyleknap]

@daoudsh how are you invoking the chalice deployed lambda function from the other lambda function? A code snippet for both lambda functions would be useful.

[daoudsh]

@kyleknap thanks for your response.
I created a small example that show the error with some custom log in line 645 in file chalice/app.py

    def __call__(self, event, context):
    # This is what's invoked via lambda.
    # Sometimes the event can be something that's not
    # what we specified in our request_template mapping.
    # When that happens, we want to give a better error message here.
    print('event: ' + json.dumps(event))
    resource_path = event.get('requestContext', {}).get('resourcePath')
    if resource_path is None:
        return error_response(error_code='InternalServerError',
                              message='Unknown request.',
                              http_status_code=500)

You can see the full example in chalice_example

You can also find the fix for this issue in chalice_fork

thanks

[kyleknap]

@daoudsh Thanks for the info! Is there a particular reason you are using API Gateway + Lambda function integration (e.g. app.route() decorator) instead of just a pure lambda function (e.g. the app.lambda_function() decorator)? I'm only asking this because I noticed in the cha-invoke code you are trying to invoke the lambda function directly without making the request go through API Gateway.

[daoudsh]

@kyleknap this is no particular reason for that but it is easier to read and handle multi API in the same lambda. And also I am also java developer who like to use Spring Framework.

cha-invoke is invoking directly cha-lambda because sometimes I need to keep one lambda secured in AWS and not exposing it to public.

[kyleknap]

@daoudsh based off this comment:

cha-invoke is invoking directly cha-lambda because sometimes I need to keep one lambda secured in AWS and not exposing it to public.

I think it may make sense to convert your cha-lambda to use the app.lambda_function() decorator. When using the app.route() decorator you will always get an API Gateway API that is public. By using app.lambda_function(), it will only be able to be invoked by your account, assuming you do not add any extra permissions. You also will not have to worry about formatting the same payload that gets sent by API Gateway to invoke the lambda function and allow you to format your own schema. Hope this help!

[daoudsh]

@kyleknap
I replaced app.route() with app.lambda_function() and I didn't get the error.
The main reason why I used Chalice and its routing feature is that it makes the code readable and easy to maintenance.
thanks for your support.
Anyway I will keep using my fix (and I hope in future that this issue will be solved)