aws-local VS docker-lambda

https://github.com/mozey/aws-local

Dev is easy because I can test everything locally, and the resulting code should be portable to any other cloud.

Obviously this approach might not be feasible if you choose to use AWS that do not have equivalent self-hosted options.

https://github.com/dherault/serverless-offline https://github.com/lambci/docker-lambda

Step 2: Push a container from your local machine to ECR. Currently, I use sample python lambda docker from https://github.com/lambci/docker-lambda.git

You can see the following projects for some examples of using this plugin to build a layer. They all leverage Docker and the docker-lambda images to compile for AWS’s Lambda environment on any operating system:

I end up using Lambda a lot so lambci is very useful for local testing: https://github.com/lambci/docker-lambda

There are kind souls in this world who created this: https://github.com/lambci/docker-lambda

If all you need is the ability to run a lambda function's code locally you might interested in docker-lambda[1]. I haven't really used localstack or SAM but a couple of years ago when we needed to run some lambda functions locally for development docker-lambda worked well enough.

[1] https://github.com/lambci/docker-lambda

Docker Lambda — Docker Lambda is a tool which tries to replicate the AWS Lambda environment as closely as possible, but within a Docker container. Docker Lambda has support for most of the AWS Lambda run times.

Want to emulate AWS environments? Try docker-lambda.