AWS AWS Lambda Error Codes

The callback ID token has either expired or the callback associated with the token has already been closed.

The maximum number of capacity providers for your account has been exceeded. For more information, see Lambda quotas

The specified code signing configuration does not exist.

Your Amazon Web Services account has exceeded its maximum total code size. For more information, see Lambda quotas.

The code signature failed one or more of the validation checks for signature mismatch or expiry, and the code signing policy is set to ENFORCE. Lambda blocks the deployment.

The durable execution with the specified name has already been started. Each durable execution name must be unique within the function. Use a different name or check the status of the existing execution.

Need additional permissions to configure VPC settings.

Amazon EC2 throttled Lambda during Lambda function initialization using the execution role provided for the function.

Lambda received an unexpected Amazon EC2 client exception while setting up for the Lambda function.

An error occurred when reading from or writing to a connected file system.

The Lambda function couldn't make a network connection to the configured file system.

The Lambda function couldn't mount the configured file system due to a permission or configuration issue.

The Lambda function made a network connection to the configured file system, but the mount operation timed out.

Lambda couldn't create an elastic network interface in the VPC, specified as part of Lambda function configuration, because the limit for network interfaces has been reached. For more information, see Lambda quotas.

The maximum number of function versions that can be associated with a single capacity provider has been exceeded. For more information, see Lambda quotas.

The code signature failed the integrity check. If the integrity check fails, then Lambda blocks deployment, even if the code signing policy is set to WARN.

One of the parameters in the request is not valid.

The request body could not be parsed as JSON, or a request header is invalid. For example, the 'x-amzn-RequestId' header is not a valid UUID string.

The runtime or runtime version specified is not supported.

The security group ID provided in the Lambda function VPC configuration is not valid.

The subnet ID provided in the Lambda function VPC configuration is not valid.

Lambda could not unzip the deployment package.

Lambda couldn't decrypt the environment variables because KMS access was denied. Check the Lambda function's KMS permissions.

Lambda couldn't decrypt the environment variables because the KMS key used is disabled. Check the Lambda function's KMS key settings.

Lambda couldn't decrypt the environment variables because the state of the KMS key used is not valid for Decrypt. Check the function's KMS key settings.

Lambda couldn't decrypt the environment variables because the KMS key was not found. Check the function's KMS key settings.

The function has no published versions available.

The permissions policy for the resource is too large. For more information, see Lambda quotas.

The RevisionId provided does not match the latest RevisionId for the Lambda function or alias. For AddPermission and RemovePermission API operations: Call GetPolicy to retrieve the latest RevisionId for your resource. For all other API operations: Call GetFunction or GetAlias to retrieve the latest RevisionId for your resource.

The specified configuration does not exist.

Lambda has detected your function being invoked in a recursive loop with other Amazon Web Services resources and stopped your function's invocation.

The request payload exceeded the Invoke request body JSON input quota. For more information, see Lambda quotas.

The resource already exists, or another operation is in progress.

The operation conflicts with the resource's availability. For example, you tried to update an event source mapping in the CREATING state, or you tried to delete an event source mapping currently UPDATING.

The resource specified in the request does not exist.

The function is inactive and its VPC connection is no longer available. Wait for the VPC connection to reestablish and try again.

The Lambda function couldn't make a network connection to the configured S3 Files access point.

The Lambda function couldn't mount the configured S3 Files access point due to a permission or configuration issue.

The Lambda function made a network connection to the configured S3 Files access point, but the mount operation timed out.

The request payload exceeded the maximum allowed size for serialized request entities.

The Lambda service encountered an internal error.

The afterRestore() runtime hook encountered an error. For more information, check the Amazon CloudWatch logs.

Lambda is initializing your function. You can invoke the function when the function state becomes Active.

Lambda couldn't restore the snapshot within the timeout limit.

Lambda couldn't set up VPC access for the Lambda function because one or more configured subnets has no available IP addresses.

The request throughput limit was exceeded. For more information, see Lambda quotas.

The content type of the Invoke request body is not JSON.