How to configure asynchronous lambda invocation via API Gateway using SAM?












1















I have configured a lambda proxy integration with API Gateway using SAM specification and am invoking the lambda asynchronously by passing X-Amz-Invocation-Type: "'Event'" header



  ApiGateway:
Type: AWS::Serverless::Api
Properties:
StageName: prod
DefinitionBody:
swagger: "2.0"
info:
title:
Ref: AWS::StackName
description: API endpoint for invoking LambdaFunction
version: 1.0.0
paths:
/items:
post:
consumes: ["application/json"]
produces: ["application/json"]
responses: {}
x-amazon-apigateway-integration:
type: "aws_proxy"
uri:
Fn::Sub: arn:aws:apigateway:${AWS::Region}:lambda:path/2015-03-31/functions/${LambdaFunction.Arn}/invocations
passthroughBehavior: "when_no_match"
httpMethod: "POST"
requestParameters:
integration.request.header.X-Amz-Invocation-Type: "'Event'"


The problem is that lambda is returning empty response(invoked async) so API Gateway is throwing following error



Wed Nov 14 08:03:14 UTC 2018 : Execution failed due to configuration error: Malformed Lambda proxy response
Wed Nov 14 08:03:14 UTC 2018 : Method completed with status: 502



Is this behaviour expected? Do I have to define responses explicitly? I do not want to throw 200 always because I also want to send bad request and unauthorized errors as well.What's the solution to avoid this problem?










share|improve this question



























    1















    I have configured a lambda proxy integration with API Gateway using SAM specification and am invoking the lambda asynchronously by passing X-Amz-Invocation-Type: "'Event'" header



      ApiGateway:
    Type: AWS::Serverless::Api
    Properties:
    StageName: prod
    DefinitionBody:
    swagger: "2.0"
    info:
    title:
    Ref: AWS::StackName
    description: API endpoint for invoking LambdaFunction
    version: 1.0.0
    paths:
    /items:
    post:
    consumes: ["application/json"]
    produces: ["application/json"]
    responses: {}
    x-amazon-apigateway-integration:
    type: "aws_proxy"
    uri:
    Fn::Sub: arn:aws:apigateway:${AWS::Region}:lambda:path/2015-03-31/functions/${LambdaFunction.Arn}/invocations
    passthroughBehavior: "when_no_match"
    httpMethod: "POST"
    requestParameters:
    integration.request.header.X-Amz-Invocation-Type: "'Event'"


    The problem is that lambda is returning empty response(invoked async) so API Gateway is throwing following error



    Wed Nov 14 08:03:14 UTC 2018 : Execution failed due to configuration error: Malformed Lambda proxy response
    Wed Nov 14 08:03:14 UTC 2018 : Method completed with status: 502



    Is this behaviour expected? Do I have to define responses explicitly? I do not want to throw 200 always because I also want to send bad request and unauthorized errors as well.What's the solution to avoid this problem?










    share|improve this question

























      1












      1








      1








      I have configured a lambda proxy integration with API Gateway using SAM specification and am invoking the lambda asynchronously by passing X-Amz-Invocation-Type: "'Event'" header



        ApiGateway:
      Type: AWS::Serverless::Api
      Properties:
      StageName: prod
      DefinitionBody:
      swagger: "2.0"
      info:
      title:
      Ref: AWS::StackName
      description: API endpoint for invoking LambdaFunction
      version: 1.0.0
      paths:
      /items:
      post:
      consumes: ["application/json"]
      produces: ["application/json"]
      responses: {}
      x-amazon-apigateway-integration:
      type: "aws_proxy"
      uri:
      Fn::Sub: arn:aws:apigateway:${AWS::Region}:lambda:path/2015-03-31/functions/${LambdaFunction.Arn}/invocations
      passthroughBehavior: "when_no_match"
      httpMethod: "POST"
      requestParameters:
      integration.request.header.X-Amz-Invocation-Type: "'Event'"


      The problem is that lambda is returning empty response(invoked async) so API Gateway is throwing following error



      Wed Nov 14 08:03:14 UTC 2018 : Execution failed due to configuration error: Malformed Lambda proxy response
      Wed Nov 14 08:03:14 UTC 2018 : Method completed with status: 502



      Is this behaviour expected? Do I have to define responses explicitly? I do not want to throw 200 always because I also want to send bad request and unauthorized errors as well.What's the solution to avoid this problem?










      share|improve this question














      I have configured a lambda proxy integration with API Gateway using SAM specification and am invoking the lambda asynchronously by passing X-Amz-Invocation-Type: "'Event'" header



        ApiGateway:
      Type: AWS::Serverless::Api
      Properties:
      StageName: prod
      DefinitionBody:
      swagger: "2.0"
      info:
      title:
      Ref: AWS::StackName
      description: API endpoint for invoking LambdaFunction
      version: 1.0.0
      paths:
      /items:
      post:
      consumes: ["application/json"]
      produces: ["application/json"]
      responses: {}
      x-amazon-apigateway-integration:
      type: "aws_proxy"
      uri:
      Fn::Sub: arn:aws:apigateway:${AWS::Region}:lambda:path/2015-03-31/functions/${LambdaFunction.Arn}/invocations
      passthroughBehavior: "when_no_match"
      httpMethod: "POST"
      requestParameters:
      integration.request.header.X-Amz-Invocation-Type: "'Event'"


      The problem is that lambda is returning empty response(invoked async) so API Gateway is throwing following error



      Wed Nov 14 08:03:14 UTC 2018 : Execution failed due to configuration error: Malformed Lambda proxy response
      Wed Nov 14 08:03:14 UTC 2018 : Method completed with status: 502



      Is this behaviour expected? Do I have to define responses explicitly? I do not want to throw 200 always because I also want to send bad request and unauthorized errors as well.What's the solution to avoid this problem?







      amazon-web-services aws-lambda aws-api-gateway aws-sam






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 14 '18 at 8:07









      himanshu219himanshu219

      859




      859
























          1 Answer
          1






          active

          oldest

          votes


















          0














          The SAM template is deploying an API with Lambda proxy integration, it won't be possible to invoke a proxy integrated Lambda asynchronously as the response will be empty which is not in the valid return format for Lambda proxy integration.



          Hence, to invoke Lambda asynchronously from API Gateway use aws (custom or non proxy) type integration, setting the X-Amz-Invocation-Type: 'Event' header.



          You can also authorize access to your API Gateway to return unauthorized access errors.






          share|improve this answer























            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53295551%2fhow-to-configure-asynchronous-lambda-invocation-via-api-gateway-using-sam%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            The SAM template is deploying an API with Lambda proxy integration, it won't be possible to invoke a proxy integrated Lambda asynchronously as the response will be empty which is not in the valid return format for Lambda proxy integration.



            Hence, to invoke Lambda asynchronously from API Gateway use aws (custom or non proxy) type integration, setting the X-Amz-Invocation-Type: 'Event' header.



            You can also authorize access to your API Gateway to return unauthorized access errors.






            share|improve this answer




























              0














              The SAM template is deploying an API with Lambda proxy integration, it won't be possible to invoke a proxy integrated Lambda asynchronously as the response will be empty which is not in the valid return format for Lambda proxy integration.



              Hence, to invoke Lambda asynchronously from API Gateway use aws (custom or non proxy) type integration, setting the X-Amz-Invocation-Type: 'Event' header.



              You can also authorize access to your API Gateway to return unauthorized access errors.






              share|improve this answer


























                0












                0








                0







                The SAM template is deploying an API with Lambda proxy integration, it won't be possible to invoke a proxy integrated Lambda asynchronously as the response will be empty which is not in the valid return format for Lambda proxy integration.



                Hence, to invoke Lambda asynchronously from API Gateway use aws (custom or non proxy) type integration, setting the X-Amz-Invocation-Type: 'Event' header.



                You can also authorize access to your API Gateway to return unauthorized access errors.






                share|improve this answer













                The SAM template is deploying an API with Lambda proxy integration, it won't be possible to invoke a proxy integrated Lambda asynchronously as the response will be empty which is not in the valid return format for Lambda proxy integration.



                Hence, to invoke Lambda asynchronously from API Gateway use aws (custom or non proxy) type integration, setting the X-Amz-Invocation-Type: 'Event' header.



                You can also authorize access to your API Gateway to return unauthorized access errors.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered 15 hours ago









                Reethi JosephReethi Joseph

                4115




                4115
































                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Stack Overflow!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53295551%2fhow-to-configure-asynchronous-lambda-invocation-via-api-gateway-using-sam%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    The Sandy Post

                    Danny Elfman

                    Pages that link to "Head v. Amoskeag Manufacturing Co."