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?

score 3 · Answer 1 · answered Oct 04 '19 at 23:03

3

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.

answered Oct 04 '19 at 23:03

Aaron

1,575
10
18

it works with eb deploy, but doesnt seem to work when i use code pipeline – yasgur99 Oct 23 '19 at 19:11
I am facing same problem – Kamlesh Delat Jun 16 '21 at 06:05
It's work for me after update buildspec.yml version – Kamlesh Delat Jun 16 '21 at 06:18

score 2 · Answer 2 · answered Oct 05 '19 at 05:43

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

score 1 · Answer 3 · answered Oct 09 '19 at 05:37

1

All the config files under .ebextension will be executed based on the order of precedence while deploying on the Elastic Beanstalk. So, it is doesn't matter whether you are using codepipeline or eb deploy, all the file in ebextension directory will be executed. So, you don't have to worry about that.

answered Oct 09 '19 at 05:37

Mounick

171
5

its working with eb deploy, but doesn't seem to be running with code pipeline. any ideas on why this discrepancy? – yasgur99 Oct 23 '19 at 19:11

score 1 · Answer 4 · edited Jun 12 '20 at 14:39

1

Be careful about the platform you're using, since “64bit Amazon Linux 2 v5.0.2" instead of .ebextension you have to use .platform.

Create .platform directory instead of .ebextension
Create the subfolders and the proxy.conf file like in this path .platform/nginx/conf.d/proxy.conf
In proxy.conf write what you need, in case of req body size just client_max_body_size 20M;

edited Jun 12 '20 at 14:39

Hoppo

1,130
1
13
32

answered Jun 12 '20 at 11:02

Andrea Arseni

11
3

score 0 · Answer 5 · answered Feb 05 '20 at 17:17

I resolved the problem. You need include .ebextension folder in your deploy. I only copy the dist files, then I need include too: - .ebextensions/**/*

Example:

## Required mapping. Represents the buildspec version. We recommend that you use 0.2.
version: 0.2

phases:
  ## install: install dependencies you may need for your build
  install:
    runtime-versions:
      nodejs: 12
    commands:
      - echo Installing Nest...
      - npm install -g @nestjs/cli
  ## pre_build: final commands to execute before build
  pre_build:
    commands:
      - echo Installing source NPM dependencies...
      - npm install
  ## build: actual build commands
  build:
    commands:
      # Build your app
      - echo Build started on `date`
      - echo Compiling the Node.js code
      - npm run build
      ## Clean up node_modules to keep only production dependencies
      # - npm prune --production

  ## post_build: finishing touches
  post_build:
    commands:
      - echo Build completed on `date`
# Include only the files required for your application to run.
artifacts:
  files:
    - dist/**/*
    - package.json
    - node_modules/**/*
    - .ebextensions/**/*

Ande the config file /.ebextensions/.node-settings.config:

option_settings:
  aws:elasticbeanstalk:container:nodejs:
    NodeCommand: "npm run start:prod"

How to utilize .ebextension while using CodePipeline

5 Answers5