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
I was able to get provisioned concurrency working for my lambda using aws.lambda.ProvisionedConcurrencyConfig, however, it seems to work inconsistently. If I comment out the config and then deploy, it successfully removes the provisioned concurrency for this lambda. Then, if I uncomment it and deploy again, sometimes I get FUNCTION_ERROR_INIT_FAILURE. Also, it seems like when I update my lambda handler, I don't always get a new version published when I deploy. For example, I added a console log at the top of my handler, deployed, and under versions my lambda still had version 3 from 2 hours ago after refreshing my AWS console.
ProvisionedConcurrencyName aws:lambda:ProvisionedConcurrencyConfig
creating urn:pulumi:justinschwartz::sst::aws:lambda/provisionedConcurrencyConfig:ProvisionedConcurrencyConfig::ProvisionedConcurrencyName: 1 error occurred:
waiting for Lambda Provisioned Concurrency Config (sst-justinschwartz-APIRoute____HandlerFunction,1) to be ready: status reason: FUNCTION_ERROR_INIT_FAILURE
The text was updated successfully, but these errors were encountered:
I was able to get provisioned concurrency working for my lambda using aws.lambda.ProvisionedConcurrencyConfig, however, it seems to work inconsistently. If I comment out the config and then deploy, it successfully removes the provisioned concurrency for this lambda. Then, if I uncomment it and deploy again, sometimes I get FUNCTION_ERROR_INIT_FAILURE. Also, it seems like when I update my lambda handler, I don't always get a new version published when I deploy. For example, I added a console log at the top of my handler, deployed, and under versions my lambda still had version 3 from 2 hours ago after refreshing my AWS console.
The text was updated successfully, but these errors were encountered: