feat: added lambda layer

LocalStack/README.md

@@ -1,4 +1,7 @@
 # LocalStack
+It's a fair tool to test terraform code without actually deploying anything on aws.
+However, there are a few limitations on LocalStack.
+
 ## Setup
 Sign up for localstack and obtain the auth token. Then fire up a container:
 
@@ -13,8 +16,7 @@ docker run \
 -e AWS_ACCESS_KEY_ID=test \
 -e AWS_SECRET_ACCESS_KEY=test \
 -e SERVICES="s3,iam,lambda,dynamodb,cloudwatch,rds,ec2,secretsmanager" \
--e DEBUG=1 \
--v /run/containerd/containerd.sock:/var/run/docker.sock \
+-e DEBUG=0 \
 -d --rm --name localstack --network macvlan localstack/localstack localstack 
 ```
 
@@ -73,9 +75,18 @@ For example, vpc with ipv6 could not be created. It failed with the following er
 
 ```
 
-Also, ec2 instance's associate_public_ip_address attribute is always set to true, despite
+Also, ec2 instance's ```associate_public_ip_address``` attribute is always set to true, despite
 it is set to false in my code. This caused the instance to be redeployed everytime terraform
 apply is ran.
 
+If I tried to deploy a lambda function, LocalStack actually tried to create an executable container
+via docker. That cannot be disabled and without docker, I got this error when trying to deploy a function.
+Subsequently, I cannot destroy the function since provisioning failed.
+
+```text
+Error: waiting for Lambda Function (HelloWorldFunction) create: unexpected state 'Failed', wanted target 
+'Active, ActiveNonInvocable'. last error: InternalError: Error while creating lambda: Docker not available
+```
+
 Both the free and community editions of LocalStack do not support rds, among other services described in
 https://docs.localstack.cloud/aws/licensing/