Lambda invocations increased 61% from PDF processing workload
Current impact
$1,900
vs baseline
Forecasted impact / mo
$2,900
if trend continues
Change vs baseline
+61.0%
Lambda Invocations
Confidence
69%
likely cause attribution
Event Context
Usage Timeline — Lambda Invocations
Actual vs 7-day rolling baseline
Usage Metric Breakdown
Current vs baseline — all contributing metrics
Invocations
72k
Baseline: 45k
+61%
Avg Duration
3k
Baseline: 2k
+19%
GB-seconds
198k
Baseline: 104k
+92%
Error Rate
1.2
Baseline: 0.8
+50%
Root Cause Analysis
1 confirmed · 1 needs confirmation
pdf-processor Lambda invocations: 820/day → 1,320/day (+61%)
Invocation timestamps shifted from irregular to uniform 15-min intervals from Apr 22.
Interpreted as: Consistent with a scheduled batch job being added or reconfigured. Verify via AWS CloudTrail EventBridge rule changes.
Was an EventBridge schedule or batch job config changed on Apr 22? Check CloudTrail.
Likely cause
Batch job frequency or volume changed in PDF processing pipeline
69% confidence · 1 signal awaiting confirmation
Connect a deployment webhook to auto-correlate releases with future spend events.
Suggested Next Steps
Owner: Platform Engineering
Review pdf-processor Lambda event source and batch schedule config
Check if document volume changed or batch size was adjusted
Confirm with Platform Engineering if this is an intended change
Consider Lambda reserved concurrency limit to control burst cost
Related dimensions