Skip to main content

Triage AWS Lambda Timeout Policy EXCESSIVE_TIMEOUT_EXCEEDED

  1. Configure AWS Lambda Timeout Policy
  2. Use Case for AWS Lambda Timeout Policy
  3. Triage Guides by Violation Type
    1. Triage AWS Lambda Timeout Policy EXCESSIVE_TIMEOUT_EXCEEDED

Triage Guide: Excessive Timeout Exceeded

0) Understand​

Why should I care about fixing this issue?

  • Excessive timeouts can lead to increased execution time, retries, and higher costs.

1) Validate​

How am I sure that this alert is true and accurate?

  • Source: CloudWatch metrics for the Lambda function.
  • Retrieve manually: Use the AWS Console or the AWS CLI to check the Lambda function's timeout configuration and CloudWatch metrics.
  • Schedule: This policy scans daily to detect any violations.

2) Triage​

What is the impact if it is unfixed?

  • Higher costs due to increased execution time and retries.
  • Potential impact on application performance.

Does this problem get worse over time if it is unaddressed?

  • Yes, prolonged excessive timeouts can accumulate significant costs over time.

Can remediation cause outages or downtime to any other running service?

  • Adjusting timeouts or function logic should be carefully tested to avoid unintended impacts.

3) Act​

What do I do to fix this alarm?

  • Review and possibly reduce the function's timeout configuration.
  • Optimize the function's code to reduce execution time.
  • Consider using asynchronous invocation if applicable.

4) Reflect​

What should I do if this alarm wasn't a good use of time?

  • Adjust the timeoutPercentThreshold to better fit your use case.
  • Disable the policy if not relevant to your environment.