Expand description
Error types that AWS Lambda can respond with.
Modules§
- builders
- Builders
Structs§
- Code
Signing Config NotFound Exception The specified code signing configuration does not exist.
- Code
Storage Exceeded Exception Your Amazon Web Services account has exceeded its maximum total code size. For more information, see Lambda quotas.
- Code
Verification Failed Exception 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.
- Ec2Access
Denied Exception Need additional permissions to configure VPC settings.
- Ec2Throttled
Exception Amazon EC2 throttled Lambda during Lambda function initialization using the execution role provided for the function.
- Ec2Unexpected
Exception Lambda received an unexpected Amazon EC2 client exception while setting up for the Lambda function.
- EfsMount
Connectivity Exception The Lambda function couldn't make a network connection to the configured file system.
- EfsMount
Failure Exception The Lambda function couldn't mount the configured file system due to a permission or configuration issue.
- EfsMount
Timeout Exception The Lambda function made a network connection to the configured file system, but the mount operation timed out.
- Efsio
Exception An error occurred when reading from or writing to a connected file system.
- EniLimit
Reached Exception 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.
- Invalid
Code Signature Exception 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.
- Invalid
Parameter Value Exception One of the parameters in the request is not valid.
- Invalid
Request Content Exception 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.
- Invalid
Runtime Exception The runtime or runtime version specified is not supported.
- Invalid
Security Group IdException The security group ID provided in the Lambda function VPC configuration is not valid.
- Invalid
Subnet IdException The subnet ID provided in the Lambda function VPC configuration is not valid.
- Invalid
ZipFile Exception Lambda could not unzip the deployment package.
- KmsAccess
Denied Exception Lambda couldn't decrypt the environment variables because KMS access was denied. Check the Lambda function's KMS permissions.
- KmsDisabled
Exception Lambda couldn't decrypt the environment variables because the KMS key used is disabled. Check the Lambda function's KMS key settings.
- KmsInvalid
State Exception 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.
- KmsNot
Found Exception Lambda couldn't decrypt the environment variables because the KMS key was not found. Check the function's KMS key settings.
- Policy
Length Exceeded Exception The permissions policy for the resource is too large. For more information, see Lambda quotas.
- Precondition
Failed Exception The RevisionId provided does not match the latest RevisionId for the Lambda function or alias.
-
For AddPermission and RemovePermission API operations: Call
GetPolicyto retrieve the latest RevisionId for your resource. -
For all other API operations: Call
GetFunctionorGetAliasto retrieve the latest RevisionId for your resource.
-
- Provisioned
Concurrency Config NotFound Exception The specified configuration does not exist.
- Recursive
Invocation Exception Lambda has detected your function being invoked in a recursive loop with other Amazon Web Services resources and stopped your function's invocation.
- Request
TooLarge Exception The request payload exceeded the
Invokerequest body JSON input quota. For more information, see Lambda quotas.- Resource
Conflict Exception The resource already exists, or another operation is in progress.
- Resource
InUse Exception 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.
- Resource
NotFound Exception The resource specified in the request does not exist.
- Resource
NotReady Exception The function is inactive and its VPC connection is no longer available. Wait for the VPC connection to reestablish and try again.
- Service
Exception The Lambda service encountered an internal error.
- Snap
Start Exception The
afterRestore()runtime hook encountered an error. For more information, check the Amazon CloudWatch logs.- Snap
Start NotReady Exception Lambda is initializing your function. You can invoke the function when the function state becomes
Active.- Snap
Start Timeout Exception Lambda couldn't restore the snapshot within the timeout limit.
- Subnet
IpAddress Limit Reached Exception Lambda couldn't set up VPC access for the Lambda function because one or more configured subnets has no available IP addresses.
- TooMany
Requests Exception The request throughput limit was exceeded. For more information, see Lambda quotas.
- Unsupported
Media Type Exception The content type of the
Invokerequest body is not JSON.
Enums§
- Invoke
With Response Stream Response Event Error - Error type for the
InvokeWithResponseStreamResponseEventErroroperation.