title: Best Practices when it comes to creating aws batch components
body: <p>We are planning to use aws batch for excution of some compute intensive models written in python. As I understand there is a terraform provider for aws batch which allows you to create compute env, job queue and job defintion.</p>
  <p>We are clear that creating the job should be part of the model ci/cd pipeline. We are also clear that compute and job queue should be created via terraform which our devops own.</p>
  <p>We are not too sure about job defintion if it should be owned by devops or should go in the models repository. The reason is becuase it contains details about the containers which is created from the models repo. Our code structure for model looks like this</p>
  <pre><code>src
    Dockerfile
    .gitlab-ci.yml
    somepythonfile.py
  </code></pre>
  <p>Any thoughts on what is the best practice here?</p>
  <p>Thanks,
  Ashish</p>