Lambda Cost Insights
Lambda cost is a multiplication problem: memory size × execution duration × invocation count, plus a small per-request fee and a flat surcharge for every Provisioned Concurrency unit you keep warm. CloudPouch Lambda Cost Insights break your AWS Lambda bill down to individual functions and show which of those factors — and which functions — drive the spend.
What it checks
Section titled “What it checks”For every function, CloudPouch shows the cost estimate at regional pricing alongside the configuration that produces it:
- Memory configuration, average duration, and invocation count — the three inputs of the Lambda cost formula.
- Provisioned Concurrency configuration and its surcharge, listed separately so you can see how much of a function’s cost is idle-time insurance.
- Idle Provisioned Concurrency — capacity you pay to keep warm that invocations don’t use.
- Concrete optimization recommendations per function.
Two kinds of rows stay visible on purpose. Functions with no recorded cost are listed rather than hidden — a function that costs nothing usually means a function nobody invokes, which is a cleanup candidate, not a non-event. And small but non-zero spend rows are kept too, because a fleet of “cheap” functions is where Lambda bills quietly grow.
Why this costs money
Section titled “Why this costs money”Standard Lambda billing is genuinely pay-per-use: no invocations, no compute and no request charges. The exception is Provisioned Concurrency, which bills for every GB-second you keep initialized, around the clock, whether or not requests arrive. A function that needed warm capacity for a launch event and never had it removed keeps billing months later at zero invocations. Memory over-allocation compounds the rest: duration cost scales linearly with the memory setting, so a 1024 MB function that would run fine at 256 MB pays roughly four times more per millisecond than it needs to.
When to use it
Section titled “When to use it”The best trigger is the end of a traffic peak: Provisioned Concurrency added for a launch event or seasonal spike rarely gets scaled back down, and this insight shows exactly which functions are still paying for it. It also pays off when Lambda spend rises without an obvious traffic change, and as a periodic sweep for abandoned functions.
Required AWS permissions
Section titled “Required AWS permissions”CloudPouch needs read access to Lambda function configuration, usage metrics, and cost data. See AWS permissions.