Lambda function should have a reasonable timeout configured
Low
AWS
General
aws-lambda-function-lambda-function-reasonable-tim
Applies to
AWS::Lambda::Function
What CGPulse checks
A resource passes this rule when timeout must be less than 900. Anything else is reported as a finding with the evaluated property value attached as evidence.
How to fix it
Review Lambda timeout settings to prevent excessive costs during failures. In AWS Console: Lambda > Functions > Configuration > General > Timeout. See: https://docs.aws.amazon.com/lambda/latest/dg/configuration-function-common.html
Terraform
resource "aws_lambda_function" "{name}" {
timeout = 30 # Set appropriate timeout
}
Compliance frameworks
Is your environment compliant with this rule?
CGPulse checks it — and 621 others — against your Azure and AWS accounts with read-only access.
Related AWS rules
- ACM certificate must be eligible for renewal
- ACM certificate must be in issued status
- Amplify app should have basic auth disabled for production
- API Gateway REST API must have an endpoint configuration
- API Gateway V2 API must be properly configured
- App Runner service must have encryption enabled
- AppSync API must have logging configured
- AppSync API must have X-Ray tracing enabled