How to utilize .ebextension while using CodePipeline

Question

I'm using CodePipeline to deploy whatever is on master branch of the git to Elastic Beanstalk.

I followed this tutorial to extend the default nginx configuration (specifically the max-body-size): https://medium.com/swlh/using-ebextensions-to-extend-nginx-default-configuration-in-aws-elastic-beanstalk-189b844ab6ad

However, because I'm not using the standard eb deploy command, I dont think the CodePipeline flow is going into the .ebextension directory and doing the things its supposed to do.

Is there a way to use code pipeline (so i can have CI/CD from master) as well as utilize the benefits of .ebextension?

Answer 1

Does this work if you use the eb deploy command directly? If yes, then I would try using the pipeline execution history to find a recent artifact to download and test with the eb deploy command.

Answer 2

If CodePipeline's Elastic Beanstalk Job Worker does not play well with ebextensions, I would consider it completely useless to deploy to Elastic Beanstalk.

I believe there is some problem with the ebextensions themselves. You can investigate the execution in these log files to see if something is going wrong during deployment:

• /var/log/eb-activity.log
• /var/log/eb-commandprocessor.log
• /var/log/eb-version-deployment.log