How to run lambda with external dependencies locally while excluding the dependencies from being packaged and pushed to AWS?

[kayvanmoj]

Your Environment

• OS: macOS 14.2.1 (23C71)
• JetBrains product: 2023.3.2 (Ultimate Edition)
• JetBrains product version: Build #IU-233.13135.103, built on December 20, 2023
• AWS Toolkit version: 3.26-233
• SAM CLI version: 1.122.0
• Python version: 3.12

Question

Hi,

In order to run a lambda function that has external dependencies locally, requirements.txt has to be provided to specify the dependencies.

The issue here is that sam build will package the dependencies with the lambda code that is pushed to AWS. However the dependencies already exist as layers in the AWS environment.

Is there a way to avoid this? Or any other workaround?

I know doing a sam deploy without a sam build will exclude the dependencies from the package. However one problem with that approach is that the run executor runs sam build before running the function so, before deployment, .aws-sam dir has to be deleted.

Is there a way to specify a different build dir for the run executor build?

Thanks.

[kayvanmoj]

My current hack:

deploy.sh

rm -rf .aws-sam
sam deploy --profile $1