AWS Resource Type:
AWS Lambda
Opportunity Description:
This Finder detects AWS Lambda functions with provisioned concurrency configured but no invocation activity over a specified period (default: 30 days). Provisioned concurrency is a powerful feature for minimizing cold starts, but it incurs continuous charges—whether your function is invoked or not.
Many organizations leave provisioned concurrency enabled on test, deprecated, or migrated functions, unknowingly racking up unnecessary costs. This Finder helps eliminate that waste by surfacing unused provisioned capacity for cleanup.
Criteria for identifying the opportunity:
-
The Lambda function exists and is in an
ACTIVE
state. -
Provisioned concurrency is configured on a specific function alias or version.
-
The function has had zero (or minimal) invocations during the lookback period (default: 30 days).
-
The total cost of the provisioned concurrency is greater than zero.
-
The function is not tagged with
cloudfix_dont_fix_it
.
Potential Savings (Annual Estimate):
Provisioned concurrency is billed per GB-second, per hour. Deleting unused configurations can recover 100% of associated provisioned capacity costs, which may range from a few dollars to thousands annually—especially for high-memory functions or those with multiple concurrent units.
The Finder uses annualized cost data from the AWS Cost and Usage Report (CUR) to estimate savings per function.
What happens when the Fixer is executed?
This Finder does not have an automated fixer at this time. It generates a recommendation report detailing the Lambda function’s configuration, usage metrics, and estimated annual savings. You can use this report to manually remove the provisioned concurrency from the AWS Console or via the Lambda API.
Is it possible to roll back once CloudFix implements the Fixer?
Not applicable. Since this is a recommendation-only Finder, CloudFix does not perform any changes automatically.
Can CloudFix implement the fix automatically once I accept the recommendation?
No. This opportunity is currently a manual process. Fixes must be applied by your team based on the report.
Does the fix require downtime?
No. Removing provisioned concurrency does not affect availability but may increase cold start latency if the function is invoked again in the future.
Bill Gleeson
Comments