{"id":37398,"date":"2017-12-06T15:03:55","date_gmt":"2017-12-06T15:03:55","guid":{"rendered":"https:\/\/www.whizlabs.com\/?p=37398"},"modified":"2024-05-17T12:20:44","modified_gmt":"2024-05-17T06:50:44","slug":"working-with-code-deploy","status":"publish","type":"post","link":"https:\/\/www.whizlabs.com\/blog\/working-with-code-deploy\/","title":{"rendered":"Working with Code Deploy"},"content":{"rendered":"

Exam Objective<\/b><\/h2>\n

This topic “Working with Code Deploy” addresses the Continuous Delivery and Process Automation topic as highlighted in the AWS Blueprint for the exam guide<\/p>\n

https:\/\/d0.awsstatic.com\/training-and-certification\/docs-devops-pro\/AWS_certified_devops_engineer_professional_blueprint.pdf<\/a><\/p>\n

Code Deploy is a service that helps with the Continuous deployment process. It can be used to deploy code either on EC2 Instances or on on-premise infrastructure. In the deployment, you can do either an in-place deployment or a Blue Green Deployment<\/a>.<\/p>\n

In the in-place deployment, each instance in your deployment group is stopped, the latest version of your code is installed and then the application is started and validated. You can also have the instances sitting behind a load balancer.<\/p>\n

\"\"<\/a><\/p><\/blockquote>\n

In the Blue green environment, Code Deploy can create a new environment which can be switched over once the new version of the application is ready for the deployed to the new environment.<\/p>\n

How does Code Deploy work?<\/b><\/h2>\n

The below snapshot from the AWS documentation shows the structure of the Code Deploy service<\/p>\n

\"Working<\/p>\n

The different parts of CodeDeploy are as follows<\/p>\n

1) You first ensure that your code is available for deployment. The code package must also contain a file called appspec.yml. This AppSpec file is specific to AWS Code Deploy. It tells Code Deploy how to deploy the package to the underlying Instances.<\/p>\n

2) You then submit this as a release Code Deploy from either Github or from an S3 bucket.<\/p>\n

3) The code gets deployed to EC2 Instances which are put as part of a deployment Group. These EC@ instances need to have Code Deploy agents running on them. The agents in the EC2 Instances deployment group then polls Code Deploy and gets the details of the code to pull in.<\/p>\n

You can have deployment groups for various stacks in your organization as shown below from the AWS documentation.<\/p>\n

\"Deployment<\/p>\n

Implementing Code Deploy<\/b><\/h4>\n

Now let\u2019s look at an example of how we can use Code Deploy<\/p>\n

In our example, we are going to deploy a simple HTML file(Demo.html) to a set of 2 EC2 Instances. The Instances will have a tag of Name=staging. This is required to classify the instances as part of a deployment group. The instances will have the nginx server deployed. This will be used to host the HTML file. The server can be installed as part of the User Data section of the EC2 Instance is required. You then need to upload the HTML file and the appspec.yml file to an S3 bucket as a zip file. Here is the appspec.yml file.<\/p>\n

version:<\/strong> 0.0<\/p>\n

os:<\/strong> Linux<\/p>\n

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