Answers: <p>Your idea will work. The organization I work for maintains some <a href="https://github.com/scaniadevtools/aws-deployer" rel="nofollow noreferrer">open source examples</a> how to do deploy to AWS using a pipeline. In comparison we use <a href="https://gitlab.com" rel="nofollow noreferrer">GitLab</a> for the purpose. Instead of Travis we use <a href="https://docs.gitlab.com/runner/" rel="nofollow noreferrer">GitLab Runner</a>. You configure it using the file <code>.gitlab-ci.yml</code> which runs the tests and deploy the AWS Lambda to dev, test and production environment every time a commit is done.  You store your secret account variables in the CI/CD settings of the repository.</p>
  
  <p>There are the usual drawbacks of AWS Lambda such as difficult or impossible to test and run locally and waiting for deployments takes time, but your deployment process will be good practice.  </p>
  
Answers: CC BY-SA 4.0
Answers: 2018-11-09T03:18:25.193Z
Answers: 2018-11-09T03:18:25.193Z
Answers: Niklas Rosencrantz
Body: <p>Will it be practically possible to build some pipeline; </p>
  
  <ol>
  <li>starting from rapid AWS Lambda function development using blueprints, </li>
  <li>to store them later on a new GitHub repo, </li>
  <li>that is linked to some CICD such as Travis, </li>
  <li>that will in turn deploy successful builds back in AWS Lambda?</li>
  </ol>
  
Tags: <amazon-web-services><github><aws-lambda><travis-ci>
Title: Storing my Lambda Functions on GitHub
UserDisplayName: A.Rashad
ThreadText: # Storing my Lambda Functions on GitHub
  
  (Asked by: username_0 on 2018-11-08)
  
  Will it be practically possible to build some pipeline;
  
  1. starting from rapid AWS Lambda function development using blueprints,
  2. to store them later on a new GitHub repo,
  3. that is linked to some CICD such as Travis,
  4. that will in turn deploy successful builds back in AWS Lambda?
  
  **Tags:** amazon-web-services, github, aws-lambda, travis-ci
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2018-11-09. Score: 2 | Accepted answer
  
  Your idea will work. The organization I work for maintains some [open source examples](https://github.com/scaniadevtools/aws-deployer) how to do deploy to AWS using a pipeline. In comparison we use [GitLab](https://gitlab.com) for the purpose. Instead of Travis we use [GitLab Runner](https://docs.gitlab.com/runner/). You configure it using the file `.gitlab-ci.yml` which runs the tests and deploy the AWS Lambda to dev, test and production environment every time a commit is done. You store your secret account variables in the CI/CD settings of the repository.
  
  There are the usual drawbacks of AWS Lambda such as difficult or impossible to test and run locally and waiting for deployments takes time, but your deployment process will be good practice.
  
  
  ---
  
  