nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to configure pipeline to send prod and staging builds to different aws ec2 with code deploy?

Muhammad Shahid_oso29r

Hi Team,

We have two ec2 instances one is for production and 2nd one is for development/staging. Similarly we have two branches, master and develop. Master's build is in used at production ec2 instance and develop is for staging server.

I have configured bitbucket-pipeline.yml with branches flow. But how I can control appsec.yml or any other feature to manage flow of builds to copy over just to relevant ec2 instances. At AWS codedeploy I can configure deployment group and when there would be commit either at master or develop branch, that build will be pushed to codedeploy deployment process and it will push code to deployment group where both servers are in same deployment group.

So question is how and where we can control build deployment to respective instance only with feature bitbucket to aws codedeploy.

Accepted answers

All comments

BillyP

Hi Muhammad,

I was reading up on your issue and I wanted to learn more about the situation. In doing so, I found this page.

https://hackernoon.com/deploy-to-ec2-with-aws-codedeploy-from-bitbucket-pipelines-4f403e96d50c

How do you currently select which system to deploy to? dev/ staging

-Billy

Muhammad Shahid_oso29r

Thank you Billy, I have check out this post and my setup is 100% relevant to this post. This setup is good for one deployment group. For example in DG1 (CodeDeploy) group if I put both servers production and staging and when pipelines will run and push code/build at that point how should I control deployment to just staging or just to production?

This is my bitbucker-pipeline.yml

pipelines: branches: develop: - step: name: Run Build and Deploy to Staging Server image: node:6 script: npm install - npm run build  - codedeploy_deploy.py # run the deployment script  branches: master: - step: name: Run Build and Deploy to Prod Server image: node:6 script: - npm install - npm run build  - python codedeploy_deploy.py

appsec.yml

version: 0.0os: linuxfiles: - source: / destination: /var/www/apphooks: BeforeInstall: - location: scripts/install_dependencies timeout: 300 runas: root - location: scripts/start_server timeout: 300 runas: root ApplicationStop: - location: scripts/stop_server timeout: 300 runas: root

Jeroen De Raedt

Am I correct in assuming that the real difference is that you want to use different appsec.yml files for staging and production?

If that is the case, 1 solution could be to create 2 directories in your repository (/staging and /production) and in each you store the appropriate version of the appsec.yml file. When doing deployments, you change directories to the appropriate folder and then execute the codedeploy script.

Muhammad Shahid_7ljv45

Thanks for reply, basically issue is not handle appsec.yml. We can have similar path for staging and production server. Issue is at AWS deployment group. There we can select deployment group with bunch of ec2 instances. But how we can deploy to just staging and production instances separately. At pipeline we can define environmental variables but for singal deployment group. So how to deploy to staging and just for production deployment groups.

Jeroen De Raedt

Ah right I see.

I suspect that the python script you use has hardcoded in it to use a certain environment variable to configure the AWS deployment group?

In the step that does a deployment, you could add a command to your script in bitbucket-pipelines.yml that overwrites the value of your deployment group variable.

For example:

pipelines: 
 branches: 
 develop: 
 - step:
 name: Run Build and Deploy to Staging Server
 image: node:6
 script:
 - npm install
 - npm run build 
 - export DEPLOYMENT_GROUP="STAGING"
 - codedeploy_deploy.py # run the deployment script 
 master:
 - step:
 name: Run Build and Deploy to Prod Server
 image: node:6
 script:
 - npm install
 - npm run build
 - export DEPLOYMENT_GROUP="PRODUCTION"
 - python codedeploy_deploy.py

BillyP

Jeroen,

It looks like this will deploy to both groups at the same time. Is that correct?

Muhammad Shahid_oso29r

No, That can be controller through bitbucket-pipeline.yml branch flow. Actual thing was at code deploy deployment and now if we can over ride environment variables through deployment script that would be super cool. Will give it a try. @Jeroen De Raedt can you please share any possible deployment script? or edit this one :

https://bitbucket.org/awslabs/aws-codedeploy-bitbucket-pipelines-python/src/73b7c31b0a72a038ea0a9b46e457392c45ce76da/codedeploy_deploy.py?at=master&fileviewer=file-view-default

Oleksandr Kyrdan

Hi @Muhammad Shahid ,

if you need AWS Code Deploy in your Bitbucket Pipelines you can use pipe aws-code-deploy

Also, more available pipes you can discover on the Bitbucket Pipes page.

Cheers,
Alex

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

git

bitbucket-pipelines

branch