{"id":27240,"date":"2016-07-31T12:29:42","date_gmt":"2016-07-31T06:59:42","guid":{"rendered":"http:\/\/www.tothenew.com\/blog\/?p=27240"},"modified":"2022-01-11T11:25:43","modified_gmt":"2022-01-11T05:55:43","slug":"aws-codedeploy-and-github","status":"publish","type":"post","link":"https:\/\/www.tothenew.com\/blog\/aws-codedeploy-and-github\/","title":{"rendered":"Deploy Code using AWS CodeDeploy and GitHub"},"content":{"rendered":"

The much talked about AWS CodeDeploy<\/a> is being used as a daily deployment tool. According to AWS “AWS CodeDeploy coordinates application deployments to Amazon EC2 instances, on-premises instances, or both. (On-premises instances are physical devices that are not Amazon EC2 instances.)”<\/p>\n

On-premise support came in mid-2015. AWS CodeDeploy has been the choice of many since a long time and we are going to talk about it in this blog.<\/p>\n

Use-case<\/h2>\n

I had to automate my deployment<\/a> process. I came across AWS CodeDeploy and it helped me to deploy my new code with ease and simplicity. We will go through the basic setup of CodeDeploy service, installation of CodeDeploy agent on a server (AWS EC2 instance) and deployment of new code from GitHub onto it. CodeDeploy is a region level service and in this, we will talk about deployment in the Virginia region. For using it in any other region, you have to make just a few changes in endpoints\u00a0which is simple too.<\/p>\n

\"\"<\/p>\n

Prerequisites<\/h2>\n
    \n
  1. An AWS EC2 instance with IAM role attached. If you don’t have a role attached to your EC2 instance, then you will have to launch a new EC2 instance with an attached role from an AMI. For now, you can just attach a blank role, and I will tell you later in the blog about what permissions policy to attach.<\/li>\n
  2. Access to GitHub repository where the code is present<\/li>\n
  3. AWS IAM role for the AWS CodeDeploy Service<\/li>\n
  4. Appspec file and scripts which we will talk about shortly<\/li>\n<\/ol>\n

    The above image shows the various stages and event hooks during a deployment using CodeDeploy. We define what CodeDeploy should do during all these events in a file called appspec.yml<\/strong> as mentioned in the prerequisites.
    \nAppspec file needs some scripts along with it to work. Let’s look at a simple appspec.yml file:<\/p>\n

    [js]
    \nversion: 0.0
    \nos: linux
    \nfiles:
    \n – source: \/
    \n destination: \/home\/xxuserxx\/xxcodedirectoryxx
    \nhooks:
    \n BeforeInstall:
    \n – location: apache_stop.sh
    \n timeout: 300
    \n runas: root
    \n AfterInstall:
    \n – location: afterinstall.sh
    \n timeout: 300
    \n runas: root
    \n ApplicationStart:
    \n – location: apache_start.sh
    \n timeout: 300
    \n runas: root<\/p>\n

    [\/js]<\/p>\n

    Above shown is the way you define various event hooks along with source ( the destination in the Git repository from where you want the code to be deployed, “\/” means the root directory of the repo) and destination ( the location on the server where the new code has to be placed). Each hook has a script associated with it.
    \nLink to various Hooks:<\/p>\n

    For this example, I have just used scripts for\u00a0BeforeInstall<\/strong>, AfterInstall<\/strong>, ApplicationStart<\/strong>.<\/p>\n

    BeforeInstall<\/strong>:
    \nIn BeforeInstall I have used a script (apache_stop.sh) which will run before the install step i.e. before CodeDeploy puts the code to GitHub onto a node.<\/p>\n

    [js]
    \n#!\/bin\/bash<\/p>\n

    #Stop apache service before deploying new code
    \nservice apache2 stop<\/p>\n

    mkdir -p \/home\/ubuntu\/code
    \ntar -vczf \/home\/sap\/betasite-git-backup.`date`.tar.gz \/home\/xxuserxx\/xxcodedirectoryxx
    \n#Copy current code to a directory
    \n[\/js]<\/p>\n

    This script will firstly clears the root directory where the older code is present. Reason being that CodeDeploy needs a clean directory where it has to deploy the code. Before cleaning the directory, it will also make a backup of the files. You can do any relevant changes in this step depending on your application like stop Apache or Tomcat etc. which would you need to do before the code is deployed.<\/p>\n

    After this, the Install hooks is run by AWS CodeDeploy itself where it pulls the new code from the Git Repository and places it in the destination directory.<\/p>\n

    AfterInstall<\/strong>:<\/p>\n

    Now, that CodeDeploy has placed the new code in the directory we asked it to, we can perform actions after it like compiling the code. For e.g. compiling CSS files or running some integrity tests:<\/p>\n

    [js]<\/p>\n

    cd \/home\/xxuserxx\/xxcodedirectoryxx
    \nnpm install<\/p>\n

    #GULP COMMANDS
    \ngulp scss
    \ngulp cpk-scss
    \ngulp compile<\/p>\n

    [\/js]<\/p>\n

    ApplicationStart<\/strong>:<\/p>\n

    Here, I have simply added a command that will start apache and check whether it is running or not. If Apache fails to start, obviously there are some code issues, and you will be shown an error on the console.<\/p>\n

    [js]
    \n#!\/bin\/bash<\/p>\n

    service apache2 restart
    \n[\/js]<\/p>\n

    Now, that we have the appspec.yml and the scripts handy, just push it along with the code to GitHub.
    \nRemember, appspec.yml<\/strong> should be present in the root directory of your code. and \u00a0the scripts in a folder named scripts and location of scripts should be correct in appspec.yml<\/strong><\/p>\n

    One more important thing before we move onto the console:<\/h3>\n

    AWS CodeDeploy needs a role to be able to access your AWS EC2 instances. Go to IAM and create a role having the following policy:<\/p>\n

    \n
    \n
    \n\n\n\n
    \n
    1<\/div>\n
    2<\/div>\n
    3<\/div>\n
    4<\/div>\n
    5<\/div>\n
    6<\/div>\n
    7<\/div>\n
    8<\/div>\n
    9<\/div>\n
    10<\/div>\n
    11<\/div>\n
    12<\/div>\n
    13<\/div>\n
    14<\/div>\n
    15<\/div>\n
    16<\/div>\n
    17<\/div>\n
    18<\/div>\n
    19<\/div>\n<\/td>\n
    		\n
    \n
    {<\/code><\/div>\n
    \"Version\"<\/code>: <\/code>\"2012-10-17\"<\/code>,<\/code><\/div>\n
    \u00a0<\/code>\"Statement\"<\/code>: [<\/code><\/div>\n
    \u00a0\u00a0\u00a0\u00a0<\/code>{<\/code><\/div>\n
    \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>\"Action\"<\/code>: [<\/code><\/div>\n
    \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>\"autoscaling:PutLifecycleHook\"<\/code>,<\/code><\/div>\n
    \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>\"autoscaling:DeleteLifecycleHook\"<\/code>,<\/code><\/div>\n
    \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>\"autoscaling:RecordLifecycleActionHeartbeat\"<\/code>,<\/code><\/div>\n
    \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>\"autoscaling:CompleteLifecycleAction\"<\/code>,<\/code><\/div>\n
    \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>\"autoscaling:DescribeAutoscalingGroups\"<\/code>,<\/code><\/div>\n
    \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>\"autoscaling:PutInstanceInStandby\"<\/code>,<\/code><\/div>\n
    \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>\"autoscaling:PutInstanceInService\"<\/code>,<\/code><\/div>\n
    \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>\"ec2:Describe*\"<\/code><\/div>\n
    \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>],<\/code><\/div>\n
    \u00a0\u00a0<\/code>\"Effect\"<\/code>: <\/code>\"Allow\"<\/code>,<\/code><\/div>\n
    \u00a0\u00a0<\/code>\"Resource\"<\/code>: <\/code>\"*\"<\/code><\/div>\n
    \u00a0\u00a0\u00a0\u00a0<\/code>}<\/code><\/div>\n
    \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>]<\/code><\/div>\n
    \u00a0<\/code>}<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n<\/div>\n

    With this, the Trust Relationship<\/strong> also needs to be changed in IAM, and that should now be as follows:<\/p>\n

    \n

    [js]
    \n{
    \n&quot;Version&quot;: &quot;2012-10-17&quot;,
    \n&quot;Statement&quot;: [
    \n{
    \n&quot;Sid&quot;: &quot;1&quot;,
    \n&quot;Effect&quot;: &quot;Allow&quot;,
    \n&quot;Principal&quot;: {
    \n&quot;Service&quot;: [
    \n&quot;codedeploy.us-west-2.amazonaws.com&quot;,
    \n&quot;codedeploy.us-east-1.amazonaws.com&quot;
    \n]
    \n},
    \n&quot;Action&quot;: &quot;sts:AssumeRole&quot;
    \n}
    \n]
    \n}
    \n[\/js]<\/p>\n

    Now, as I told you above in the prerequisites that the Instances on which we need to deploy the new code needs an IAM role attached to it along with a CodeDeploy agent installed on it. The policy that needs to be given to the role is:<\/p>\n

    [js]
    \n { &quot;Statement&quot;:[
    \n {&quot;Resource&quot;:&quot;*&quot;,
    \n &quot;Action&quot;: [&quot;autoscaling:Describe*&quot;,&quot;cloudformation:Describe*&quot;,&quot;s3:Get*&quot;],
    \n &quot;Effect&quot;:&quot;Allow&quot;}] }
    \n[\/js]<\/p>\n

    and Trust Relationship would be:<\/p>\n

    [js]{
    \n&quot;Version&quot;: &quot;2012-10-17&quot;,
    \n&quot;Statement&quot;: [
    \n{
    \n&quot;Sid&quot;: &quot;&quot;,
    \n&quot;Effect&quot;: &quot;Allow&quot;,
    \n&quot;Principal&quot;: {
    \n&quot;Service&quot;: &quot;ec2.amazonaws.com&quot;
    \n},
    \n&quot;Action&quot;: &quot;sts:AssumeRole&quot;
    \n}
    \n]
    \n}[\/js]<\/p>\n

    Let’s install the CodeDeploy agent on the node\/nodes now by following the below steps:<\/p>\n

    [js]sudo apt-get update
    \nsudo apt-get install awscli
    \nsudo apt-get install ruby2.0
    \ncd \/home\/ubuntu
    \nsudo aws s3 cp s3:\/\/aws-codedeploy-us-east-1\/latest\/install . –region us-east-1
    \nsudo chmod +x .\/install
    \nsudo .\/install auto
    \n[\/js]<\/p>\n

    CONSOLE STEPS<\/h2>\n

    Steps to perform in the AWS CodeDeploy Console:<\/h3>\n

    1. Go to AWS CodeDeploy and Select on Create New Application:<\/p>\n

    \"Screenshot<\/p>\n

    The above will take you to the following page where you need to give a name to your application and enter Deployment Group Name <\/strong>and\u00a0Deployment Group<\/strong> is a subset of an Application where we add instances on which we want to deploy the code.\u00a0:<\/p>\n

    \"Screenshot<\/p>\n

    2. Next, choose the Tag you want to use to filter instances to add to a Deployment Group<\/strong>. We can have different Deployment Groups within a single application. We can make another Deployment\u00a0Group later if needed and deploy different code on both of them. In a single deployment you can deploy code only to one Deployment Group:<\/p>\n

    \"Screenshot<\/p>\n

    Once that is done, we need to deploy the new code and let CodeDeploy know from where it has to pick up the code and deploy to the deployment group demo that has instance code_deploy_test in it.<\/p>\n

    3. Next, you can configure the deployment Config (which is an input that tells code deploy about the deployment strategy when you have more than one servers where the code will be deployed):
    \nFor e.g., Deploy code to one server at a time:<\/p>\n

    \"Screenshot
    \nYou have other options as well:
    \nDeploy Half at once<\/strong>: Deploys to exactly half of the servers at a time.
    \nDeploy All at once<\/strong>: Deploys to all servers at once.
    \nI prefer one at a time as any error if there is one can be detected early rather than after new code is already deployed to all the servers.<\/p>\n

    Along with that, you can also create any triggers using “Create trigger”. A simple use-case could be triggering an SNS notification which in turn could perform an action. When you click on create trigger, you would see something like:<\/p>\n

    \"Screenshot<\/p>\n

    Following\u00a0are the events triggers that CodeDeploy supports:
    \n\"Screenshot
    \nAfter selecting the event just mention the SNS topic and create the trigger. You can create multiple triggers.<\/p>\n

    After all that is done, just create the application by clicking on Create Application<\/strong>:
    \n\"codedeploy-img-1\"<\/p>\n

    4. Once that is done, you will be directed to a new page, and you should see a message like:
    \n\"Screenshot<\/p>\n

    On the same page, you will see Deployment Groups<\/strong> and Revisions:<\/strong>
    \n\"Screenshot
    \nYou can create a new Deployment Group by clicking on “Create deployment group<\/strong>“. “Revisions<\/strong>”\u00a0shows the number of times the code was deployed to this Deployment Group which of course is zero for now. If you have multiple Deployment Groups, just select it and then click on Revisions which will expand any previous deployment details. You can also revert to a previous revision of code by selecting the revision and deploying it to the Deployment Group again. All that said, let’s do our first AWS CodeDeploy deployment.<\/p>\n

    5. Select the Deployment Group and then go to “Actions<\/strong>” to select “Deploy new revision<\/strong>“:
    \n\"Screenshot<\/p>\n

    This will take you to a new page which will look something like:
    \n\"Screenshot
    \nYou just need to choose the application, and it’s respective Deployment Group and GitHub in Revision Type. Once you do that, just select “Connect with GitHub<\/strong>“. Doing that will pop up a new browser window, take you to GitHub login where you will have to enter your username and password. After that come back to this page, and you should see something like below. Just enter the remaining details and click “Deploy Now<\/strong>“:
    \n\"Screenshot<\/p>\n

    This will take you to a page as follows:
    \n\"Screenshot
    \nHere you will see details of your current deployment like Deployment ID<\/strong>, Application<\/strong>, Deployment Group<\/strong>, Revision Location<\/strong>, Start Time<\/strong>, End Time<\/strong>, Status<\/strong>, Actions<\/strong>.\u00a0You can stop your deployment from under the Actions by clicking on STOP.\u00a0<\/strong>To view the live progress of the deployment just click on the Deployment ID and it will take you to the details page where you will be able to see all the hooks being performed one by one. If the deployment is successfully completed you will see something below on the same page:
    \n\"Screenshot<\/p>\n

    6. For a successful job CodeDeploy usually does not give logs but just in case your deployment failed at any step, \u00a0you can go ahead, check the error log by clicking on “View Logs”<\/strong>, and by clicking on View in EC2 it will do nothing but take you to the AWS EC2 Management Console where and filter out the servers of the deployment group. You can ssh into the servers and check the logs in “\/var\/log\/’ directory. The below image shows what you would see during an error:
    \n\"Screenshot
    \nRemember you can’t start a deployment again from here itself. You need to go to Deployment Groups page and deploy a new revision.<\/p>\n

    So, this is how CodeDeploy works and how you can deploy your code easily using CodeDeploy on n number of servers.<\/p>\n

    You can perform all the above console steps via AWS CLI as well. Read more about it here: AWS CodeDeploy CLI<\/a>.
    \nFor now, automatic rollback is not provided as a feature, and you have to deploy a previous revision through the console manually. To get rid of that, we at TO THE NEW have been able to     automate that using AWS Lambda<\/a>. You can read about that use-case here: Automatic Rollback in AWS CodeDeploy<\/a>.<\/p>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

    The much talked about AWS CodeDeploy is being used as a daily deployment tool. According to AWS “AWS CodeDeploy coordinates application deployments to Amazon EC2 instances, on-premises instances, or both. (On-premises instances are physical devices that are not Amazon EC2 instances.)” On-premise support came in mid-2015. AWS CodeDeploy has been the choice of many since […]<\/p>\n","protected":false},"author":174,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":38},"categories":[1174,2348,1],"tags":[248,1676,3884,3878,3879,3881,3883,3880,3877,3882],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/27240"}],"collection":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/users\/174"}],"replies":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/comments?post=27240"}],"version-history":[{"count":1,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/27240\/revisions"}],"predecessor-version":[{"id":54512,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/27240\/revisions\/54512"}],"wp:attachment":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/media?parent=27240"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/categories?post=27240"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/tags?post=27240"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}