- Le plus récent
- Le plus de votes
- La plupart des commentaires
Lambda provisioned concurrency can be reserved up to 100 less than the number of unreserved account concurrencies. [1]
[1] Managing Lambda reserved concurrency - AWS Lambda
https://docs.aws.amazon.com/lambda/latest/dg/configuration-concurrency.html
Therefore, to set the provisioned concurrency to 3, the account concurrency must be greater than 103.
The concurrency limit can be requested via service quotas. [2]
[2] AWS service quotas - AWS General Reference
https://docs.aws.amazon.com/general/latest/gr/aws_service_limits.html
You have to leave a minimum of 100 for lambda functions in an account that don't have reserved concurrency - https://docs.aws.amazon.com/lambda/latest/dg/configuration-concurrency.html that mentions "You can reserve up to the Unreserved account concurrency value that is shown, minus 100 for functions that don't have reserved concurrency."
You have to request an increase in the account concurrency to a number higher than 100, so you can set reserved concurrency for certain lambda functions in your account.
Contenus pertinents
- demandé il y a 6 mois
- demandé il y a un an
- demandé il y a un an
- AWS OFFICIELA mis à jour il y a 2 ans
Provisioned concurrency and reserved concurrency are different things. I believe you intended to say Reserved Concurrency and not Provisioned Concurrency