Home › Forums › AWS › AWS Certified Solutions Architect Associate › Lambda execution period › Reply To: Lambda execution period
-
Hello theodosiostziomakas,
Thank you for posting here. The issue described in the scenario is most likely caused by the execution timeout limit of AWS Lambda, making Option 1 the correct answer. AWS Lambda has a maximum execution timeout of 15 minutes per invocation. When a function exceeds this limit, it is forcibly terminated. Since the application’s Lambda functions process complex financial data and run for approximately 15 minutes, any slight delay in execution would result in termination due to the timeout limit.
Option 2, on the other hand, refers to the concurrent execution limit, which governs the total number of Lambda instances that can run simultaneously. When this limit is reached, new invocations are throttled or rejected, but existing invocations are not affected. This means that the terminated invocations observed in the scenario cannot be attributed to reaching the concurrent execution limit.
The key difference is that the execution timeout terminates invocations exceeding the maximum time limit, while the concurrent execution limit only affects the ability to start new invocations.
Regards,
Nikee @ Tutorials Dojo