Continuous Deployment with AWS Lambda and API Gateway

Question

Has anyone figured out a method of doing continuous deployment with AWS Lambda? We are looking at Lambda, and the new API gateway, for a very large API app we are designing for a client. It looks perfect - no servers we have to worry about, infinite scalability. But the client wants to do continuous deployment. Lambda does not have versioning, so we'd have to figure out how to increment the versions. But the idea is to do the whole thing - checkout, any code manipulation that's required, zip, send to AWS, automatically, or at worst at the push of a button.

I've had a look at Strider, and can probably use this, but there is going to be a lot of custom dev involved for scripts at each step of the build. And Strider doesn't seem to have the concept of multiple environments, so I'm not sure I can set it up to build dev, and qa, without having to have multiple bitbucket projects. We essentially have to check out the repo, create the deployment package which means moving some code around, zipping it up, and sending it to AWS.

Checkout this article one the AWS blog: blog.cloudbees.com/2015/07/… — Frank
– Frank, Commented Jul 16, 2015 at 10:54
Thanks. Pretty bare bones. After doing a bunch more research, and trying out API Gateway and Lamdba, we are coming to the conclusion that it is just not ready for prime time. It's missing a whole bunch of functionality that we need. Might be back to Elastic Beanstalk. — CargoMeister
– CargoMeister, Commented Jul 16, 2015 at 20:30

typemismatch · Accepted Answer · 2015-08-05 20:47:39Z

1

I would take a look at this project, we are in the same boat and are about to give this a test run to handle our AWS deployments - seems like they are solving the right problems especially around environments...

https://github.com/servant-app/JAWS

answered Aug 5, 2015 at 20:47

typemismatch

2,0583 gold badges23 silver badges26 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

CargoMeister Over a year ago

That does look interesting, doesn't it? Will keep my eye on that. We are definitely back to beanstalk for this app, but next go around, maybe not.

Michael Hart · Accepted Answer · 2016-07-06 21:53:54Z

1

LambCI can do this (disclaimer: I wrote it!)

I wrote a blog post introducing it here:

https://medium.com/@hichaelmart/lambci-4c3e29d6599b#.c071nns8h

answered Jul 6, 2016 at 21:53

Michael Hart

5,1893 gold badges25 silver badges21 bronze badges

Comments

Kosio · Accepted Answer · 2015-08-31 12:49:09Z

0

You may want to take a look at kappa (https://github.com/garnaat/kappa). It is a command line tool for deploying and testing AWS lambda functions.

You cannot control the API gateway settings, but at least the AWS deployment

answered Aug 31, 2015 at 12:49

Kosio

941 silver badge4 bronze badges

Comments

Camilo Ortegón · Accepted Answer · 2016-05-09 15:02:29Z

0

One easy way to start with continuous delivery is creating an auto-deployment code using s3 and aws lambda. S3 allows you do versioning and you can trigger from there a deployment to one or multiple lambda functions.

For detailed instructions to do so, read this tutorial I did: https://cloudpointer.blogspot.com.co/2016/04/continuous-delivery-with-aws-lambda.html

answered May 9, 2016 at 15:02

Camilo Ortegón

3,7423 gold badges29 silver badges34 bronze badges

Collectives™ on Stack Overflow

Continuous Deployment with AWS Lambda and API Gateway

4 Answers 4

1 Comment

Comments

Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

4 Answers 4

1 Comment

Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related