{"id":3187,"date":"2017-07-19T07:13:09","date_gmt":"2017-07-19T07:13:09","guid":{"rendered":"http:\/\/cloudkul.com\/blog\/?p=3187"},"modified":"2017-07-19T07:13:09","modified_gmt":"2017-07-19T07:13:09","slug":"code-deployment-using-aws-codedeploy","status":"publish","type":"post","link":"https:\/\/cloudkul.com\/blog\/code-deployment-using-aws-codedeploy\/","title":{"rendered":"Code Deployment Using AWS CodeDeploy"},"content":{"rendered":"

In the previous blog<\/a>, we learnt about CodeDeploy service of AWS and how it is useful in simplifying the Code deployment process. It is used to automate application deployments to the Amazon EC2 instances or on-premises instances in our data-centers. AWS CodeDeploy can deploy application content stored in Amazon S3 buckets, GitHub repositories, or Bitbucket repositories. So let’s learn how to setup the environment and deploy our code using the CodeDeploy service.<\/p>\n

The various steps involved to configure and use the CodeDeploy service can be summarized in the following steps.<\/p>\n

    \n
  1. Creating IAM roles.<\/li>\n
  2. Configuring the servers\/Instances where code is to be deployed.<\/li>\n
  3. Uploading files or codes in either github or S3.<\/li>\n
  4. Creating Deployment Configurations in AWS CodeDeploy.<\/li>\n
  5. Deploying the Code.<\/li>\n<\/ol>\n

     <\/p>\n

     <\/p>\n

    Step-1: Creating IAM roles :<\/strong><\/h3>\n

     <\/p>\n

    The first step to setup an environment for CodeDeploy is to create an IAM role. Here, we will be creating two types of roles –<\/p>\n

      \n
    1. IAM role for Instance Profile.<\/li>\n
    2. IAM role for Service Profile.<\/li>\n<\/ol>\n

      Instance Profile<\/span><\/em> :-<\/strong> Instance Profile is a container for IAM roles and can provide the role’s credentials to an application running on that instance. Those credentials can then be used in the application’s API calls to access resources and to limit access to only those resources that the role specifies. These role credentials are temporary and rotated automatically improving the security. Only one Instance Profile can be attached to a particular Instance. The “Instance Profile” has the same name as the “IAM Instance Role” by default when you create it from the AWS console. However, when you create it from aws-cli, Instance role and Instance Profile role can be different.<\/p>\n

      Service Profile<\/span><\/em> :-<\/strong> Service Profile consist of roles containing permission that allows ClodeDeploy to use other AWS services.<\/p>\n

       <\/p>\n

      Creating Instance Profile :<\/strong><\/p>\n

      So, lets create both Instance role and Service role one by one. First login to your AWS console and open the IAM service.<\/p>\n

      On left side of the IAM console page, click on the roles. Now click on “create new role<\/strong>” option on top. Now select the role type as “Amazon EC2<\/strong>” from the options list. Next, select the following policies:<\/p>\n

      a).<\/strong> AmazonEC2RoleforAWSCodeDeploy<\/strong> ->> This allows EC2 instance under CodeDeploy To Access S3 service.<\/p>\n

      b). AutoScalingNotificationAccessRole <\/strong> ->> This allows EC2 instance under CodeDeploy to access SNS and SQS.<\/p>\n

      And finally give the Instance Role a name. I will use the name “CodeDeployInstanceRole<\/strong>” as Instance Role for this demo. This role will be attached to the instance on which deployment is to be done.<\/p>\n

       <\/p>\n

      Creating Service Profile :<\/strong><\/p>\n

      Similarly, create a new Service role for CodeDeploy. Click on “create new role<\/strong>” option on top. Now select the role type as ” AWS CodeDeploy<\/strong> ” from the options list. Next, select the following policies:<\/p>\n

      a). AWSCodeDeployRole <\/strong> ->> This allows CodeDeploy to access other AWS services like Autoscaling\/ec2\/SNS.<\/p>\n

      And finally give the Service Role a name. I will use the name “CodeDeployServiceRole<\/strong>” for this demo. This role will be used while creating Deployment configurations in CodeDeploy .<\/p>\n

      By now, you have successfully created the two required IAM roles.<\/p>\n

       <\/p>\n

      Step-2:- Configuring the servers\/Instances :<\/strong><\/h3>\n

       <\/p>\n

      The second step is to configure the instances on which we want to deploy code using the CodeDeploy service. Configuring the instances involve two major steps:<\/p>\n

        \n
      1. Attaching the IAM role.<\/li>\n
      2. Installing “Code Deploy Agent” on the instance.<\/li>\n<\/ol>\n

        However, if you want to launch a new instance in AWS, the Instance IAM role can be attached at the time of launching the instance. During the launching of the instance, in the third step which is “Configure Instance”, find the section “IAM role” and select the created IAM role\u00a0“CodeDeployInstanceRole”<\/strong> from the drop-down list. For an already running instance, you can attach the role using AWS CLI.<\/p>\n

         <\/p>\n

        Now let us configure our instance. You can configure instances either present on AWS or on-Premises. In this demo, we will be using AWS instances using apache web-server.<\/p>\n

        First login to your server, and run the following commands as a root user.<\/p>\n

         <\/p>\n

        For Ubuntu Or Debian:-<\/strong><\/p>\n

        Update your server and install apache web-server.<\/p>\n

        apt-get update\r\napt-get install apache2 -y<\/pre>\n
        Download and install the “code deploy agent”. First install ruby and wget packages as the agent is ruby based.<\/p>\n
        apt-get install ruby wget -y<\/pre>\n
        Now download and install the agent. Replace “$REGION” with your present AWS Region name for example “us-east-2”.<\/p>\n
        wget https:\/\/aws-codedeploy-$REGION.s3.amazonaws.com\/latest\/install\r\nchmod +x .\/install\r\n.\/install auto<\/pre>\n
        Check if the code deploy agent is installed and running on your instance.<\/p>\n
        ps -aux | grep agent<\/pre>\n
        Next step is to install “AWS CLI” on the instance. AWS CLI is python based API. Use pip package manager to install aws-cli package. To install pip and aws-cli, use the following commands.<\/p>\n
        apt-get install python-pip\r\npip install --upgrade pip\r\npip install awscli\r\npip install --upgrade awscli\r\naws --version<\/pre>\n
         <\/p>\n
         <\/p>\n
        For RHEL Distibutions like Centos, Amazon AMI, etc :-<\/strong><\/p>\n
        Update your server and install apache web-server.<\/p>\n
        yum update\r\nyum install httpd -y\r\n<\/pre>\n
        Download and install epel repository.<\/p>\n
        yum install wget -y\r\nwget http:\/\/dl.fedoraproject.org\/pub\/epel\/7\/x86_64\/e\/epel-release-7-10.noarch\r\nrpm -ivh epel-release-7-10.noarch.rpm  #Install epel repository\r\nyum repolist                           #To check if the repo is installed\r\n<\/pre>\n
        Install code-deploy-agent in your instance. Replace “$REGION” with your present AWS Region name for example “us-east-2”.<\/p>\n
        yum install ruby -y\r\nwget https:\/\/aws-codedeploy-$REGION.s3.amazonaws.com\/latest\/install\r\nchmod +x .\/install\r\n.\/install auto\r\n<\/pre>\n
        Install “AWS CLI” on the instance. AWS CLI is python based API. Use pip package manager to install aws-cli package. To install pip and aws-cli, use the following commands.<\/p>\n
        yum install python-pip \u2013y \r\npip install --upgrade pip \r\npip install awscli \r\npip install --upgrade awscli \r\naws --version<\/pre>\n
         <\/p>\n
         <\/p>\n
        [COMMON COMMANDS FOR DEBIAN AND RHEL DISTRIBUTIONS]<\/em><\/strong><\/p>\n
        Configure aws-cli with appropriate credentials to enable it to access the AWS resources.<\/p>\n
        aws configure<\/pre>\n
         <\/p>\n
        Enter your Access Key or Secret Key and you can skip the default region and output format options by pressing enter. If you don’t have previous Access key, you can generate new key pairs. To Get Your AWS Access Key And Secret Keys, click on drop-down arrow, near the AWS Account Name displayed on top of the AWS console. From the options select My security credientials. If asked Select Continue to security credientials. On the “Your Security Credentials” page that appears, Select “Access Keys (Access Key ID and Secret Access Key)” and then Click on “Create New Access Key”. Download the Access key that is created. You can also view the access key and secret key on the console.<\/p>\n
        AWS Access Key ID [None] : Enter_Your_Access_Key\r\nAWS Secret Access Key [None] : Enter_your_Secret_key\r\nDefault region name [None] : Specify_your_region or Press_Enter_to_Skip\r\nDefault output format [None] : json or Press_Enter_to_Skip<\/pre>\n
         <\/p>\n
        Once your aws-cli is properly configured, you can attach the instance profile with the following command. Specify your instance ID and instance profile name\u00a0 “CodeDeployInstanceRole” which we previously created.<\/p>\n
        aws ec2 associate-iam-instance-profile --instance-id <Your_Instance_ID> --iam-instance-profile Name=CodeDeployInstanceRole<\/pre>\n
        You can check the all the Instance Profiles attached to various instances using the below commands.<\/p>\n
        aws ec2 describe-iam-instance-profile-associations<\/pre>\n
        If you can see your instance attached with your Instance Profile, then your instance is attached with Instance Profile containing IAM role.<\/p>\n
         <\/p>\n
        Remember to reboot your server after configuration if you have attached your “IAM Instance role” to an existing instance. Reboot is not required if you have attached the “Instance role” at the time of launching the instance.<\/p>\n
         <\/p>\n
        Step-3 :\u00a0 Uploading files or codes in either github or S3 :<\/strong><\/h3>\n
         <\/p>\n
        The Third step is to prepare your code for deployment. You can either deploy your code from github or S3 bucket.<\/p>\n
        However to use CodeDeploy, you need to include two things along with your code.<\/p>\n
          \n
        1. appspec.yml file<\/li>\n
        2. deployment scripts<\/li>\n<\/ol>\n
          The application specification file (AppSpec file) is a\u00a0YAML-formatted file used by AWS CodeDeploy to determine:<\/p>\n
          \n