- Newest
- Most votes
- Most comments
Hello, I managed to identify the problem.
In fact, it is the slack bolt library that receives the request and, by default, forwards the request from the api to the main function, without informing the Alias, which is why I was invoking $LATEST.
I have already informed the API developers and they are checking for possible updates.
Hello,
Just to confirm, provisioned Concurrency is not supported on the unpublished version of the function ($LATEST). It must be a different version of the function, or on an alias. For your case, you can create an ALIAS, and enable PC on that alias.
If that's already done, edit the Lambda function ARN in the APIGW configuration. Ensure that the field is not pointing to $LATEST. Instead, use the full function ARN, including the ALIAS (e.g., arn:aws:lambda:regions:account:function:FUNCTION-NAME:ALIAS-NAME)
Relevant content
- Accepted Answerasked 5 months ago
- Accepted Answerasked 2 years ago
- Accepted Answerasked 10 months ago
- asked 3 months ago
- AWS OFFICIALUpdated 2 years ago