Menu
I am studying Lambdas of my project and I've seen that one of them is idle. In the top of dashboard page I see block with text:
The function __ is idle. To reactivate your function, choose Restore.
I slightly confused of it because this function is very similar to others which isn't marked as idle but as well haven't been launched for couple of months. Since I haven't find answers in AWS documentation i'd appreciate somebody to explain me what difference between functions in idle state and not, and how/why function becomes Idle?
420
There are three reasons why retry and timeout issues occur when invoking a Lambda function with an AWS SDK: A remote API is unreachable or takes too long to respond to an API call. The API call doesn't get a response within the socket timeout.
First, open up the AWS console (and yes, there is a way to do this via CLI) and go to CloudWatch. From there, go to Events and click Create rule . Set the event type to Schedule , and run this event every 1 minute. Then select the Lambda function you want to target from the Targets list and save.
A cold start occurs when the container is shut down and then has to be restarted when the lambda function is invoked, typically this happens after ~5 mins of inactivity.
It is related to VPC, please check this doc.
If your functions aren't active for a long period of time, Lambda reclaims its network interfaces, and the functions become Idle. To reactivate an idle function, invoke it. This invocation fails, and the function enters a Pending state again until a network interface is available.
https://docs.aws.amazon.com/lambda/latest/dg/configuration-vpc.html
91
Instead of a Cloudwatch event, I would suggest using Provisioned Concurrency to keep a lambda(s) warm.
https://aws.amazon.com/about-aws/whats-new/2019/12/aws-lambda-announces-provisioned-concurrency/
42
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
