Skip to content

Lambda function did not stabilize

1

Our AWS stack lambda deployment is failing to deploy due to a "Resource handler returned message: "Resource of type 'AWS::Lambda::Function' with identifier .. did not stabilize." (HandlerErrorCode: NotStabilized)". The problem seems be with just one function in the stack since others update successfully before being rolled back. This is the first time that this happened to us and is strange because the function does work as expected when called with sam local invoke and no logic changes were introduced. I've tried to deploy from two different machines and got the same results and deleting the stack is not an option for us. I have even tried to introduce small ineffectual code changes to the function in question to see if this would resolve the error but the issue remained. Any help is greatly appreciated.

4 Answers
0
Accepted Answer

We were able to identify the issue after attempting to deploy the same code into a new stack. This resulted in a more descriptive InvalidImage(SizeLimitExceeded: Uncompressed container image size exceeds 10 GiB limit) .. failed to stabilize error.

The docker images command was used to confirm the size of the failing function's image, and confirmed that it was indeed 1 GB over the limit.

As a result, we were then able to optimise our image to bring it down below this threshold.

answered 2 years ago
EXPERT
reviewed 2 years ago
0

Hello.

Can you share the SAM template with the problem?
I would like to check if there are any problems with the template syntax.

EXPERT
answered 2 years ago
0

I have attempted validating my SAM template using aws cloudformation validate-template --template-body file:///... but got no errors, output below:

{
    "Parameters": [
        {
            "ParameterKey": "BucketName",
            "NoEcho": false
        },
        {
            "ParameterKey": "SentryDSN",
            "NoEcho": false,
            "Description": "DSN address of the Sentry project"
        },
        {
            "ParameterKey": "QueueName",
            "NoEcho": false,
            "Description": "Results queue name"
        },
        {
            "ParameterKey": "QueueURL",
            "NoEcho": false,
            "Description": "Results queue url"
        }
    ],
    "Description": "Analyzer\n",
    "Capabilities": [
        "CAPABILITY_AUTO_EXPAND"
    ]
}
answered 2 years ago
0

Hello, In my case I was using aws cdk and this happened to me when there were no changes in the docker image (other words when the stack is trying to be updated without making any code changes in the source/ lambda function). In cloudformation template deploys using boto3 it'd look like:

botocore.exceptions.ClientError: An error occurred (ValidationError) when calling the UpdateStack operation: No updates are to be performed.

TLDR; Better to check if there were any changes made at all since the previous deployment.

answered a year ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.