AWS Lambda supports additional concurrency metric for improved quota monitoring
AWS Lambda now offers additional concurrency metric, ClaimedAccountConcurrency, that reports the sum of used unreserved concurrency, allocated reserved concurrency and provisioned concurrency. With this launch, AWS Lambda customers can now track the amount of overall concurrency in their account that is available for on-demand executions.
AWS Lambda now offers additional concurrency metric, ClaimedAccountConcurrency, that reports the sum of used unreserved concurrency, allocated reserved concurrency and provisioned concurrency. With this launch, AWS Lambda customers can now track the amount of overall concurrency in their account that is available for on-demand executions.
Previously, AWS Lambda customers who enabled reserved concurrency and provisioned concurrency had limited visibility to monitor when they are approaching their account limit because the existing concurrency metric, ConcurrentExecutions, only reflects the amount of concurrent executions at a point in time and disregards reserved concurrency and provisioned concurrency allocation. Customers can now use ClaimedAccountConcurrency metric to track their overall account concurrency availability and use this metric to set alarms on when their account concurrency is approaching the account limit.
This metric is now available on Amazon CloudWatch in all AWS Regions, including the AWS GovCloud (US) Regions. To learn more about ClaimedAccountConcurrency metric, visit Monitoring Concurrency documentation page.