AWS Lambda: async C# handler

Multi tool use
Multi tool use












1














The AWS document states that




Using Async in C# Functions with AWS Lambda



If you know your Lambda function will require a long-running process,
such as uploading large files to Amazon S3 or reading a large stream
of records from DynamoDB, you can take advantage of the async/await
pattern. By creating a handler with this signature, Lambda will
execute the function synchronously and wait a maximum of 5 minutes for
execution to complete before returning or timing out.




I feel very confused Lambda will




execute the function synchronously and wait a maximum of 5 minutes




When Lambda support up to 15 minutes of processing time.
Does that mean if I put async on the handler, I can only process one event in 5 minutes?










share|improve this question
























  • @TheGeneral Thanks. I removed the broad part and would ask the AWS support instead. I do have some basic understanding about async in .NET and used both async/non async in Lambda integration. I will create an answer if I can get a definitive one from AWS support
    – qkhanhpro
    Dec 28 '18 at 3:44






  • 1




    This to me was an interesting question I have a feeling the documentation has not been updated and should read: "By creating a handler with this signature, Lambda will execute the function synchronously and wait a maximum of 15 minutes for execution to complete before returning or timing out."
    – David Webster
    Dec 28 '18 at 13:02
















1














The AWS document states that




Using Async in C# Functions with AWS Lambda



If you know your Lambda function will require a long-running process,
such as uploading large files to Amazon S3 or reading a large stream
of records from DynamoDB, you can take advantage of the async/await
pattern. By creating a handler with this signature, Lambda will
execute the function synchronously and wait a maximum of 5 minutes for
execution to complete before returning or timing out.




I feel very confused Lambda will




execute the function synchronously and wait a maximum of 5 minutes




When Lambda support up to 15 minutes of processing time.
Does that mean if I put async on the handler, I can only process one event in 5 minutes?










share|improve this question
























  • @TheGeneral Thanks. I removed the broad part and would ask the AWS support instead. I do have some basic understanding about async in .NET and used both async/non async in Lambda integration. I will create an answer if I can get a definitive one from AWS support
    – qkhanhpro
    Dec 28 '18 at 3:44






  • 1




    This to me was an interesting question I have a feeling the documentation has not been updated and should read: "By creating a handler with this signature, Lambda will execute the function synchronously and wait a maximum of 15 minutes for execution to complete before returning or timing out."
    – David Webster
    Dec 28 '18 at 13:02














1












1








1







The AWS document states that




Using Async in C# Functions with AWS Lambda



If you know your Lambda function will require a long-running process,
such as uploading large files to Amazon S3 or reading a large stream
of records from DynamoDB, you can take advantage of the async/await
pattern. By creating a handler with this signature, Lambda will
execute the function synchronously and wait a maximum of 5 minutes for
execution to complete before returning or timing out.




I feel very confused Lambda will




execute the function synchronously and wait a maximum of 5 minutes




When Lambda support up to 15 minutes of processing time.
Does that mean if I put async on the handler, I can only process one event in 5 minutes?










share|improve this question















The AWS document states that




Using Async in C# Functions with AWS Lambda



If you know your Lambda function will require a long-running process,
such as uploading large files to Amazon S3 or reading a large stream
of records from DynamoDB, you can take advantage of the async/await
pattern. By creating a handler with this signature, Lambda will
execute the function synchronously and wait a maximum of 5 minutes for
execution to complete before returning or timing out.




I feel very confused Lambda will




execute the function synchronously and wait a maximum of 5 minutes




When Lambda support up to 15 minutes of processing time.
Does that mean if I put async on the handler, I can only process one event in 5 minutes?







c# amazon-web-services aws-lambda






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Dec 28 '18 at 3:41

























asked Dec 28 '18 at 3:21









qkhanhpro

726411




726411












  • @TheGeneral Thanks. I removed the broad part and would ask the AWS support instead. I do have some basic understanding about async in .NET and used both async/non async in Lambda integration. I will create an answer if I can get a definitive one from AWS support
    – qkhanhpro
    Dec 28 '18 at 3:44






  • 1




    This to me was an interesting question I have a feeling the documentation has not been updated and should read: "By creating a handler with this signature, Lambda will execute the function synchronously and wait a maximum of 15 minutes for execution to complete before returning or timing out."
    – David Webster
    Dec 28 '18 at 13:02


















  • @TheGeneral Thanks. I removed the broad part and would ask the AWS support instead. I do have some basic understanding about async in .NET and used both async/non async in Lambda integration. I will create an answer if I can get a definitive one from AWS support
    – qkhanhpro
    Dec 28 '18 at 3:44






  • 1




    This to me was an interesting question I have a feeling the documentation has not been updated and should read: "By creating a handler with this signature, Lambda will execute the function synchronously and wait a maximum of 15 minutes for execution to complete before returning or timing out."
    – David Webster
    Dec 28 '18 at 13:02
















@TheGeneral Thanks. I removed the broad part and would ask the AWS support instead. I do have some basic understanding about async in .NET and used both async/non async in Lambda integration. I will create an answer if I can get a definitive one from AWS support
– qkhanhpro
Dec 28 '18 at 3:44




@TheGeneral Thanks. I removed the broad part and would ask the AWS support instead. I do have some basic understanding about async in .NET and used both async/non async in Lambda integration. I will create an answer if I can get a definitive one from AWS support
– qkhanhpro
Dec 28 '18 at 3:44




1




1




This to me was an interesting question I have a feeling the documentation has not been updated and should read: "By creating a handler with this signature, Lambda will execute the function synchronously and wait a maximum of 15 minutes for execution to complete before returning or timing out."
– David Webster
Dec 28 '18 at 13:02




This to me was an interesting question I have a feeling the documentation has not been updated and should read: "By creating a handler with this signature, Lambda will execute the function synchronously and wait a maximum of 15 minutes for execution to complete before returning or timing out."
– David Webster
Dec 28 '18 at 13:02












2 Answers
2






active

oldest

votes


















0














AWS recently changed the timeout for Lamdba. The execution timeout is changed from 5 minutes to 15 minutes.



https://aws.amazon.com/about-aws/whats-new/2018/10/aws-lambda-supports-functions-that-can-run-up-to-15-minutes/






share|improve this answer





























    0














    The final answer of AWS support at the time:




    • The document was not up to date. It should run at maximum 15 minute timeout ( depend on the Lambda function configuration )

    • The async modifier does not change how AWS behave, they will just await it.

    • The behaviour diference is only on the .NET side






    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%2f53953309%2faws-lambda-async-c-sharp-handler%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      2 Answers
      2






      active

      oldest

      votes








      2 Answers
      2






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      0














      AWS recently changed the timeout for Lamdba. The execution timeout is changed from 5 minutes to 15 minutes.



      https://aws.amazon.com/about-aws/whats-new/2018/10/aws-lambda-supports-functions-that-can-run-up-to-15-minutes/






      share|improve this answer


























        0














        AWS recently changed the timeout for Lamdba. The execution timeout is changed from 5 minutes to 15 minutes.



        https://aws.amazon.com/about-aws/whats-new/2018/10/aws-lambda-supports-functions-that-can-run-up-to-15-minutes/






        share|improve this answer
























          0












          0








          0






          AWS recently changed the timeout for Lamdba. The execution timeout is changed from 5 minutes to 15 minutes.



          https://aws.amazon.com/about-aws/whats-new/2018/10/aws-lambda-supports-functions-that-can-run-up-to-15-minutes/






          share|improve this answer












          AWS recently changed the timeout for Lamdba. The execution timeout is changed from 5 minutes to 15 minutes.



          https://aws.amazon.com/about-aws/whats-new/2018/10/aws-lambda-supports-functions-that-can-run-up-to-15-minutes/







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Dec 28 '18 at 12:15









          iikkoo

          1,32852228




          1,32852228

























              0














              The final answer of AWS support at the time:




              • The document was not up to date. It should run at maximum 15 minute timeout ( depend on the Lambda function configuration )

              • The async modifier does not change how AWS behave, they will just await it.

              • The behaviour diference is only on the .NET side






              share|improve this answer


























                0














                The final answer of AWS support at the time:




                • The document was not up to date. It should run at maximum 15 minute timeout ( depend on the Lambda function configuration )

                • The async modifier does not change how AWS behave, they will just await it.

                • The behaviour diference is only on the .NET side






                share|improve this answer
























                  0












                  0








                  0






                  The final answer of AWS support at the time:




                  • The document was not up to date. It should run at maximum 15 minute timeout ( depend on the Lambda function configuration )

                  • The async modifier does not change how AWS behave, they will just await it.

                  • The behaviour diference is only on the .NET side






                  share|improve this answer












                  The final answer of AWS support at the time:




                  • The document was not up to date. It should run at maximum 15 minute timeout ( depend on the Lambda function configuration )

                  • The async modifier does not change how AWS behave, they will just await it.

                  • The behaviour diference is only on the .NET side







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Jan 4 at 3:33









                  qkhanhpro

                  726411




                  726411






























                      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.





                      Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                      Please pay close attention to the following guidance:


                      • 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%2f53953309%2faws-lambda-async-c-sharp-handler%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







                      OHQw9axv,Le,LMYlGfR,SBo,BSLr 2jhViidyq 0
                      ThikW6ZxJ7Bbw0

                      Popular posts from this blog

                      Monofisismo

                      compose and upload a new article using a custom form

                      “attempting to read past stream EOM” using Sybase.AdoNet4.AseClient