C# Lambda constructor not called in consecutive lambda calls

Question

I have a c# aws lambda class with some code in its constructor. The lambda method itself is getting called every time I initiate it (with an SNS message post), however, I cannot see the constructor getting called (added log calls to observe from cloudwatch). The constructor only gets called at first launch (after the aws stack creation/update).

Is this an expected behaviour? Does aws somehow cache my lambda instances?

public class MyLambda
{
     public MyLambda()
     {
          Console.WriteLine("Hello from ctor");
     }

     // This is the method assigned in CloudFormation
     public bool Execute(SNSEvent snsEvent)
     {          
          Console.WriteLine("Lambda called");
          return true;
     }
}

And here is the outcome in cloudwatch log; First time initiate Lambda:

Hello from ctor
Lambda called

And second time initiation of Lambda

Lambda called

Answer 1

AWS reuses the instances as described in this blog post, in the FAQ and the official documentation.

In general the instances are reused and replaced every now and then. If you have a higher load AWS will create more concurrent instances. So usually it's very likely that your instances get reused, but you cannot count on it as they get recycled. When the instance is reused than the constructor won't be called again as the constructor was already called during the initialization.

Usually the first call to a new instance is quite slow, as the run-time does initialization like loading itself, class loading, etc and calling the constructor. The subsequent calls are usually much faster as the Lambda is already fully initialized. However, if you haven't called your Lambda for a while it needs some warm-up from its "freeze" as well. This still constitutes a reuse, so the constructor won't be called again.