# Unnecessary Lambda provisioned concurrency on low-utilization functions Canonical: https://www.pointfive.co/efficiency-hub/inefficiencies/unnecessary-lambda-provisioned-concurrency-on-low-utilization-functions Provisioned Concurrency is enabled for Lambda functions that do not require consistently low latency or steady traffic. By: Kevin Talbierz Updated: 2026-09-28 [Cloud Efficiency Hub](https://www.pointfive.co/efficiency-hub) # Unnecessary Lambda Provisioned Concurrency on Low-Utilization Functions The short version Provisioned Concurrency is enabled for Lambda functions that do not require consistently low latency or steady traffic. [Kevin Talbierz](https://www.linkedin.com/in/kevin-talbierz/) FinOps Manager @ Accor AWS service [AWS Lambda](https://www.pointfive.co/efficiency-hub/cloud-services/aws-lambda) Category [Compute](https://www.pointfive.co/efficiency-hub/service-category/compute) Reference CER-0290 Type Underutilized Commitment ## Explanation Why the waste happens and who it affects. In such cases, provisioned concurrency remains allocated and billed during idle periods, creating ongoing cost without proportional performance or business benefit. This is distinct from standard Lambda execution charges, which are purely usage-based. ## Billing model The pricing dimensions that drive this cost. Lambda Provisioned Concurrency is billed per GB-second, based on configured memory multiplied by the amount of concurrency provisioned, from when it is enabled until it is disabled, rounded up to the nearest 5 minutes. Charges accrue regardless of invocation volume, even when functions are idle. ## How to detect 3 checks to find it in your estate. - Review whether functions with Provisioned Concurrency have sustained or predictable traffic patterns - Assess whether cold-start latency materially impacts user experience or system behavior - Identify functions where provisioned concurrency appears idle for extended periods (for example, using the ProvisionedConcurrencyUtilization metric); reserved concurrency is a separate, free setting ## How to fix 2 ways to remove the waste. - Remove Provisioned Concurrency from functions without strict latency or availability requirements - Reserve Provisioned Concurrency only for workloads with consistent traffic or critical cold-start sensitivity ## Documentation Vendor references for pricing and configuration. [https://docs.aws.amazon.com/lambda/latest/dg/provisioned-concurrency.html](https://docs.aws.amazon.com/lambda/latest/dg/provisioned-concurrency.html) ## Related inefficiencies [Browse the library](https://www.pointfive.co/efficiency-hub) - AWS Lambda CER-0296 ### [Inefficient Lambda Pricing Model for Steady High-Volume Workloads (Use Lambda Managed Instances)](https://www.pointfive.co/efficiency-hub/inefficiencies/inefficient-lambda-pricing-for-steady-high-volume-workloads-use-lambda-managed-instances) A function has steady, high-volume traffic (or predictable load) but continues running on default Lambda pricing, where costs scale with execution duration. Lambda Managed Instances runs Lambda on EC2 capacity managed by Lambda and... Compute - AWS Lambda CER-0209 ### [Unnecessary Costs from Unused Lambda Versions with SnapStart](https://www.pointfive.co/efficiency-hub/inefficiencies/unnecessary-costs-from-unused-lambda-versions-with-snapstart) Many teams publish new Lambda versions frequently (e.g., through CI/CD pipelines) but do not clean up old ones. When SnapStart is enabled on Python or .NET functions, each of these versions retains a cached snapshot, generating ongoing... Compute - AWS Lambda CER-0204 ### [Inefficient SnapStart Configuration in Lambda](https://www.pointfive.co/efficiency-hub/inefficiencies/inefficient-snapstart-configuration-in-lambda) SnapStart reduces cold-start latency, but when configured inefficiently, it can increase costs. For Python and .NET functions, high-traffic workloads can trigger frequent snapshot restorations, multiplying costs. Slow initialization code... Compute --- Source: the public page above. Product screenshots and illustrative interfaces are examples, not live customer data.