I added the provisionedConcurrency property to my lambda configuration. The Serverless Framework seems to apply the configuration by version number to the new version of the lambda when deployed. The API Gateway though by default references $Latest instead of the new version number. It seems as though this results in provisioned lambda not being used (cloudwatch metrics indicated its only used when invoking it by version number not $Latest). So how are people addressing this?
Hi rt. The most recent version of the Framework resolves this issue. There was actually a bug in the AWS implementation of provisionedConcurrency that has now been resolved. Can you try out the newest version and see how that goes for you?
1 Like