🛡️ AWS Lambda Function has low invocation activity🟢

• Contextual name: 🛡️ Function has low invocation activity🟢
• ID: /ce/ca/aws/lambda/function-low-invocation-activity
• Tags:
  • 🟢 Policy with categories
  • 🟢 Policy with type
  • 🟢 Production policy
• Policy Type: BEST_PRACTICE
• Policy Categories: COST

Stats

not available

Logic

• 🧠 prod.logic.yaml🟢
  • 📗 AWS Lambda Function
  • 🔌 AWS Lambda Function - object.extracts.yaml
  • 🧪 test-data.json

Description

Open File

Description

This policy identifies AWS Lambda functions with fewer than 10 invocations over the last 14 days for an ownership and continued-necessity review. It includes functions with no invocations, treating a null 2-Week Invocation Count as zero under the established CMDB data contract. Functions with at least 10 recorded execution errors or throttled requests in the same period are excluded because these counters demonstrate activity that requires troubleshooting rather than an inactivity review.

Rationale

Low or absent invocation activity can reveal obsolete deployments, unnecessary permissions, and unused integrations. One review covers both idle functions and functions that execute only occasionally, since both require the same ownership and dependency assessment.

The threshold of fewer than 10 invocations over 14 days is a review heuristic, not an AWS service limit or a capacity recommendation. It does not establish oversized memory or significant compute waste. A function with no executions does not incur request or execution charges; savings may come from separately billed resources, such as provisioned concurrency or retained logs.

... see more

Remediation

Open File

Remediation

1. Identify the function owner and confirm the expected invocation frequency. Review invocation history, schedules, event source mappings, triggers, aliases, function URLs, resource policies, and upstream dependencies. Use the CMDB application and owner information when available.
2. Compare the finding with the AWS/Lambda Invocations metric in CloudWatch using the Sum statistic over the same 14-day period. Use the function-level dimension covering all versions and aliases in the correct account and Region. For Lambda@Edge, review the Regions where replicas execute. The CMDB represents no invocation activity as a null count.
3. Extend the review beyond 14 days when weekly, monthly, seasonal, recovery, or standby use is expected. If the function is intentionally infrequent, record its business justification and use the organization's policy exception process. Review recorded execution errors and throttled requests before retiring a function. Even activity below the exclusion threshold can indicate a failed integration or concurrency issue. Reserved concurrency controls capacity; it is not billed provisioned concurrency and should not be counted as savings.

... see more

policy.yaml

Open File

Linked Framework Sections

Section	Sub Sections	Internal Rules	Policies	Flags	Compliance
💼 Cloudaware Framework → 💼 Waste Reduction			31		no data