Invokes a Lambda function.
Need additional permissions to configure VPC settings.
AWS Lambda was throttled by Amazon EC2 during Lambda function initialization using the execution role provided for the Lambda function.
AWS Lambda received an unexpected EC2 client exception while setting up for the Lambda function.
AWS Lambda was not able to create an elastic network interface in the VPC, specified as part of Lambda function configuration, because the limit for network interfaces has been reached.
One of the parameters in the request is invalid.
The request body could not be parsed as JSON.
The runtime or runtime version specified is not supported.
The Security Group ID provided in the Lambda function VPC configuration is invalid.
The Subnet ID provided in the Lambda function VPC configuration is invalid.
AWS Lambda could not unzip the deployment package.
Lambda was unable to decrypt the environment variables because KMS access was denied.
Lambda was unable to decrypt the environment variables because the KMS key used is disabled.
Lambda was unable to decrypt the environment variables because the KMS key used is in an invalid state for Decrypt.
Lambda was unable to decrypt the environment variables because the KMS key was not found.
The request payload exceeded the
The resource already exists, or another operation is in progress.
The resource specified in the request does not exist.
The function is inactive and its VPC connection is no longer available.
The AWS Lambda service encountered an internal error.
AWS Lambda was not able to 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.
The content type of the
Copyright © 2018 Amazon Web Services, Inc. All Rights Reserved.