Provision Concurrency not keeping AWS Lambda function warm and it still has initialization time

Question

I was trying to set up lambda with provisioned concurrency. I enabled this feature for the latest version of my lambda function.

After that, i ran this function and watched logs in AWS X-RAY. I saw that my function, still has initialization, but it should become warm with provisioned concurrency.

Without latency, after first start, i ran it twice and it became warm as expected (because it is a default behaviour when lambda became warm after first start without provisioned concurrency).

I waited 15 minutes and was trying to start my lambda again and still it still has initialization time in the logs. It doesn't become warm with provisioned concurrency as expected and always has initialization time.

How can i resolve it?

Waadt

Was this a docker container deployment, zip archive, or inline code lambda? Also just because the initialization time is showing, doesn't mean that the lambda wasn't warm, does it? What is the observed response time, when making an API call directly to the Lambda/Invoke API? – Lyte

When the function was invoked, was it invoked with the version/qualifier for which provisioned concurrency was set, or with $LATEST? – Unarm