- Newest
- Most votes
- Most comments
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.
Hello.
Can you share the SAM template with the problem?
I would like to check if there are any problems with the template syntax.
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"
]
}
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.
Relevant content
- asked 2 years ago
- asked 2 years ago
- AWS OFFICIALUpdated 4 years ago
