title: Where to put ebextensions config in AWS Elastic Beanstalk Docker deploy with dockerrun source bundle?
body: <p>I am having trouble getting my docker elastic beanstalk deploy to read my .ebextensions/setup.config file.</p>
  
  <p>The documentation for <a href="http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/customize-containers.html">eb environment configuration</a> says:</p>
  
  <blockquote>
    <p>You can include one or more configuration files with your source bundle. Configuration files must be named with the extension .config (for example, myapp.config) and placed in an .ebextensions top-level directory in your source bundle.</p>
  </blockquote>
  
  <p>However it looks like for Docker that the source bundle is not a <code>.zip</code> or <code>.war</code> file, but a <code>.json</code> file, e.g., the docs say to <a href="http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/create_deploy_docker_image.html">create a Dockerrun.aws.json file</a>—and it looks like that is the source bundle?</p>
  
  <p>In creating a version of the app I upload a custom <code>Dockerrun-$VERSION.aws.json</code> file to s3 and the run something like the following (where <code>$APP</code> is the versioned dockerrun json file):</p>
  
  <pre class="lang-sh prettyprint-override"><code>aws elasticbeanstalk create-application-version \
      --application-name $APP_NAME \
      --version-label $VERSION \
      --source-bundle S3Bucket=$S3_BUCKET,S3Key=$S3_PATH/$APP
  </code></pre>
  
  <p>So… how is the .ebextensions directory going to be found in the top-level directory of the source bundle when the “bundle” is just a json file that ends up building a container? (My first attempt was to just put it in the root of the project, but that didn’t work.)</p>