There is an issue where you can’t update provisioned concurrency when deploying a new lamba version and doing a routingStage.
The issue is occurring because routing the weights takes some time to complete and while the weights are distributed between two versions requesting to update provisioned concurrency is prevented by AWS.
The solution was to validate that the weights are fully moved after executing LambdaTrafficUpdateTask and before executing LambdaPutConcurrencyTask.
Doing a LambdaTrafficUpdate with $WEIGHTED Strategy remains the same
There is an issue where you can’t update provisioned concurrency when deploying a new lamba version and doing a routingStage.
The issue is occurring because routing the weights takes some time to complete and while the weights are distributed between two versions requesting to update provisioned concurrency is prevented by AWS. The solution was to validate that the weights are fully moved after executing LambdaTrafficUpdateTask and before executing LambdaPutConcurrencyTask.
Doing a LambdaTrafficUpdate with $WEIGHTED Strategy remains the same