revamp aws-lambda-proxy

[andreineculau]

to be http-agnostic and allow debugging any lambda triggered by any service

gist of v1 UX:

$ aws-lambda-proxy \
  --function-name <value> \
  --ip <value> \
  --port <value> \
  [--listen | --no-listen]

$ cd path/to/aws/lambda/code
$ aws-lambda-proxy-listen \
  --runtime <value> \
  --ip <value> \
  --port <value> \

at this point all calls to your lambda inside the AWS walls will proxy everythint (event, context, process.env, smth else?) to your local server started by aws-lambda-proxy-listen that will call the main function on each request

v1 can be as simple as that, supporting nodejs only. future versions could

• integrate with ngrok, in order to bypass NATs
• implement a unique auth token so that the local server cannot be called without it
• assume lambda roles, in order to simulate even closer the lambda runtime constraints
• ?

// cc Tobias Lindgren (@tobiiasl)