Lambda integration timeout shape (timeout config sanity)
What it checks
Lambda integration timeout shape (timeout config sanity)
Where it applies
Terraform: aws_lambda_function
CloudFormation: AWS::Lambda::Function
How to fix it
- If a REST API integration at the 29-second default (an edge-optimized API cannot exceed it) or an HTTP API integration (30-second maximum) invokes this function: keep the function timeout below the integration timeout, and move long work to Step Functions or SQS, returning 202 with a correlation ID.
- If it is a Regional or private REST API: either lower the function timeout to what the integration allows, or raise the integration timeout_milliseconds above 29,000: up to 300,000 ms for buffered responses (response_transfer_mode BUFFERED; a Service Quotas request that might lower your account throttle quota) or 900,000 ms with response streaming (response_transfer_mode STREAM).
- If no API Gateway API invokes this function: this threshold does not apply; Lambda's own maximum is 900 seconds (15 minutes).
Frameworks
- AWS Well-Architected REL.5
These mappings are advisory, not an attestation of compliance.