AWS Lambda: async C# handler

Multi tool use
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
add a comment |
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
@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
add a comment |
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
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
c# amazon-web-services aws-lambda
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
add a comment |
@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
add a comment |
2 Answers
2
active
oldest
votes
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/
add a comment |
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
add a comment |
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
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
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
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/
add a comment |
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/
add a comment |
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/
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/
answered Dec 28 '18 at 12:15
iikkoo
1,32852228
1,32852228
add a comment |
add a comment |
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
add a comment |
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
add a comment |
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
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
answered Jan 4 at 3:33
qkhanhpro
726411
726411
add a comment |
add a comment |
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.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
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
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
@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