Has anyone figured out a continuous deployment method with AWS Lambda? We are considering Lambda and the new API gateway for the very large API application that we are developing for the client. It looks great - without the servers we need to worry about, infinite scalability. But the client wants to do continuous deployment. Lambda does not have a version, so we need to figure out how to increase the versions. But the idea is to do all this: checkout, any necessary code manipulations, zip, send to AWS, automatically or in the worst case, with the click of a button.
I took a look at Strider and I can probably use this, but a lot of custom developers will be involved at every build stage. And Strider doesn't seem to have the concept of multiple environments, so I'm not sure I can configure it to create dev and qa without having to have multiple bitbucket projects. We essentially need to check out the repo, create a deployment package that means moving some code, filing it and sending it to AWS.
source
share