title: Beanstalk deployment ignores my nginx configuration files in .ebextensions
body: <p>I host my Java webapp on a single-instance Elastic Beanstalk environment and I added several ebextension files which successfully create config files for me upon each deployment. I can't however find a way of getting Beanstalk to add new configs within the <code>/etc/nginx</code> or <code>/etc/nginx/conf.d</code> directories.</p>
  
  <p>I followed the steps described here: <a href="https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/https-singleinstance-java.html" rel="noreferrer">https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/https-singleinstance-java.html</a></p>
  
  <p>My deployment package structure looks like this:</p>
  
  <pre><code>$ zip -r deploy.zip api-1.0-SNAPSHOT-all.jar .ebextensions
    adding: api-1.0-SNAPSHOT-all.jar (deflated 11%)
    adding: .ebextensions/ (stored 0%)
    adding: .ebextensions/ssl-certificates.config (deflated 37%)
    adding: .ebextensions/https-instance-securitygroup.config (deflated 38%)
    adding: .ebextensions/nginx/ (stored 0%)
    adding: .ebextensions/nginx/conf.d/ (stored 0%)
    adding: .ebextensions/nginx/conf.d/https.conf (deflated 61%)
  </code></pre>
  
  <p>My files are nearly 1-to-1 copy of samples in the guide above.</p>
  
  <p>During deployment both my <code>*.config</code> files execute successfully, but the <code>/etc/nginx/conf.d/https.conf</code> is missing. I tried to workaround the issue by removing the <code>.ebextensions/nginx</code> directory and replacing it with another <code>.config</code> file that creates <code>/etc/nginx/conf.d/https.conf</code> from scratch, but this didn't help and the file was still missing.</p>
  
  <p>I ssh-ed onto my EC2 instance and here's what I found in <code>/var/log/eb-engine.log</code>:</p>
  
  <pre><code>2020/05/03 19:42:37.754375 [INFO] Executing instruction: configure proxy Nginx
  2020/05/03 19:42:37.754393 [WARN] skipping nginx folder under .ebextensions
  2020/05/03 19:42:37.754670 [INFO] No plugin in cfn metadata.
  </code></pre>
  
  <p>I feel like I might have missed something very obvious here, but surprisingly I couldn't find any solution to my problem. Thoughts? Thanks!</p>