You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are adding a feature to change the API limit. programmatically and once the limit is updated we are again starting the Lambda's. For that, we need set the reversed concurrency to unreserved.
permission changes
Visit this policy Lambdas-PutFunctionConcurrency-all-ffb-lamdas
and edit it to as below to add a permission to delete the concurrency of lambda's. and attach this policy to new lambda ResetLimitFunction role
We are deleting the reserved concurrency which is set to 0 so that the lambda's don't serve any requests after that in order to make the lambda's working again we need delete the concurrency so by default it becomes unreserved. for that we need a remission lambda:DeleteFunctionConcurrency
Issue Description
We are adding a feature to change the API limit. programmatically and once the limit is updated we are again starting the Lambda's. For that, we need set the
reversed concurrency
tounreserved
.permission changes
and edit it to as below to add a permission to delete the concurrency of lambda's. and attach this policy to new lambda ResetLimitFunction role
We are deleting the reserved concurrency which is set to 0 so that the lambda's don't serve any requests after that in order to make the lambda's working again we need delete the concurrency so by default it becomes
unreserved
. for that we need a remissionlambda:DeleteFunctionConcurrency
The text was updated successfully, but these errors were encountered: