mentum/lambdaws

Deploy, run and get results from Amazon AWS Lambda in a breeze

Austen

@ac360

I'm most interested in building a series of open-source lambda functions for common utilities

EFF

@EFF

We had a similar idea, would be awesome !

Austen

@ac360

Each would be bundled with the lambdaws project.

EFF

@EFF

Yeah !

It’ll help to find new use cases

Raphaël Antonmattei

@rantonmattei

I just installed v1.0.11 with npm, the bin directory seems to be gone

EFF

@EFF

Hi there gone ? let me check

EFF

@EFF

Everything seems fine on my side @rantonmattei have you managed to use lambdaws ?

Sylvain Perron

@slvnperron

@rantonmattei there is no bin directory, did you mean lib ? Entry point is /index.js which points to /lib/lambdaws.js

Gustav Svalander

@gurre

Hey, I suppose you can use this lib just for creating lambda-functions to be available by other services on aws?

Sylvain Perron

@slvnperron

@gurre what do you mean?

if you mean just to upload a function and make it available to receive events from other AWS Services, then yes

Raphaël Antonmattei

@rantonmattei

I figured it out. It is in master but not available on npm yet.

https://github.com/mentum/lambdaws/tree/master/bin

Thanks

Sylvain Perron

@slvnperron

Oh, yes. Sorry about that

We’ll push to NPM this week along with other features

Raphaël Antonmattei

@rantonmattei

Just tried to install 1.0.12

got the following:

npm ERR! Darwin 14.1.0
npm ERR! argv "node" "/usr/local/bin/npm" "install"
npm ERR! node v0.10.28
npm ERR! npm  v2.7.1
npm ERR! path /Users/rantonmattei/work/dev/lambdas/node_modules/lambdaws/bin/lambdaws-cli
npm ERR! code ENOENT
npm ERR! errno 34

npm ERR! enoent ENOENT, chmod '/Users/rantonmattei/work/dev/lambdas/node_modules/lambdaws/bin/lambdaws-cli'
npm ERR! enoent This is most likely not a problem with npm itself
npm ERR! enoent and is related to npm not being able to find a file.
npm ERR! enoent

1.0.11 is going through just fine

Anyone experienced that?

Luciano Bertenasco

@lbertenasco

Hey guys, first of all great work! It runs great and its super easy to set up. Thank you for your hard work!

Secondly, I'm having an issue sometimes when i restart or re-upload the server in ebs & local. I have 3 lambda functions and on every restart i always get one of them stuck with this message:
{ [Error: Function upload to AWS Lambda timed out.] code: 'ETIMEDOUT' }
I need to manually delete the lambda function from the aws console, then restart the server in ebs and pray that it works. its kind of random and i couldn't figure out why it happens.
Can you give me a hand?

EFF

@EFF

Hey @rantonmattei, you’re right, looks like we’re experiencing some issues with our CLI. Thanks for your feedback, I’ll fix this issue tomorrow during the day. If you get time and figure out what’s going on, please send a PR !

@lbertenasco thanks for your support. Lambdaws will get most of my attention tomorrow during the day, I’ll try to figure out what’s happening in there.

EFF

@EFF

If you guys land up on anything more that I should take care of, please feel free to notify !

Luciano Bertenasco

@lbertenasco

Thanks @EFF, meanwhile i'll keep trying to solve this by myself. if i have news i'll let you know.

EFF

@EFF

great !!!

Raphaël Antonmattei

@rantonmattei

@EFF thx! I noticed the version is also off on master in the package.json it says "version": "1.0.10" whereas the latest is supposed to be 1.0.12 according to NPM. I'll look into that error.
Another thing that could help to debug this would be to publish the tags on github, cause it is really hard for me to know what I actually pull. (I mean npm vs. github)

Sylvain Perron

@slvnperron

Hey @lbertenasco ! Thank you for the feedback, it’s really appreciated. There’s other people that had the same issue, and it seems like it could be related to a slow upload. The default timeout is 5 seconds, can you try raising that timeout to 20s?

  credentials: {
    accessKey: 'MYACCESSKEY',  // string, AWS AccessKeyId.
    secretKey: 'MYSECRETKEY',  // string, AWS AccessKeySecret.
  },
  role: 'arn:aws:iam::999999999999999:role/lambda_exec_role',  // string, AWS ARN. Must have full access to SQS.
  region: 'us-east-1',
  uploadTimeout: 30000
});

@rantonmattei you’re right, we’ll do that. Feel free to make a PR if you happen to know how to do this quickly. The CLI isn’t working with npm for some reason, but if you pull master you can run the CLI with node bin/lambdaws-cli

Luciano Bertenasco

@lbertenasco

@slvnperron good info, i mistakenly thought the default was 20s. i've just changed my config adding "uploadTimeout: 120000" (just to be safe) and it seems it fixed the issue.
I re-uploaded it several times to give it a good try and it does not break, thank you very much!

EFF

@EFF

@lbertenasco good to hear !

Sylvain Perron

@slvnperron

@lbertenasco Glad it fixed your issue!

Sylvain Perron

@slvnperron

@lbertenasco The CLI’s fixed in 1.0.14

Raphaël Antonmattei

@rantonmattei

Thanks, that's great

Raphaël Antonmattei

@rantonmattei

Hi there

I am working with S3 events

and the way the user function is called does not allow that because you call :

func.apply(this, event.args);

in https://github.com/mentum/lambdaws/blob/master/lib/LambdaHelper.js#L52

If I change this to

func.apply(this, [event, context]);

this works fine

so, I was about to submit a PR for that

however I ran into another issue with this line
event.args.push(doneCallback);
https://github.com/mentum/lambdaws/blob/master/lib/LambdaHelper.js#L46

because in my case, the args property is not defined

Here is the event object I get back from the invocation

[ { eventVersion: '2.0', eventSource: 'aws:s3', awsRegion: 'us-east-1', eventTime: '2015-03-18T15:40:07.417Z', eventName: 'ObjectCreated:Put', userIdentity: [Object], requestParameters: [Object], responseElements: [Object], s3: [Object] } ] }

So, that line triggers an error

Failure while running task: TypeError: Cannot call method 'push' of undefined at __lambda__ (/var/task/index.js:13:20)

Where communities thrive

People

Repo info

Activity