title: Continuous Integration on AWS EMR
body: <p>We have a long running EMR cluster that has multiple libraries installed on it using bootstrap actions. Some of these libraries are under continuous development and their codebase is on GitHub.</p>
  
  <p>I've been looking to plug Travis CI with AWS EMR in a similar way to Travis and CodeDeploy. The idea is to get the code on GitHub tested and deployed automatically to EMR while using bootstrap actions to install the updated libraries on all EMR's nodes.</p>
  
  <p>A solution I came up with is to use an EC2 instance in the middle, where Travis and CodeDeploy can be first used to deploy the code on the instance. After that a lunch script on the instance is triggered to create a new EMR cluster with the updated libraries. </p>
  
  <p>However, the above solution means we need to create a new EMR cluster every time we deploy a new version of the system</p>
  
  <p>Any other suggestions?</p>