aws-code-deploy

Environment variables using AWS CodeDeploy

心已入冬 提交于 2019-12-03 09:49:20
I have a web application that utilizes environment variables for some of its configuration (DB credentials, API keys, etc). I'm currently using Elastic Beanstalk for deployment and can easily set these from within AWS, which is great because I don't have this sensitive data in my code base. However, I'm looking into switching from Elastic Beanstalk so I can leverage a bit more flexibility with my web instances, and naturally I'm looking into deploying (from my Codeship CI setup) using CodeDeploy. CodeDeploy is fairly straight forward and I've integrated it with Codeship just fine, but I

Can I use AWS code Deploy for pulling application code while autoscaling?

六眼飞鱼酱① 提交于 2019-12-03 05:55:04
问题 I want to autoscale the infrastructure when load gets high. I am running my infrastructure on AWS . I have a requirement where I need to pull the application code from Github when autoscaling happens. As the code changes frequently, we can't take an AMI and launch an instance from that AMI . So I want to pull the latest code from repositories . AWS just launched a service called AWS CodeDeploy . How can I use this service to automate the process of pulling the code when the instances start? P

Can I use AWS code Deploy for pulling application code while autoscaling?

假装没事ソ 提交于 2019-12-02 20:34:43
I want to autoscale the infrastructure when load gets high. I am running my infrastructure on AWS . I have a requirement where I need to pull the application code from Github when autoscaling happens. As the code changes frequently, we can't take an AMI and launch an instance from that AMI . So I want to pull the latest code from repositories . AWS just launched a service called AWS CodeDeploy . How can I use this service to automate the process of pulling the code when the instances start? P.S. I have written an init script to automatically attach an EIP , whitelist that IP on different

Amazon CodeDeploy. Deployment failed

不羁岁月 提交于 2019-12-02 00:04:13
问题 I have been configuring AWS CodeDeploy for a few days and my first deployment is failing. The error message I get reads "The overall deployment failed because too many individual instances failed deployment, too few healthy instances are available for deployment, or some instances in your deployment group are experiencing problems." To get more detailed info I have installed the AWS CodeDeploy agent on the Windows instance and it appears not to be working. All what I manage to read in the

AWS CodeDeploy Fail: The deployment failed because a specified file already exists at this location

蹲街弑〆低调 提交于 2019-12-01 03:10:59
I am trying to set AWS Code deploy with Github to automate my deloyment. the problem i am having is the ec2 instance is already active and has the web app code. the problem is there is also other content on the instance that I don't want under source control. Code deploy is failing with the following error: The deployment failed because a specified file already exists at this location this is because the source code is on the instance and was not added as a revision. So my question is there any way to make the code deploy recognise the current files on the instance as an inital revision? This

AWS CodeDeploy Fail: The deployment failed because a specified file already exists at this location

倖福魔咒の 提交于 2019-11-30 22:46:37
问题 I am trying to set AWS Code deploy with Github to automate my deloyment. the problem i am having is the ec2 instance is already active and has the web app code. the problem is there is also other content on the instance that I don't want under source control. Code deploy is failing with the following error: The deployment failed because a specified file already exists at this location this is because the source code is on the instance and was not added as a revision. So my question is there

AWS CodeDeploy Github File Already Exist

这一生的挚爱 提交于 2019-11-30 17:11:15
问题 I am trying to use AWS CodeDeploy to pull my latest changes from Github down to a server. The problem I am running into is on the install step I am getting this error: Error CodeUnknownError Script Name MessageFile already exists at location /data/sites/wordpress/api_now_playing_staging.php Log Tail And my appspec.yml looks like this: version: 0.0 os: "linux" files: - source: "/" destination: "/data/sites/wordpress" permissions: - object: /data/sites/wordpress pattern: "**" owner: wp group:

Amazon Web Service CodeDeploy appspec.yml problems

痞子三分冷 提交于 2019-11-30 12:45:40
问题 I have a Node.js application which is being automatically deployed to Amazon Web Service through Codeship using the CodeDeploy AWS deployment system . During the deployment process I've set in my appspec.yml for the currently running web application to be stopped. Once the deployment is complete, I want the web application to be started up again. os: linux files: - source: / destination: /var/www/app2 hooks: AfterInstall: - location: bash_scripts/stop_forever.sh runas: ec2-user

How to deploy with Gitlab-Ci to EC2 using AWS CodeDeploy/CodePipeline/S3

烂漫一生 提交于 2019-11-28 13:45:34
问题 I've been working on a SlackBot project based in Scala using Gradle and have been looking into ways to leverage Gitlab-CI for the purpose of deploying to AWS EC2. I am able to fully build and test my application with Gitlab-CI. How can I perform a deployment from Gitlab-CI to Amazon EC2 Using CodeDeploy and CodePipeline? Answer to follow as a Guide to do this. 回答1: I have created a set of sample files to go with the Guide provided below. These files are available at the following link: https:

Jenkins triggered code deploy is failing at ApplicationStop step even though same deployment group via code deploy directly is running successfully

泪湿孤枕 提交于 2019-11-28 10:47:24
问题 When I trigger via Jenkins (code deploy plugin), I get the following error - No such file or directory - /opt/codedeploy-agent/deployment-root/edbe4bd2-3999-4820-b782-42d8aceb18e6/d-8C01LCBMG/deployment-archive/appspec.yml However, if I trigger deployment into the same deployment group via code deploy directly, and specify the same zip in S3 (obtained via Jenkins trigger), this step passes. What does this mean, and how do I find a workaround to this? I am currently working on integrating a