Permissions, Triggers, Asynchronous invocations present in $LATEST version but not in alias or published version

Question

We created a lambda function with dynamo db and s3 permissions, apigw triggers. These configurations are present in the $LATEST version. Recently we are facing the cold start issues, we are trying to use provisioned concurrency. The provisioned concurrency needs a published version. When we publish the version, it is not having all the configuration that is present in $LATEST version.

How do we retain those configurations when we publish ? We use CDK to create the lambda function, it will be helpful if any leads on retain the configurations in published version of lambda using CDK.

How do we retain those configurations when we publish ?
We use CDK to create the lambda function, it will be helpful if any leads on retain the configurations in published version of lambda using CDK.

Accepted Answer

Triggers and Permissions and Function urls are not getting moved to alias automatically. After debugging it looks like we need to set the Triggers and Permissions and Function urls needs to set separately to alias via cdk code.

The execution role is reused between alias and $LATEST lambda function.

Answer

Can you expand a little more on what configuration you are not seeing present?  Does your CDK code contain the configurations needed and how are you publishing the stack?

Permissions, Triggers, Asynchronous invocations present in $LATEST version but not in alias or published version

Relevanter Inhalt