AWS Lambda: fork/exec /var/task/demo: exec format error: PathError null

2 min read

Executing a lambda function we might find that if fails with the following error:

2023-02-04T21:15:33.723+01:00 START RequestId: 7cb12d0d-1e8c-4a8d-485a-0f5dced9a545 Version: $LATEST
2023-02-04T21:15:33.723+01:00 fork/exec /var/task/demo: exec format error: PathError null
2023-02-04T21:15:33.724+01:00 END RequestId: 7cb12d0d-1e8c-4a8d-485a-0f5dced9a545

13/02/2023

Lambda functions: Allow lambda function to use VPC

2 min read

Lambda functions sometimes might need to interact with other AWS services that depending on how we are configuring it might need some explicit permissions to be set.

06/02/2023

Deploy a lambda function using terraform

4 min read

To be able to deploy a lambda function there are several pieces that need to be deployed:

• IAM roles: It might need to access to the AWS API, so we need to create an IAM role to control it's privileges
• Triggering: We might want the function to get triggered with some event (that's what we are going to do on this post) or a load balancer
• Code: What we want to execute
• Lambda function itself

05/05/2022

terraform: Update a Lambda function when the code changes

2 min read

If we are using the archive_file datasource to zip some Lambda function to be able to push it to AWS, we need to se the source_code_hash with it's hash to make sure the function gets updated when it changes:

01/04/2022