CODEWITHSUNDEEP
aws-lambdaaws-code-deployaws-codepipelineaws-codebuildaws-serverless
Saad Siddiqui
Saad Siddiqui

Reputation: 63

What’s the best way to deploy multiple lambda functions from a single github repo onto AWS?

I have a single repository that hosts my lambda functions on github. I would like to be able to deploy the new versions whenever new logic is pushed to master.

I did a lot of reasearch and found a few different approaches, but nothing really clear. Would like to know what others feel would be the best way to go about this, and maybe some detail (if possible) into how that pipeline is setup.

Thanks

Upvotes: 6

Views: 9684

Answers (4)

sachin
sachin

Reputation: 1117

I too had the same problem. I wanted to manage 12 lambdas with 1 git repository. I solved it by introducing travis-ci. travis-ci saved the time and really useful in many ways. We can check the logs whenever we want and you can share the logs to anyone by sharing the URL. The sample documentation of all steps can be found here. You can go through it. 👍

Upvotes: 1

Aaron
Aaron

Reputation: 1605

Given that you're using AWS Lambda, you may want to consider CodePipeline to automate your release process. [SAM(https://docs.aws.amazon.com/lambda/latest/dg/serverless_app.html) may also be interesting.

Upvotes: 1

Thales Minussi
Thales Minussi

Reputation: 7245

Welcome to StackOverflow. You can improve your question by reading this page.

You can setup a CI/CD pipeline using CircleCI with its GitHub integration (which is an online Service, so you don't need to maintain anything, like a Jenkins server, for example)

Upon every commit to your repository, a CircleCI build will be triggered. Once the build process is over, you can declare sls deploy, sam deploy, use Terraform or even create a script to upload the .zip file from your GitHub repo to an S3 Bucket and then, within your script, invoke the create-function command. There's an example how to deploy Serverless applications using CircleCI along with the Serverless Framework here

Other options include TravisCI, AWS Code Deploy or even maintain your own CI/CD Server. The same logic applies to all of these tools though: commit -> build -> deploy (using one of the tools you've chosen).

EDIT: After @Matt's answer, it clicked that the OP never mentioned the Serverless Framework (I, somehow, thought he was already using it, so I pointed the OP to tutorials using the Serverless Framework already). I then decided to update my answer with a few other options for serverless deployment

Upvotes: 2

Matt Clevenger
Matt Clevenger

Reputation: 337

I know that this isn't exactly what you asked for but I use Serverless Framework (https://serverless.com) for deployment and I love it. I don't do my deployments when I push to my repo. Instead I push to my repo after I've deployed. I like this flow because a deployment can fail due to so many things and pushing to GitHub is much less likely to fail. I this way, I prevent pushing code that failed to deploy to my master branch.

I don't know if you're familiar with the framework but it is super simple. The website describes the simple steps to creating and deploy a function like this.

1     # Step 1. Install serverless globally
2     $ npm install serverless -g
3
4     # Step 2. Create a serverless function
5     $ serverless create --template hello-world
6 
7     # Step 3. deploy to cloud provider
8     $ serverless deploy
9
10   # Your function is deployed!
11   $ http://xyz.amazonaws.com/hello-world

There are also a number of plugins you can use to integrate easily with custom domains on APIGateway, prune older versions of lambda functions that might be filling up your limits, etc...

Overall, I've found it to be the easiest way to manage and deploy my lambdas. Hope it helps!

Upvotes: 2

Related Questions