kappa

Another nice project that helps to ease lambda workflows is https://github.com/garnaat/kappa

> There seems to be some issue applying privileges that I can't seem to figure out. Your lambda function will fail to execute because API Gateway does not have permissions to execute your function. This stuff is definitely confusing. I think I "reverse-engineered" from applying things via the web interface and then looking at the policy when I created Gimel[0] - an AWS Lambda A/B testing backend. Take a look here[1] for the policy. I think that's what you're looking for, but I can't say I'm confident it is... (it's confusing). There are some more general-purpose tools to help you deploy to Lambda. Kappa[2] and Apex[3] are worth looking into. [0] https://github.com/Alephbet/gimel [1] https://github.com/Alephbet/gimel/blob/master/gimel/deploy.p... [2] https://github.com/garnaat/kappa [3] https://github.com/apex/apex

If you're using Python, you might also want to check out Kappa [0] [0] http://github.com/garnaat/kappa

If you're interested in dirt simple Lambda deployment, check out Kappa[0], written by the same person as boto. Gordon looks interesting and I'm definitely going to check it out, but from what I can tell, one of the downsides is that it uses CF. Don't get me wrong, I love CF for it's reproducibility, but waiting for a CF stack to run on every deploy will be frustrating for rapid iteration. CF is great for managing your infrastructure once you have a good idea of how it should look and aren't making constant changes anymore. I suspect my workflow will be something like using Kappa while I'm iterating, and then using Gordon for the final deployment once it looks like everything is working as expected. [0] https://github.com/garnaat/kappa

We built Kappa[0] to handle our production Lambda deployment. It was built by the same person who wrote Boto and the AWS command line. Here is an example[1] of a program built in Python that uses Kappa, and here is a video tutorial[2] on how I deploy that program with kappa. Obviously I disagree with the premise. It's true that it is more difficult to use than other technologies and you'll certainly pay the pioneer tax, having to develop your own tooling, but it's ready for production traffic. Error handling is ok, could be better (it takes a while for the cloud watch log to show up). The real big problem is testing. It's really hard to test if you have more than one function because there is no mocking framework (yet). It's fairly easy to deploy and test with a test account, but local testing still needs to be solved. [0] https://git

https://github.com/garnaat/kappa targets the same feature set, and has more functionality afaics, albeit perhaps slightly different. It has more sources to bind lambda to, and takes care of more of the drudgery (iam, permissions, etc). It doesn't do the nodejs shim for go.

My company is building exclusively[0] on Lambda and API Gateway. It's definitely got its warts and you'll be paying an early adopters tax for sure. My cofounder wrote a tool to help manage Lambda deployments: https://github.com/garnaat/kappa/tree/python-refactor [0] Well as much as we can. We're building a Slack bot right now so we still need a container running under ECS to maintain the connection to Slack.

A few options - Codeship (https://blog.codeship.com/integrating-aws-lambda-with-codesh...), popular community extensions such as Kappa (https://github.com/garnaat/kappa) Jenkins plugins (https://wiki.jenkins-ci.org/display/JENKINS/AWS+Lambda+Plugi...) and Grunt plugins (https://github.com/Tim-B/grunt-aws-lambda/commits/master/pac...) that you can use as part of your CI/CD pipelines. There was even recent blogpost about using Lambda to deploy Lambda functions :) (https://aws.amazon.com/blogs/compute/new-deployment-options-...). Would be great to hear what else you would like to see.