{"id":1930,"date":"2020-10-30T10:53:58","date_gmt":"2020-10-30T09:53:58","guid":{"rendered":"https:\/\/blog.besharp.it\/?p=1930"},"modified":"2021-05-10T15:48:31","modified_gmt":"2021-05-10T13:48:31","slug":"how-to-setup-a-continuous-deployment-pipeline-on-aws-for-ecs-blue-green-deployments","status":"publish","type":"post","link":"https:\/\/blog.besharp.it\/how-to-setup-a-continuous-deployment-pipeline-on-aws-for-ecs-blue-green-deployments\/","title":{"rendered":"How to setup a Continuous Deployment Pipeline on AWS for ECS Blue\/Green Deployments."},"content":{"rendered":"\n<p><span style=\"font-weight: 400;\">Continuous Deployment is nowadays a well-known strategy for releasing software where any commit that passes the automated testing phase is automatically released into the production deployment.<\/span><\/p>\n\n\n\n<p>With Continuous Deployment, companies can eliminate DIY for Continuous Delivery and increase the focus on the product, make deployments frictionless without compromising security, and creating a flawless workflow across development, testing, and production environments.<\/p>\n\n\n\n<p><span style=\"font-weight: 400;\">In our <\/span><span style=\"font-weight: 400;\"><a href=\"https:\/\/blog.besharp.it\/en\/ecs-deployment-strategies-reduce-downtime-and-risk-with-blue-green-deployment\/\">last article<\/a>,<\/span><span style=\"font-weight: 400;\"> we talked about Microservices, their benefits, and how to set up a Blue\/Green Deployment on AWS for an ECS Service. <\/span><\/p>\n\n\n\n<p>Blue\/Green Deployment is a technique where both the old infrastructure (blue) and the new temporary infrastructure (green) co-exist. Once a new version is installed, it is possible to carry out integration\/validation tests on the green infrastructure before promoting it to production. If so, the traffic switch can be done with virtually no downtime. \n<\/p>\n\n\n\n<p><span style=\"font-weight: 400;\">This time we want to take another step forward from our last article and, as promised, show how to make the process automatic, by defining a pipeline for Continuous Deployment to manage the entire release flow.<\/span>\n\n<span style=\"font-weight: 400;\">In short, from a simple <\/span><i><span style=\"font-weight: 400;\">git push,<\/span><\/i><span style=\"font-weight: 400;\"> we want to release the new software package in Blue\/Green mode through an ECS service.<\/span><\/p>\n\n\n\n<p><span style=\"font-weight: 400;\">In the end, we\u2019ll also propose to you two bonus sections: how to automate testing on green environments and how it is possible to skip some initial infrastructure\u2019s boilerplate creation thanks to AWS CloudFormation.<\/span><\/p>\n\n\n\n<p> Are you ready? Let\u2019s dig in!<\/p>\n\n\n\n<h1 class=\"wp-block-heading\">Requirements<\/h1>\n\n\n\n<p>Before start preparing your pipeline some steps must be done in order to have everything in place, ready to be configured to your needs:\n<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>Having a GitHub repository up and running where you can save your code and trigger your pipeline.<\/li><li>Having a role with CodeDeploy permissions that grants AWS CodeDeploy access to your target instances.<\/li><li>Having a Docker image ready with a simple express app for ECR.<\/li><li>Having an ECS cluster, an ECS service, and a Task Definition ready on your Account in AWS.<\/li><\/ul>\n\n\n\n<p><span style=\"font-weight: 400;\">Note: following are simplified steps to cover the last prerequisite; for more in-depth instructions, follow the steps provided in our <\/span><a href=\"https:\/\/blog.besharp.it\/en\/ecs-deployment-strategies-reduce-downtime-and-risk-with-blue-green-deployment\/\"><span style=\"font-weight: 400;\">previous article<\/span><\/a><span style=\"font-weight: 400;\">.<\/span><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Create a new ECS Cluster<\/h2>\n\n\n\n<p>Go to your AWS account, select ECS in the search bar and after that click on \u201cClusters\u201d in the left panel and \u201cCreate Cluster\u201d in the new window. Leave \u201cNetworking only\u201d as an option since we want to use Fargate and click \u201cnext\u201d.<\/p>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"387\" height=\"369\" src=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-70.png\" alt=\"select cluster template\" class=\"wp-image-1883\" srcset=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-70.png 387w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-70-315x300.png 315w\" sizes=\"auto, (max-width: 387px) 100vw, 387px\" \/><\/figure><\/div>\n\n\n\n<p>Type your cluster name, leave all settings as default and finally add some meaningful tags if you want. Click \u201cCreate\u201d to generate a new blank cluster.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Create a new Task Definition<\/h2>\n\n\n\n<p>Another prerequisite is the Task Definition, which will host our Docker containers.<\/p>\n\n\n\n<p>Go to \u201cTask Definitions\u201d under  \u201cAmazon ECS\u201d menu, then click \u201cCreate new Task Definition\u201d and select \u201cFargate\u201d as the image below and click \u201cNext Step\u201d:\n<\/p>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"850\" height=\"730\" src=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-71.png\" alt=\"create task definition\" class=\"wp-image-1885\" srcset=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-71.png 850w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-71-349x300.png 349w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-71-768x660.png 768w\" sizes=\"auto, (max-width: 850px) 100vw, 850px\" \/><\/figure><\/div>\n\n\n\n<p>For now, we can assign the default roles to both the Task Role and the Task Execution Role since they are sufficient for the operations we have to perform. Select the minimum values for Memory and Cpu (0.5GB and 0.25vCPU for this example).<\/p>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"579\" height=\"1024\" src=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-72-579x1024.png\" alt=\"task definition parameters\" class=\"wp-image-1886\" srcset=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-72-579x1024.png 579w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-72-170x300.png 170w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-72-768x1359.png 768w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-72-868x1536.png 868w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-72.png 904w\" sizes=\"auto, (max-width: 579px) 100vw, 579px\" \/><\/figure><\/div>\n\n\n\n<p><span style=\"font-weight: 400;\">We then create a container and associate it with the Docker image, previously saved on ECR (see the <\/span><a href=\"https:\/\/blog.besharp.it\/en\/ecs-deployment-strategies-reduce-downtime-and-risk-with-blue-green-deployment\/\"><span style=\"font-weight: 400;\">last article<\/span><\/a><span style=\"font-weight: 400;\">), appropriately configuring the vCPU and the memory with the same values as our task definition. <\/span><\/p>\n\n\n\n<p>Select \u201cAdd Container\u201d.<\/p>\n\n\n\n<p><span style=\"font-weight: 400;\">&nbsp;A sidebar will open. Set a name for the container and for the Image Uri, open a new Tab, and navigate to ECR dashboard, select your previously created image and copy its URI value. Assign the value to \u201cImage URI\u201d.<\/span><\/p>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"202\" src=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-73-1024x202.png\" alt=\"image uri value\" class=\"wp-image-1888\" srcset=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-73-1024x202.png 1024w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-73-400x79.png 400w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-73-768x152.png 768w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-73-1536x303.png 1536w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-73.png 1550w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure><\/div>\n\n\n\n<p><span style=\"font-weight: 400;\">Then add <\/span><b>3000<\/b><span style=\"font-weight: 400;\"> for <\/span><b>tpc protocol<\/b><span style=\"font-weight: 400;\"> in \u201cPort mapping\u201d, leave all other parameters as default and click \u201cAdd\u201d. Finally, save your task definition with \u201cCreate\u201d.<\/span><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Create a new Service<\/h2>\n\n\n\n<p>Start by going to your created Cluster in ECS service, click on its name and in the bottom area of the dashboard, under the \u201cService\u201d tab, click \u201cCreate\u201d.<\/p>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"772\" height=\"208\" src=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-74.png\" alt=\"create ecs service\" class=\"wp-image-1891\" srcset=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-74.png 772w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-74-400x108.png 400w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-74-768x207.png 768w\" sizes=\"auto, (max-width: 772px) 100vw, 772px\" \/><\/figure><\/div>\n\n\n\n<p>In the new area, configure the options as following:<\/p>\n\n\n\n<p>1. Launch Type: <strong>FARGATE<\/strong><\/p>\n\n\n\n<p>2. Task Definition: <strong>&lt;YOUR_TASK_DEFINITION&gt;<\/strong><\/p>\n\n\n\n<p>3. Cluster: <strong>&lt;YOUR_CLUSTER&gt;<\/strong><\/p>\n\n\n\n<p>4. Service Name: <strong>&lt;A_NAME_FOR_THE_SERVICE&gt;<\/strong><\/p>\n\n\n\n<p>5. Number of Tasks: <strong>1<\/strong><\/p>\n\n\n\n<p>6. Deployment Type: <strong>Blue\/Green<\/strong><\/p>\n\n\n\n<p>7. Deployment Configuration: <strong>CodeDeployDefault.ECSAllAtOnce<\/strong><\/p>\n\n\n\n<p>8. Service Role for CodeDeploy: <strong>&lt;A_SUITABLE_ROLE_WITH_ECS_PERMISSIONS&gt;<\/strong><\/p>\n\n\n\n<p>Leave the rest of the options as default and click \u201cNext Step\u201d. In the new section select a suitable VPC, one or more of its subnets and auto-assign IP enabled.\n<\/p>\n\n\n\n<p>Then we need to configure an Application LoadBalancer for our cluster. Select an existing one or create a new one from the EC2 console. Then select your container, being sure that it shows your mapped port.<\/p>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"763\" src=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-75-1024x763.png\" alt=\"configure Application LoadBalancer\" class=\"wp-image-1892\" srcset=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-75-1024x763.png 1024w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-75-400x298.png 400w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-75-768x573.png 768w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-75.png 1430w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure><\/div>\n\n\n\n<p>After selecting your container click \u201cAdd to load balancer\u201d. <\/p>\n\n\n\n<p><span style=\"font-weight: 400;\">Select <\/span><b>8080<\/b><span style=\"font-weight: 400;\"> for \u201cProduction Listener Port\u201d and <\/span><b>8090 <\/b><span style=\"font-weight: 400;\">for \u201cTest Listener Port\u201d, select your LoadBalancer\u2019s target group as shown in figure (you\u2019ll have to configure them beforehand or now in another tab following <a href=\"https:\/\/docs.aws.amazon.com\/elasticloadbalancing\/latest\/application\/create-application-load-balancer.html\" target=\"_blank\" rel=\"noopener noreferrer\">this guide.<\/a><\/span><\/p>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"952\" height=\"1024\" src=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-76-952x1024.png\" alt=\"select LoadBalancer\u2019s target group\" class=\"wp-image-1896\" srcset=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-76-952x1024.png 952w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-76-279x300.png 279w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-76-768x826.png 768w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-76-1428x1536.png 1428w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-76.png 1487w\" sizes=\"auto, (max-width: 952px) 100vw, 952px\" \/><\/figure><\/div>\n\n\n\n<p>After that, you can go to the next step and leave autoscaling off (for this example). Finally, after the review check, your service will be created!\n<\/p>\n\n\n\n<p>Now we have all the fundamental bricks to create the Pipeline process in CodePipeline. Let\u2019s move on!\n<\/p>\n\n\n\n<h1 class=\"wp-block-heading\">Create the Deployment Pipeline<\/h1>\n\n\n\n<p>Start by having your sample application pushed on your GitHub repository.<\/p>\n\n\n\n<p>Go to your AWS Account, select AWS CodePipeline from the services list. From the dashboard click on \u201cCreate pipeline\u201d.\n<\/p>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"156\" src=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-77-1024x156.png\" alt=\"Create Deployment Pipeline\" class=\"wp-image-1898\" srcset=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-77-1024x156.png 1024w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-77-400x61.png 400w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-77-768x117.png 768w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-77.png 1220w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure><\/div>\n\n\n\n<p>In the next screen give a name to your pipeline and if you don\u2019t already have a suitable role, leave \u201cNew service role\u201d checked and the other options as defaults; click \u201cnext\u201d.\n<\/p>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"552\" src=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-78-1024x552.png\" alt=\"pipeline settings\" class=\"wp-image-1900\" srcset=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-78-1024x552.png 1024w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-78-400x216.png 400w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-78-768x414.png 768w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-78-1536x829.png 1536w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-78.png 1598w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure><\/div>\n\n\n\n<p><span style=\"font-weight: 400;\">In the <\/span><b>source<\/b><span style=\"font-weight: 400;\"> stage select \u201cGitHub version 2\u201d and then you have to connect to your GitHub repository. Please follow the instructions provided after clicking on \u201cConnect to GitHub\u201d. Remember to <\/span><b>authorize only the repository of your solution <\/b><span style=\"font-weight: 400;\">and to be the <\/span><b>owner of that repo,<\/b><span style=\"font-weight: 400;\"> otherwise you won\u2019t be able to complete the process.<\/span><\/p>\n\n\n\n<p>After being connected to GitHub, you\u2019ll be able to complete the stage as follows, setting repository and branch:\n<\/p>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"975\" src=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-79-1024x975.png\" alt=\"github repository and branch\" class=\"wp-image-1904\" srcset=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-79-1024x975.png 1024w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-79-315x300.png 315w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-79-768x731.png 768w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-79-1536x1463.png 1536w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-79.png 1592w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure><\/div>\n\n\n\n<p>Click \u201cnext\u201d, and you\u2019ll be presented with the build stage where we need to create our CodeDeploy project to add to the pipeline.\n<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Create a new CodeBuild project<\/h2>\n\n\n\n<p>In order to keep your code always up to date in the pipeline, you need to make this step to always generate an updated docker image for your codebase. \n<\/p>\n\n\n\n<p><span style=\"font-weight: 400;\">Start by giving a name to your <\/span><b>Build stage<\/b><span style=\"font-weight: 400;\">, select <\/span><b>CodeBuild<\/b><span style=\"font-weight: 400;\"> as the \u201cAction provider\u201d, the region, and <\/span><b>SourceArtifact <\/b><span style=\"font-weight: 400;\">as the \u201cInput Artifact\u201d.<\/span><\/p>\n\n\n\n<p><span style=\"font-weight: 400;\">Then you need to create a new build project. Clicking on \u201cAdd project\u201d will bring a screen similar to this:<\/span><\/p>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"844\" src=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-80-1024x844.png\" alt=\"new build project\" class=\"wp-image-1906\" srcset=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-80-1024x844.png 1024w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-80-364x300.png 364w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-80-768x633.png 768w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-80-1536x1265.png 1536w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-80.png 1600w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure><\/div>\n\n\n\n<p><span style=\"font-weight: 400;\">Give a name to the project, then leave <\/span><b>Managed Image<\/b><span style=\"font-weight: 400;\"> with all the container properties as suggested, then <\/span><b>check <\/b><span style=\"font-weight: 400;\">(this is very important) the \u201cPrivileged option\u201d in order to allow building your docker image. Check your settings with the image below:<\/span><\/p>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"934\" src=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-81-1024x934.png\" alt=\"environment image docker\" class=\"wp-image-1909\" srcset=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-81-1024x934.png 1024w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-81-329x300.png 329w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-81-768x701.png 768w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-81-1536x1402.png 1536w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-81.png 1600w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure><\/div>\n\n\n\n<p><span style=\"font-weight: 400;\">For the <\/span><b>buildspec<\/b><span style=\"font-weight: 400;\"> option, select the inline editor and paste these commands:<\/span><\/p>\n\n\n\n<pre>version: 0.2\nphases:\n pre_build:\n   commands:\n     - REPOSITORY_URI=<b>YOU_ECR_URI<\/b>\n     - echo $CODEBUILD_RESOLVED_SOURCE_VERSION      - COMMIT_HASH=$(echo $CODEBUILD_RESOLVED_SOURCE_VERSION)\n     - IMAGE_TAG=${COMMIT_HASH}:latest\n     - $(aws ecr get-login --no-include-email --region <b>YOUR_REGION<\/b>)\n install:\n   runtime-versions:\n     java: corretto11\n build:\n   commands:\n   - printf '{\"ImageURI\":\"%s\"}' $REPOSITORY_URI:latest &gt; imageDetail.json\n   - docker build -t <b>YOU_ECR_URI<\/b>:latest .\n   - docker push <b>YOU_ECR_URI<\/b>:latest\nartifacts:\nfiles: imageDetail.json\n<\/pre>\n\n\n\n<p><\/p>\n\n\n\n<p>Note: in bold there are the variables you need to customize yourself to your specific project.\n<\/p>\n\n\n\n<p>After that, click ok, then add this CodeBuild project to your stage. \n<\/p>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"934\" src=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-82-1024x934.png\" alt=\"environment image docker step 2\" class=\"wp-image-1911\" srcset=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-82-1024x934.png 1024w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-82-329x300.png 329w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-82-768x701.png 768w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-82-1536x1402.png 1536w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-82.png 1600w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure><\/div>\n\n\n\n<h2 class=\"wp-block-heading\">Create a new CodeDeploy project<\/h2>\n\n\n\n<p>Start by selecting \u201cAmazon ECS (Blue\/Green)\u201d for Deploy provider, a region for your project, and then click on \u201cCreate application\u201d.\n<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"381\" src=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-83-1024x381.png\" alt=\"new codedeploy project\" class=\"wp-image-1913\" srcset=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-83-1024x381.png 1024w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-83-400x149.png 400w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-83-768x286.png 768w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-83.png 1328w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<p>Give a new name to the project and select \u201cAmazon ECS\u201d as a Compute provider. After that, you\u2019ll be presented with a screen for creating a new Deployment group. <\/p>\n\n\n\n<p>Give a name to the Deployment group than select in order:<\/p>\n\n\n\n<p>A service role with suitable access.<\/p>\n\n\n\n<p>The ECS cluster we have created before<\/p>\n\n\n\n<p>The ECS service we have created before<\/p>\n\n\n\n<p>The Application load balancer we have created before with 8080 and TargetGroup 1 for production and 8090 and TargetGroup 2 for test environments respectively.<\/p>\n\n\n\n<p><span style=\"font-weight: 400;\">Select a traffic strategy; for this example use \u201cSpecify when to reroute traffic\u201d and select <strong>five minutes<\/strong>.<\/span><\/p>\n\n\n\n<p><span style=\"font-weight: 400;\">Click \u201cCreate\u201d and then return to your CodePipeline stage and select your newly created <\/span><b>CodeDeploy application<\/b><span style=\"font-weight: 400;\"> and <\/span><b>CodeDeploy deployment group<\/b><span style=\"font-weight: 400;\">.<\/span><\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"298\" src=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-84-1024x298.png\" alt=\"CodeDeploy project settings\" class=\"wp-image-1915\" srcset=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-84-1024x298.png 1024w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-84-400x116.png 400w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-84-768x223.png 768w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-84.png 1148w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<p>Per \u201cInput Artifacts\u201d aggiungiamo <strong>BuildArtifact<\/strong> affianco a \u201cSourceArtifact\u201d.<\/p>\n\n\n\n<p><span style=\"font-weight: 400;\">For <\/span><b>Amazon ECS task definition<\/b><span style=\"font-weight: 400;\"> and <\/span><b>AWS CodeDeploy AppSpec file<\/b><span style=\"font-weight: 400;\"> select \u201cSource Artifact\u201d; then add BuildArtifact and IMAGE as the last options. Click \u201cNext\u201d, review and finally \u201cCreate pipeline\u201d.<\/span><\/p>\n\n\n\n<p><span style=\"font-weight: 400;\">We are almost there! To complete our pipeline we need to add a <\/span><b>task definition<\/b><span style=\"font-weight: 400;\"> and an <\/span><b>appspec.yml<\/b><span style=\"font-weight: 400;\"> to our application.<\/span><\/p>\n\n\n\n<p><span style=\"font-weight: 400;\">Create a new <\/span><b>appspec.yml<\/b><span style=\"font-weight: 400;\"> file in the root of your app\u2019s project and add the following code to it:<\/span><\/p>\n\n\n\n<pre>version: 0.0\nResources:\n - TargetService:\n     Type: AWS::ECS::Service\n     Properties:\n       TaskDefinition: &lt;task_definition&gt;\n       LoadBalancerInfo:\n         ContainerName: \"<b>YOUR_ECS_CLUSTER_NAME<\/b>\"\n         ContainerPort: 3000\n\n<\/task_definition><\/pre>\n\n\n\n<p>For the task definition file we can use a trick:<\/p>\n\n\n\n<p><span style=\"font-weight: 400;\">we have already created a task definition in the prerequisites: go find it and click on \u201cEdit\u201d, you\u2019ll find a JSON editor, copy all text from there and paste it in a new <\/span><b>taskdef.json <\/b><span style=\"font-weight: 400;\">file in the root of your project and change these two lines:<\/span><span style=\"font-weight: 400;\">\n<\/span><\/p>\n\n\n\n<pre>\"image\": \"&lt;IMAGE&gt;\"\n\"taskDefinitionArn\": \"&lt;TASK_DEFINITION&gt;\"<\/pre>\n\n\n\n<p>Push everything on your repo.<\/p>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"994\" height=\"512\" src=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-85.png\" alt=\"create task definition\" class=\"wp-image-1918\" srcset=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-85.png 994w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-85-400x206.png 400w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-85-768x396.png 768w\" sizes=\"auto, (max-width: 994px) 100vw, 994px\" \/><\/figure><\/div>\n\n\n\n<p>Test your application before promoting to Production<\/p>\n\n\n\n<p>To verify that all the system is working as expected just make a slight modification to the text on the main route of your application, commit, wait until the pipeline finishes its tasks, and then check your URL with port 8090 and verify that presents the updated version while URL with port 8080 not. Wait for 5-6 minutes and then also the production environment should show the correct new version. \n<\/p>\n\n\n\n<p>Your pipeline is now fully functional!<\/p>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"364\" src=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-86-1024x364.png\" alt=\"test your Pipeline\" class=\"wp-image-1919\" srcset=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-86-1024x364.png 1024w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-86-400x142.png 400w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-86-768x273.png 768w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-86-1536x546.png 1536w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/unnamed-86.png 1600w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure><\/div>\n\n\n\n<p><span style=\"font-weight: 400;\">Bonus 1: apply automated testing through Lambda on your Green environment<\/span><\/p>\n\n\n\n<p>In the deploy phase, it is possible to associate one or more Lambda functions to assert the health and the functionalities of your app before promoting the new version to production. This is done during the configuration of your Deployment lifecycle hooks. You\u2019ll need to add a Lambda hook to AfterAllowTraffic.\n<\/p>\n\n\n\n<p>Please refer to these guides by AWS to configure this extra touch with a simple test example:<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li><a href=\"https:\/\/docs.aws.amazon.com\/codedeploy\/latest\/userguide\/tutorial-ecs-deployment-with-hooks.html\" target=\"_blank\" rel=\"noreferrer noopener\">https:\/\/docs.aws.amazon.com\/codedeploy\/latest\/userguide\/tutorial-ecs-deployment-with-hooks.html<\/a><\/li><\/ul>\n\n\n\n<ul class=\"wp-block-list\"><li><a href=\"https:\/\/docs.aws.amazon.com\/codedeploy\/latest\/userguide\/tutorial-ecs-with-hooks-create-hooks.html\" target=\"_blank\" rel=\"noreferrer noopener\">https:\/\/docs.aws.amazon.com\/codedeploy\/latest\/userguide\/tutorial-ecs-with-hooks-create-hooks.html<\/a><\/li><\/ul>\n\n\n\n<h1 class=\"wp-block-heading\">Bonus 2: automate prerequisite phase through CloudFormation<\/h1>\n\n\n\n<p>We have checked the prerequisites necessary to create an ECS cluster and its components but as we have seen this section needs a lot of configuration and can be tedious and nonetheless we want it to be repeatable.<\/p>\n\n\n\n<p>Therefore a good idea would be to create a CloudFormation template to automate and simplify the infrastructure creation process.<\/p>\n\n\n\n<p>The following is a simplified snippet to guide you to get started with it.<\/p>\n\n\n\n<pre>LoadBalancer:\n   Type: AWS::ElasticLoadBalancingV2::LoadBalancer\n   Properties:\n     Name: !Ref ProjectName\n     LoadBalancerAttributes:\n       - Key: 'idle_timeout.timeout_seconds'\n         Value: '60'\n       - Key: 'routing.http2.enabled'\n         Value: 'true'\n       - Key: 'access_logs.s3.enabled'\n         Value: 'true'\n       - Key: 'access_logs.s3.prefix'\n         Value: loadbalancers\n       - Key: 'access_logs.s3.bucket'\n         Value: !Ref S3LogsBucketName\n       - Key: 'deletion_protection.enabled'\n         Value: 'true'\n       - Key: 'routing.http.drop_invalid_header_fields.enabled'\n         Value: 'true'\n     Scheme: internet-facing\n     SecurityGroups:\n       - !Ref LoadBalancerSecurityGroup\n     Subnets:\n       - !Ref SubnetPublicAId\n       - !Ref SubnetPublicBId\n       - !Ref SubnetPublicCId\n     Type: application\n HttpListener:\n   Type: AWS::ElasticLoadBalancingV2::Listener\n   Properties:\n     DefaultActions:\n       - RedirectConfig:\n           Port: '443'\n           Protocol: HTTPS\n           StatusCode: 'HTTP_301'\n         Type: redirect\n     LoadBalancerArn: !Ref LoadBalancer\n     Port: 80\n     Protocol: HTTP\n HttpsListener:\n   Type: AWS::ElasticLoadBalancingV2::Listener\n   Properties:\n     Certificates:\n       - CertificateArn: !Ref LoadBalancerCertificateArn\n     DefaultActions:\n       - Type: forward\n         TargetGroupArn: !Ref TargetGroup\n     LoadBalancerArn: !Ref LoadBalancer\n     Port: 443\n     Protocol: HTTPS\n TargetGroup:\n   Type: AWS::ElasticLoadBalancingV2::TargetGroup\n   Properties:\n     Name: !Ref ProjectName\n     HealthCheckIntervalSeconds: 30\n     HealthCheckPath: !Ref HealthCheckPath\n     HealthCheckProtocol: HTTP\n     HealthCheckPort: !Ref NginxContainerPort\n     HealthCheckTimeoutSeconds: 10\n     HealthyThresholdCount: 2\n     UnhealthyThresholdCount: 2\n     Matcher:\n       HttpCode: '200-299'\n     Port: 8080\n     Protocol: HTTP\n     TargetType: ip\n     TargetGroupAttributes:\n       - Key: deregistration_delay.timeout_seconds\n         Value: '30'\n     VpcId: !Ref VpcId\n Cluster:\n   Type: AWS::ECS::Cluster\n   Properties:\n     ClusterName: !Ref ProjectName\n Service:\n   Type: AWS::ECS::Service\n   Properties:\n     Cluster: !Ref Cluster\n     DeploymentConfiguration:\n       MaximumPercent: 200\n       MinimumHealthyPercent: 100\n     DesiredCount: 3\n     HealthCheckGracePeriodSeconds: 60\n     LaunchType: FARGATE\n     LoadBalancers:\n       - ContainerName: ContainerOne\n         ContainerPort: !Ref ContainerPort\n         TargetGroupArn: !Ref TargetGroup\n     NetworkConfiguration:\n       AwsvpcConfiguration:\n         AssignPublicIp: DISABLED\n         SecurityGroups:\n           - !Ref ContainerSecurityGroupId\n         Subnets:\n           - !Ref SubnetPrivateNatAId\n           - !Ref SubnetPrivateNatBId\n           - !Ref SubnetPrivateNatCId\n     ServiceName: !Ref ProjectName\n     TaskDefinition: !Ref TaskDefinition\n   DependsOn: HttpsListener\n TaskDefinition:\n   Type: AWS::ECS::TaskDefinition\n   Properties:\n     Family: !Ref ProjectName\n     ContainerDefinitions:\n       - Cpu: 2048\n         Image: !Ref ContainerImageUri\n         Memory: 4096\n         MemoryReservation: 4096\n         PortMappings:\n           - ContainerPort: !Ref ContainerPort\n             Protocol: tcp\n         Name: ContainerOne\n         LogConfiguration:\n           LogDriver: awslogs\n           Options:\n             awslogs-group: !Ref ContainerLogGroup\n             awslogs-region: !Ref AWS::Region\n             awslogs-stream-prefix: ContainerOne\n     Cpu: '2048'\n     Memory: '4096'\n     ExecutionRoleArn: !GetAtt ExecutionContainerRole.Arn\n     TaskRoleArn: !GetAtt TaskContainerRole.Arn\n     NetworkMode: awsvpc\n     RequiresCompatibilities:\n       - FARGATE\n<\/pre>\n\n\n\n<p>This code is just a hint, you\u2019ll need to cover by yourself parameters\u2019 management and add some tweaks for your specific project. In case of need also refer to these two links:\n<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li><a href=\"https:\/\/github.com\/awslabs\/aws-cloudformation-templates\/tree\/master\/aws\/services\">https:\/\/github.com\/awslabs\/aws-cloudformation-templates\/tree\/master\/aws\/services<\/a><\/li><li><a href=\"https:\/\/docs.aws.amazon.com\/AmazonECS\/latest\/developerguide\/AWS_Fargate.html\">https:\/\/docs.aws.amazon.com\/AmazonECS\/latest\/developerguide\/AWS_Fargate.html<\/a><\/li><\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">To sum up<\/h2>\n\n\n\n<p>In this article, we have seen how to create a pipeline to make Blue\/Green deployments on ECS completely automated. <\/p>\n\n\n\n<p>We have also seen how Lambda functions can be used to automate the testing phase in the green environment.<\/p>\n\n\n\n<p>To complete our tutorial we\u2019ve also seen how AWS CloudFormation template can be used to minimize boilerplate infrastructure creation as well as making it reusable and repeatable.\n<\/p>\n\n\n\n<p>As our aim was to trace the path to help you master automation and pipeline setup, this overview was maintained specifically simple, as it is intended to be expanded and manipulated by the reader to fit its particular needs. \n<\/p>\n\n\n\n<p>Have you ever applied this, or similar \u2013 and maybe more advanced &#8211; configurations for your Pipelines? Let us know! We can\u2019t wait to hear from you!\n\nWe hope you enjoyed this reading and found it useful. \n<\/p>\n\n\n\n<p>As always #Proud2beCloud meets you in two weeks.<\/p>\n\n\n\n<p><span style=\"font-weight: 400;\">Till then, happy deployments \ud83d\ude42<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Continuous Deployment is nowadays a well-known strategy for releasing software where any commit that passes the automated testing phase is [&hellip;]<\/p>\n","protected":false},"author":14,"featured_media":1923,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[242],"tags":[378,292,294,286,409,369],"class_list":["post-1930","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-devops-en","tag-amazon-ecs-en","tag-aws-codebuild-en","tag-aws-codedeploy-en","tag-aws-codepipeline-en","tag-blue-green-deployment-en","tag-continuous-delivery-en"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v24.7 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>How to setup a Continuous Deployment Pipeline on AWS for ECS Blue\/Green Deployments. - Proud2beCloud Blog<\/title>\n<meta name=\"description\" content=\"In this article, we&#039;ll set up a Continuous Deployment Pipeline for automatic blue\/green Deployment on ECS.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/blog.besharp.it\/how-to-setup-a-continuous-deployment-pipeline-on-aws-for-ecs-blue-green-deployments\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Automatic blue\/green Deployment on ECS\" \/>\n<meta property=\"og:description\" content=\"Let&#039;s create a Pipeline for automatic blue\/green Deployment on ECS.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/blog.besharp.it\/how-to-setup-a-continuous-deployment-pipeline-on-aws-for-ecs-blue-green-deployments\/\" \/>\n<meta property=\"og:site_name\" content=\"Proud2beCloud Blog\" \/>\n<meta property=\"article:published_time\" content=\"2020-10-30T09:53:58+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2021-05-10T13:48:31+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/facebook-link-image-2.png\" \/>\n<meta name=\"author\" content=\"Alessandro Bertini\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:title\" content=\"Automatic blue\/green Deployment on ECS\" \/>\n<meta name=\"twitter:description\" content=\"Let&#039;s create a Pipeline for automatic blue\/green Deployment on ECS.\" \/>\n<meta name=\"twitter:image\" content=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/twitter-shared-link-3.png\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Alessandro Bertini\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"13 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/blog.besharp.it\/how-to-setup-a-continuous-deployment-pipeline-on-aws-for-ecs-blue-green-deployments\/\",\"url\":\"https:\/\/blog.besharp.it\/how-to-setup-a-continuous-deployment-pipeline-on-aws-for-ecs-blue-green-deployments\/\",\"name\":\"How to setup a Continuous Deployment Pipeline on AWS for ECS Blue\/Green Deployments. - Proud2beCloud Blog\",\"isPartOf\":{\"@id\":\"https:\/\/blog.besharp.it\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/blog.besharp.it\/how-to-setup-a-continuous-deployment-pipeline-on-aws-for-ecs-blue-green-deployments\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/blog.besharp.it\/how-to-setup-a-continuous-deployment-pipeline-on-aws-for-ecs-blue-green-deployments\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/Copertina_55-55.png\",\"datePublished\":\"2020-10-30T09:53:58+00:00\",\"dateModified\":\"2021-05-10T13:48:31+00:00\",\"author\":{\"@id\":\"https:\/\/blog.besharp.it\/#\/schema\/person\/06e173694a005ed650e6de35e965e0c9\"},\"description\":\"In this article, we'll set up a Continuous Deployment Pipeline for automatic blue\/green Deployment on ECS.\",\"breadcrumb\":{\"@id\":\"https:\/\/blog.besharp.it\/how-to-setup-a-continuous-deployment-pipeline-on-aws-for-ecs-blue-green-deployments\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/blog.besharp.it\/how-to-setup-a-continuous-deployment-pipeline-on-aws-for-ecs-blue-green-deployments\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/blog.besharp.it\/how-to-setup-a-continuous-deployment-pipeline-on-aws-for-ecs-blue-green-deployments\/#primaryimage\",\"url\":\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/Copertina_55-55.png\",\"contentUrl\":\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/Copertina_55-55.png\",\"width\":1667,\"height\":1251,\"caption\":\"automatic blue\/green deployment on ecs\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/blog.besharp.it\/how-to-setup-a-continuous-deployment-pipeline-on-aws-for-ecs-blue-green-deployments\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/blog.besharp.it\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"How to setup a Continuous Deployment Pipeline on AWS for ECS Blue\/Green Deployments.\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/blog.besharp.it\/#website\",\"url\":\"https:\/\/blog.besharp.it\/\",\"name\":\"Proud2beCloud Blog\",\"description\":\"il blog di beSharp\",\"alternateName\":\"Proud2beCloud Blog\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/blog.besharp.it\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/blog.besharp.it\/#\/schema\/person\/06e173694a005ed650e6de35e965e0c9\",\"name\":\"Alessandro Bertini\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/blog.besharp.it\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/6138dfdbb6ddab5ec54e7b8be0bbef73?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/6138dfdbb6ddab5ec54e7b8be0bbef73?s=96&d=mm&r=g\",\"caption\":\"Alessandro Bertini\"},\"description\":\"DevOps Engineer @ beSharp. I deal with Cloud-Native software development, strongly oriented to the serverless paradigm! Passionate about board games and video games (as the best geeks do!)\",\"url\":\"https:\/\/blog.besharp.it\/author\/alessandro-bertini\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"How to setup a Continuous Deployment Pipeline on AWS for ECS Blue\/Green Deployments. - Proud2beCloud Blog","description":"In this article, we'll set up a Continuous Deployment Pipeline for automatic blue\/green Deployment on ECS.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/blog.besharp.it\/how-to-setup-a-continuous-deployment-pipeline-on-aws-for-ecs-blue-green-deployments\/","og_locale":"en_US","og_type":"article","og_title":"Automatic blue\/green Deployment on ECS","og_description":"Let's create a Pipeline for automatic blue\/green Deployment on ECS.","og_url":"https:\/\/blog.besharp.it\/how-to-setup-a-continuous-deployment-pipeline-on-aws-for-ecs-blue-green-deployments\/","og_site_name":"Proud2beCloud Blog","article_published_time":"2020-10-30T09:53:58+00:00","article_modified_time":"2021-05-10T13:48:31+00:00","og_image":[{"url":"https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/facebook-link-image-2.png","type":"","width":"","height":""}],"author":"Alessandro Bertini","twitter_card":"summary_large_image","twitter_title":"Automatic blue\/green Deployment on ECS","twitter_description":"Let's create a Pipeline for automatic blue\/green Deployment on ECS.","twitter_image":"https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/twitter-shared-link-3.png","twitter_misc":{"Written by":"Alessandro Bertini","Est. reading time":"13 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/blog.besharp.it\/how-to-setup-a-continuous-deployment-pipeline-on-aws-for-ecs-blue-green-deployments\/","url":"https:\/\/blog.besharp.it\/how-to-setup-a-continuous-deployment-pipeline-on-aws-for-ecs-blue-green-deployments\/","name":"How to setup a Continuous Deployment Pipeline on AWS for ECS Blue\/Green Deployments. - Proud2beCloud Blog","isPartOf":{"@id":"https:\/\/blog.besharp.it\/#website"},"primaryImageOfPage":{"@id":"https:\/\/blog.besharp.it\/how-to-setup-a-continuous-deployment-pipeline-on-aws-for-ecs-blue-green-deployments\/#primaryimage"},"image":{"@id":"https:\/\/blog.besharp.it\/how-to-setup-a-continuous-deployment-pipeline-on-aws-for-ecs-blue-green-deployments\/#primaryimage"},"thumbnailUrl":"https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/Copertina_55-55.png","datePublished":"2020-10-30T09:53:58+00:00","dateModified":"2021-05-10T13:48:31+00:00","author":{"@id":"https:\/\/blog.besharp.it\/#\/schema\/person\/06e173694a005ed650e6de35e965e0c9"},"description":"In this article, we'll set up a Continuous Deployment Pipeline for automatic blue\/green Deployment on ECS.","breadcrumb":{"@id":"https:\/\/blog.besharp.it\/how-to-setup-a-continuous-deployment-pipeline-on-aws-for-ecs-blue-green-deployments\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/blog.besharp.it\/how-to-setup-a-continuous-deployment-pipeline-on-aws-for-ecs-blue-green-deployments\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/blog.besharp.it\/how-to-setup-a-continuous-deployment-pipeline-on-aws-for-ecs-blue-green-deployments\/#primaryimage","url":"https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/Copertina_55-55.png","contentUrl":"https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/Copertina_55-55.png","width":1667,"height":1251,"caption":"automatic blue\/green deployment on ecs"},{"@type":"BreadcrumbList","@id":"https:\/\/blog.besharp.it\/how-to-setup-a-continuous-deployment-pipeline-on-aws-for-ecs-blue-green-deployments\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/blog.besharp.it\/"},{"@type":"ListItem","position":2,"name":"How to setup a Continuous Deployment Pipeline on AWS for ECS Blue\/Green Deployments."}]},{"@type":"WebSite","@id":"https:\/\/blog.besharp.it\/#website","url":"https:\/\/blog.besharp.it\/","name":"Proud2beCloud Blog","description":"il blog di beSharp","alternateName":"Proud2beCloud Blog","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/blog.besharp.it\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/blog.besharp.it\/#\/schema\/person\/06e173694a005ed650e6de35e965e0c9","name":"Alessandro Bertini","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/blog.besharp.it\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/6138dfdbb6ddab5ec54e7b8be0bbef73?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/6138dfdbb6ddab5ec54e7b8be0bbef73?s=96&d=mm&r=g","caption":"Alessandro Bertini"},"description":"DevOps Engineer @ beSharp. I deal with Cloud-Native software development, strongly oriented to the serverless paradigm! Passionate about board games and video games (as the best geeks do!)","url":"https:\/\/blog.besharp.it\/author\/alessandro-bertini\/"}]}},"_links":{"self":[{"href":"https:\/\/blog.besharp.it\/wp-json\/wp\/v2\/posts\/1930","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.besharp.it\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.besharp.it\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.besharp.it\/wp-json\/wp\/v2\/users\/14"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.besharp.it\/wp-json\/wp\/v2\/comments?post=1930"}],"version-history":[{"count":0,"href":"https:\/\/blog.besharp.it\/wp-json\/wp\/v2\/posts\/1930\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.besharp.it\/wp-json\/wp\/v2\/media\/1923"}],"wp:attachment":[{"href":"https:\/\/blog.besharp.it\/wp-json\/wp\/v2\/media?parent=1930"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.besharp.it\/wp-json\/wp\/v2\/categories?post=1930"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.besharp.it\/wp-json\/wp\/v2\/tags?post=1930"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}