{"id":472,"date":"2017-03-10T15:33:42","date_gmt":"2017-03-10T14:33:42","guid":{"rendered":"https:\/\/blog.besharp.it\/full-stack-continuous-delivery-on-aws\/"},"modified":"2023-02-22T17:20:22","modified_gmt":"2023-02-22T16:20:22","slug":"full-stack-continuous-delivery-on-aws","status":"publish","type":"post","link":"https:\/\/blog.besharp.it\/full-stack-continuous-delivery-on-aws\/","title":{"rendered":"Full stack Continuous Delivery on AWS"},"content":{"rendered":"<p id=\"4f79\" class=\"graf graf--p graf-after--h3\"><strong class=\"markup--strong markup--p-strong\">AWS DevOps<\/strong><br \/>\nWith the launch of\u00a0<a class=\"markup--anchor markup--p-anchor\" href=\"https:\/\/aws.amazon.com\/codebuild\/\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" data-href=\"https:\/\/aws.amazon.com\/codebuild\/\"><strong class=\"markup--strong markup--p-strong\">CodeBuild<\/strong><\/a>\u00a0last November\u00a0<a class=\"markup--anchor markup--p-anchor\" href=\"https:\/\/www.youtube.com\/watch?v=ZDScBNahsL4\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" data-href=\"https:\/\/www.youtube.com\/watch?v=ZDScBNahsL4\"><strong class=\"markup--strong markup--p-strong\">on the stage of re:Invent<\/strong><\/a>, AWS added the missing puzzle piece to the suite of software development lifecycle management tools.<\/p>\n<p id=\"bbb3\" class=\"graf graf--p graf-after--p\"><strong class=\"markup--strong markup--p-strong\"><a class=\"markup--anchor markup--p-anchor\" href=\"https:\/\/blog.besharp.it\/aws-reinvent-2016-parola-chiave-trasformazione\/\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" data-href=\"https:\/\/blog.besharp.it\/aws-reinvent-2016-parola-chiave-trasformazione\/\">We were there<\/a>, <\/strong>and this was all we had been waiting for to be able to get to work and implement\u00a0<strong class=\"markup--strong markup--p-strong\">a Continuous Delivery system entirely based on services operated by Amazon Web Services<\/strong>.<\/p>\n<p id=\"7e90\" class=\"graf graf--p graf-after--p\">Before CodeBuild, AWS\u2019s suite only covered aspects relating to source control (<a class=\"markup--anchor markup--p-anchor\" href=\"https:\/\/aws.amazon.com\/codecommit\/\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" data-href=\"https:\/\/aws.amazon.com\/codecommit\/\"><strong class=\"markup--strong markup--p-strong\">CodeCommit<\/strong><\/a>), release management (<a class=\"markup--anchor markup--p-anchor\" href=\"https:\/\/aws.amazon.com\/codedeploy\/\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" data-href=\"https:\/\/aws.amazon.com\/codedeploy\/\"><strong class=\"markup--strong markup--p-strong\">CodeDeploy<\/strong><\/a>) and orchestration (<a class=\"markup--anchor markup--p-anchor\" href=\"https:\/\/aws.amazon.com\/codepipeline\/\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" data-href=\"https:\/\/aws.amazon.com\/codepipeline\/\"><strong class=\"markup--strong markup--p-strong\">CodePipeline<\/strong><\/a>), forcing developers to use third-party tools (for example\u00a0<a class=\"markup--anchor markup--p-anchor\" href=\"https:\/\/jenkins.io\/\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" data-href=\"https:\/\/jenkins.io\/\"><strong class=\"markup--strong markup--p-strong\">Jenkins<\/strong><\/a>) to manage the build and test phases. Tools that have to be configured and operated manually, with all the issues that this entails in terms of the complexity, costs, and reliability of the solution.<\/p>\n<p id=\"3b89\" class=\"graf graf--p graf-after--p\">We are thinking about how the Continuous Delivery stack is, on the one hand, critical (an incident with one of these tools can compromise hours or days of a whole development team\u2019s work), but on the other hand, it represents\u200a\u2014\u200aespecially for small, agile DevOps teams\u200a\u2014\u200aan object which is foreign to the \u201ccore\u201d activities which should have the least effort focused on it possible;\u00a0<strong class=\"markup--strong markup--p-strong\">a sort of black box that just needs to work.<\/strong><\/p>\n<p id=\"3af9\" class=\"graf graf--p graf-after--p\">A Continuous Delivery stack must:<\/p>\n<ul class=\"postList\">\n<li id=\"e85f\" class=\"graf graf--li graf-after--p\">Be extremely reliable (no single-point-of-failure)<\/li>\n<li id=\"55b7\" class=\"graf graf--li graf-after--li\">Ensure the durability of the data (in particular with regard to repositories)<\/li>\n<li id=\"f7dc\" class=\"graf graf--li graf-after--li\">Require minimal effort to manage and configure<\/li>\n<li id=\"1bfe\" class=\"graf graf--li graf-after--li\">Easily integrate with both development and production environments and tools<\/li>\n<li id=\"1b4c\" class=\"graf graf--li graf-after--li\">Be easy to scale in order to grow with both the team and their projects<\/li>\n<li id=\"6ae1\" class=\"graf graf--li graf-after--li\">Be cheap<\/li>\n<\/ul>\n<p id=\"d4d5\" class=\"graf graf--p graf-after--li\">For AWS users, the use of a CD stack which is entirely based on its managed services is the most natural and immediate option that meets all these requirements.<\/p>\n<p id=\"3866\" class=\"graf graf--p graf-after--p\"><strong class=\"markup--strong markup--p-strong\">The Solution<br \/>\n<\/strong>Let\u2019s briefly review which tools we have available to us:<\/p>\n<ul class=\"postList\">\n<li id=\"87b4\" class=\"graf graf--li graf-after--p\"><strong class=\"markup--strong markup--li-strong\">CodeCommit<\/strong>: a fully-managed and automatically-scaled git repository<\/li>\n<li id=\"e0c2\" class=\"graf graf--li graf-after--li\"><strong class=\"markup--strong markup--li-strong\">CodeBuild<\/strong>: a build and testing system based on containers<\/li>\n<li id=\"5e6b\" class=\"graf graf--li graf-after--li\"><strong class=\"markup--strong markup--li-strong\">CodeDeploy<\/strong>: an agent-based system to deploy EC2 instances automatically<\/li>\n<li id=\"aaf1\" class=\"graf graf--li graf-after--li\"><strong class=\"markup--strong markup--li-strong\">CodePipeline<\/strong>: an orchestrator that is fully integrated into the AWS ecosystem, which is able to make the other three services interact with one another or with third-party providers.<\/li>\n<\/ul>\n<p id=\"0fce\" class=\"graf graf--p graf-after--li\">Our team has developed a\u00a0<strong class=\"markup--strong markup--p-strong\">comprehensive and automated solution for managing the software lifecycle on Amazon Web Services<\/strong>, applicable both to hybrid environments (in this case, integration with the repository and build is done in the Cloud, whereas the deploy can take place on any type of instance, both in the Cloud or on-premise), and to fully Cloud-based environments, with the staging and production machines which are also in the Cloud.<\/p>\n<figure id=\"attachment_483\" aria-describedby=\"caption-attachment-483\" style=\"width: 900px\" class=\"wp-caption aligncenter\"><img loading=\"lazy\" decoding=\"async\" class=\"wp-image-483 size-full\" src=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2017\/03\/FullStackCDonAWS-e1489149925140.png\" alt=\"\" width=\"900\" height=\"520\" srcset=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2017\/03\/FullStackCDonAWS-e1489149925140.png 900w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2017\/03\/FullStackCDonAWS-e1489149925140-400x231.png 400w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2017\/03\/FullStackCDonAWS-e1489149925140-768x444.png 768w\" sizes=\"(max-width: 900px) 100vw, 900px\" \/><figcaption id=\"caption-attachment-483\" class=\"wp-caption-text\">The developers push the code on CodeCommit, a trigger is set off, and CodePipeline takes the code and feeds it into CodeBuild, which carries out the build and the tests and creates the artifact, ready for the deploy. At this point, CodePipeline passes the packet to CodeDeploy which releases it on a pool of EC2 instances. At every step, S3 is used as supporting storage for the artifacts.<\/figcaption><\/figure>\n<p class=\"graf graf--p graf-after--figure\">Using only AWS services, which are compatible and specifically designed to cooperate with each other, has the advantage of putting specific triggers and extremely simplified setups at our disposal. <strong class=\"markup--strong markup--p-strong\">Everything scales automatically and without the need for any particular technical operations<\/strong>; the team is, therefore relieved of the burden of sizing the Continuous Delivery infrastructure in advance.<\/p>\n<p id=\"6963\" class=\"graf graf--p graf-after--p\">It is also possible to manage security and permissions at a granular level by using IAM role and IAM policy. Unlike what happens when using other tools, it is possible to remain confined within the sandbox of a single Amazon account, without having to externally present an endpoint to start the build process.<\/p>\n<p id=\"8f44\" class=\"graf graf--p graf-after--p\">We have found that CodeBuild takes care of the build and test phases by using provisioning of the containers; these start up only when needed, thus optimising performance and eliminating the need for dedicated instances, as happens when using Jenkins, for example.<\/p>\n<p id=\"703b\" class=\"graf graf--p graf-after--p\">Another key feature of CodeBuild is isolation, which allows for\u00a0<strong class=\"markup--strong markup--p-strong\">each build to be segregated at both the application and release levels.<\/strong><\/p>\n<p id=\"b65f\" class=\"graf graf--p graf-after--p\"><strong class=\"markup--strong markup--p-strong\">AWS Costs<br \/>\n<\/strong>Before we begin with the tutorial, let\u2019s have a look at the AWS costs incurred by this solution:<\/p>\n<p id=\"296b\" class=\"graf graf--p graf-after--p\">The price of each CodePipeline pipeline is $1\/month, whilst for the first 5 users (50GB and 10000 git requests), the CodeCommit service is totally free. For the sixth user onwards, the cost is $1\/month per user.<\/p>\n<p id=\"dcee\" class=\"graf graf--p graf-after--p\">The cost of the CodeBuild service is calculated according to the minutes of the actual use of the containers carried out by the builds, a model that allows for significant cost savings compared to traditional runners based on EC2 instances, which are charged on an hourly basis.<\/p>\n<p id=\"a011\" class=\"graf graf--p graf-after--p\">CodeDeploy is free, with no limits on traffic or time.<\/p>\n<p id=\"abd0\" class=\"graf graf--p graf-after--p\">The additional costs to be considered are the storage and bandwidth costs generated by S3, which is used as supporting storage for the artifacts between one step and the next of each pipeline.<\/p>\n<p id=\"f2d5\" class=\"graf graf--p graf-after--p\">Obviously, costs can vary widely depending on the context and organisation of every team, but we would like to say that in most cases, this stack works out to be<strong class=\"markup--strong markup--p-strong\">\u00a0one of the cheapest solutions around.<\/strong><\/p>\n<p id=\"970b\" class=\"graf graf--p graf-after--p\">Now let us enter into the heart of the implementation.<\/p>\n<p id=\"f4c4\" class=\"graf graf--p graf-after--p\"><strong class=\"markup--strong markup--p-strong\">CodeCommit<br \/>\n<\/strong>The first service to be configured is CodeCommit.<\/p>\n<p id=\"c50b\" class=\"graf graf--p graf-after--p\">We create the repository by logging into the AWS console or, in the case of programming access, to the CLI.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"size-full wp-image-484 aligncenter\" src=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2017\/03\/CodeCommit1.png\" alt=\"\" width=\"679\" height=\"500\" srcset=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2017\/03\/CodeCommit1.png 679w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2017\/03\/CodeCommit1-400x295.png 400w\" sizes=\"(max-width: 679px) 100vw, 679px\" \/><\/p>\n<p>Now we create an IAM user that will allow us to proceed with the main git actions on the repository that has just been created.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"size-full wp-image-485 aligncenter\" src=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2017\/03\/CodeCommit2.png\" alt=\"\" width=\"967\" height=\"781\" srcset=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2017\/03\/CodeCommit2.png 967w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2017\/03\/CodeCommit2-371x300.png 371w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2017\/03\/CodeCommit2-768x620.png 768w\" sizes=\"(max-width: 967px) 100vw, 967px\" \/><\/p>\n<p>To get the necessary permissions to access the repo, you must authenticate as an IAM user. Here are the possible methods:<\/p>\n<ul class=\"postList\">\n<li id=\"f49f\" class=\"graf graf--li graf-after--p\"><em class=\"markup--em markup--li-em\">Git credential helper<\/em>, which uses the CLI. In which case, a key pair is needed for access:<\/li>\n<li id=\"c884\" class=\"graf graf--li graf-after--li\">an\u00a0<em class=\"markup--em markup--li-em\">SSH key<\/em>\u00a0that can be generated by IAM user management;<\/li>\n<li id=\"c760\" class=\"graf graf--li graf-after--li\">a<em class=\"markup--em markup--li-em\">\u00a0username and password<\/em>, also generated by the IAM management console (using HTTPS).<\/li>\n<\/ul>\n<p id=\"d13c\" class=\"graf graf--p graf-after--li\">With each push of the app\u2019s source code, this is taken over by CodeBuild, which deals with the provisioning of a temporary, isolated environment (container) inside which the build and test phases will take place.<\/p>\n<p id=\"87fd\" class=\"graf graf--p graf-after--p\"><strong class=\"markup--strong markup--p-strong\">CodeBuild<br \/>\n<\/strong>Before proceeding to the test and build phases, we must configure CodeBuild, specifying the container size, the type of image desired (for example, a Linux container with a preinstalled framework from the ones available or a custom image) and specifying the steps we want CodeBuild to take to carry out the test and build of the app. This last step means a choice between two methodologies: declaring the inline commands or using a file called buildspec.yml that will invoke the hooks of the build cycle.<\/p>\n<p id=\"26e5\" class=\"graf graf--p graf-after--p\">We chose to use the latter method because, in this way, the YAML buildspec file can be versioned along with the application code, giving us the opportunity to change the test and build procedures just before the build phase itself.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"size-large wp-image-486 aligncenter\" src=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2017\/03\/CodeBuild-1024x934.png\" alt=\"\" width=\"1024\" height=\"934\" srcset=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2017\/03\/CodeBuild-1024x934.png 1024w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2017\/03\/CodeBuild-329x300.png 329w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2017\/03\/CodeBuild-768x701.png 768w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2017\/03\/CodeBuild.png 1380w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/p>\n<p id=\"2393\" class=\"graf graf--p graf-after--figure\">So, within each hook, we have specified the commands that CodeBuild will perform, moment by moment.<\/p>\n<p id=\"40cc\" class=\"graf graf--p graf-after--p\">Below is a generic example of the structure of a buildspec.yml file located in the root directory of the repository:<\/p>\n<pre class=\"graf graf--pre graf-after--p\">version<strong class=\"markup--strong markup--pre-strong\">: <\/strong>0.1\r\n\r\nenvironment_variables:\r\nplaintext:\r\nJAVA_HOME<strong class=\"markup--strong markup--pre-strong\">: <\/strong>\"\/usr\/lib\/jvm\/java-8-openjdk-amd64\"\r\n\r\nphases:\r\ninstall:\r\ncommands<strong class=\"markup--strong markup--pre-strong\">:\r\n<\/strong>- apt-get update -y\r\n- apt-get install -y maven\r\npre_build:\r\ncommands<strong class=\"markup--strong markup--pre-strong\">:\r\n<\/strong>- echo Nothing to do in the pre_build phase...\r\nbuild:\r\ncommands<strong class=\"markup--strong markup--pre-strong\">:\r\n<\/strong>- echo Build started on `date`\r\n- mvn install\r\npost_build:\r\ncommands<strong class=\"markup--strong markup--pre-strong\">:\r\n<\/strong>- echo Build completed on `date`\r\nartifacts:\r\nfiles<strong class=\"markup--strong markup--pre-strong\">:\r\n<\/strong>- target\/messageUtil-1.0.jar\r\ndiscard-paths<strong class=\"markup--strong markup--pre-strong\">: yes<\/strong><\/pre>\n<p id=\"0712\" class=\"graf graf--p graf-after--pre\">Since the last phase of the buildspec.yml, we made sure to get a bundle that was compatible with CodeDeploy, the service used in the next phase; the package obtained from the last build phase contains both the application, ready for implementation, and the scripts to run to install it and configure it on the deploy instance.<\/p>\n<p id=\"880e\" class=\"graf graf--p graf-after--p\"><strong class=\"markup--strong markup--p-strong\">CodeDeploy<br \/>\n<\/strong>For CodeDeploy to function, its scripts must be executed from within the instance; for this to happen, the AWS CLI and the CodeDeploy agent must be installed in each instance of the process\u2019 target infrastructure.<\/p>\n<p id=\"05e4\" class=\"graf graf--p graf-after--p\">We create a file containing the declaration of the hooks, this time called appspec.yml. After having created the necessary scripts from scratch, we decided which and how many of them to call for each hook.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"size-full wp-image-487 aligncenter\" src=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2017\/03\/CodeDeploy.png\" alt=\"\" width=\"941\" height=\"919\" srcset=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2017\/03\/CodeDeploy.png 941w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2017\/03\/CodeDeploy-307x300.png 307w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2017\/03\/CodeDeploy-768x750.png 768w\" sizes=\"(max-width: 941px) 100vw, 941px\" \/><\/p>\n<p id=\"b5a9\" class=\"graf graf--p graf-after--figure\">The YAML appspec file, in this specific case, requires two folders to be created in the bundle: one (<em class=\"markup--em markup--p-em\">App<\/em>) dedicated to the application and another (<em class=\"markup--em markup--p-em\">Scripts<\/em>) dedicated to the scripts.<\/p>\n<p id=\"3f7a\" class=\"graf graf--p graf-after--p\">Below is a generic example of the structure of an appspec.yml file located in the root directory of the bundle:<\/p>\n<pre class=\"graf graf--pre graf-after--p\">version<strong class=\"markup--strong markup--pre-strong\">: <\/strong>0.0\r\nos<strong class=\"markup--strong markup--pre-strong\">: <\/strong>linux\r\nfiles:\r\n- source<strong class=\"markup--strong markup--pre-strong\">: <\/strong>App\/\r\ndestination<strong class=\"markup--strong markup--pre-strong\">: <\/strong>\/var\/www\/html\/\r\n- source<strong class=\"markup--strong markup--pre-strong\">: <\/strong>nginx.conf\r\ndestination<strong class=\"markup--strong markup--pre-strong\">: <\/strong>\/etc\/nginx\/\r\nhooks:\r\nBeforeInstall:\r\n- location<strong class=\"markup--strong markup--pre-strong\">: <\/strong>Scripts\/UnzipResourceBundle.sh\r\ntimeout<strong class=\"markup--strong markup--pre-strong\">: <\/strong>300\r\nrunas<strong class=\"markup--strong markup--pre-strong\">: <\/strong>root\r\n- location<strong class=\"markup--strong markup--pre-strong\">: <\/strong>Scripts\/InstallDependencies.sh\r\ntimeout<strong class=\"markup--strong markup--pre-strong\">: <\/strong>300\r\nrunas<strong class=\"markup--strong markup--pre-strong\">: <\/strong>ubuntu\r\nAfterInstall:\r\n- location<strong class=\"markup--strong markup--pre-strong\">: <\/strong>Scripts\/FixPermissions.sh\r\ntimeout<strong class=\"markup--strong markup--pre-strong\">: <\/strong>300\r\nrunas<strong class=\"markup--strong markup--pre-strong\">: <\/strong>root\r\nApplicationStart:\r\n- location<strong class=\"markup--strong markup--pre-strong\">: <\/strong>Scripts\/WebServerStart.sh\r\ntimeout<strong class=\"markup--strong markup--pre-strong\">: <\/strong>300\r\nrunas<strong class=\"markup--strong markup--pre-strong\">: <\/strong>root\r\nValidateService:\r\n- location<strong class=\"markup--strong markup--pre-strong\">: <\/strong>Scripts\/ValidateService.sh\r\ntimeout<strong class=\"markup--strong markup--pre-strong\">: <\/strong>300\r\nrunas<strong class=\"markup--strong markup--pre-strong\">: <\/strong>ubuntu<\/pre>\n<p id=\"7a17\" class=\"graf graf--p graf-after--pre\"><strong class=\"markup--strong markup--p-strong\">CodePipeline<br \/>\n<\/strong>Working in parallel with the three tools that we have just described is CodePipeline, the service orchestrator that deals with passing the outputs generated by each phase to the next service, which will use them as the inputs needed to perform its task. Each phase of the Continuous Integration process uses the S3 platform as supporting storage.<\/p>\n<p id=\"908e\" class=\"graf graf--p graf-after--p\">For CodePipeline to function, you need to create a pipeline; to do this, we access the AWS console and perform the following steps:<\/p>\n<ul class=\"postList\">\n<li id=\"9e50\" class=\"graf graf--li graf-after--p\">choose a name for the pipeline;<\/li>\n<\/ul>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"size-large wp-image-488 aligncenter\" src=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2017\/03\/CodePipeline1-1024x362.png\" alt=\"\" width=\"1024\" height=\"362\" srcset=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2017\/03\/CodePipeline1-1024x362.png 1024w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2017\/03\/CodePipeline1-400x142.png 400w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2017\/03\/CodePipeline1-768x272.png 768w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2017\/03\/CodePipeline1.png 1026w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/p>\n<ul class=\"postList\">\n<li id=\"4de1\" class=\"graf graf--li graf-after--figure\">choose the source, in our case CodeCommit;<\/li>\n<\/ul>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"size-large wp-image-489 aligncenter\" src=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2017\/03\/CodePipeline2-1024x593.png\" alt=\"\" width=\"1024\" height=\"593\" srcset=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2017\/03\/CodePipeline2-1024x593.png 1024w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2017\/03\/CodePipeline2-400x232.png 400w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2017\/03\/CodePipeline2-768x445.png 768w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2017\/03\/CodePipeline2.png 1026w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/p>\n<ul class=\"postList\">\n<li id=\"8107\" class=\"graf graf--li graf-after--figure\">configure the build step, in our case CodeBuild;<\/li>\n<\/ul>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"size-full wp-image-490 aligncenter\" src=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2017\/03\/CodePipeline3.png\" alt=\"\" width=\"1021\" height=\"688\" srcset=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2017\/03\/CodePipeline3.png 1021w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2017\/03\/CodePipeline3-400x270.png 400w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2017\/03\/CodePipeline3-768x518.png 768w\" sizes=\"(max-width: 1021px) 100vw, 1021px\" \/><\/p>\n<ul class=\"postList\">\n<li id=\"4ae5\" class=\"graf graf--li graf-after--figure\">choose the deploy provider, in our case CodeDeploy;<\/li>\n<\/ul>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"size-full wp-image-491 aligncenter\" src=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2017\/03\/CodePipeline4.png\" alt=\"\" width=\"1018\" height=\"627\" srcset=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2017\/03\/CodePipeline4.png 1018w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2017\/03\/CodePipeline4-400x246.png 400w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2017\/03\/CodePipeline4-768x473.png 768w\" sizes=\"(max-width: 1018px) 100vw, 1018px\" \/><\/p>\n<p>The Pipeline has been successfully created.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"size-full wp-image-492 aligncenter\" src=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2017\/03\/CodePipeline_final.png\" alt=\"\" width=\"285\" height=\"774\" srcset=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2017\/03\/CodePipeline_final.png 285w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2017\/03\/CodePipeline_final-110x300.png 110w\" sizes=\"(max-width: 285px) 100vw, 285px\" \/><\/p>\n<p id=\"3dba\" class=\"graf graf--p graf-after--figure\">When CodeCommit is linked to CodePipeline, it automatically creates a trigger that means that every\u00a0<em class=\"markup--em markup--p-em\">git push<\/em>\u00a0causes the process described in the pipeline created to initiate.<\/p>\n<p id=\"1641\" class=\"graf graf--p graf-after--p\">The source code that results from this phase is delivered in the form of an input to CodeBuild, which generates a bundle that will, in turn, be the input for CodeDeploy. CodeDeploy will then install the app on the target infrastructure.<\/p>\n<p id=\"4bfa\" class=\"graf graf--p graf-after--p\"><em class=\"markup--em markup--p-em\">N.B. it is important to verify that the code generated at the end of each phase by each tool is correct; as each result is the starting point for the next phase, if an output were to be wrong, the whole deploy process would be compromised.<\/em><\/p>\n<p id=\"fae0\" class=\"graf graf--p graf-after--p\">We have been using this solution for the past few weeks now, and we are delighted indeed with it: we deleted all the management efforts of our previous Continuous Delivery infrastructure, increasing the number of builds that we can manage in parallel, and we are also spending significantly less. This stack has turned out to be excellent in terms of efficiency, reliability, and cost efficiency.<\/p>\n<p id=\"6791\" class=\"graf graf--p graf-after--p\">What do you think of it?<\/p>\n<p id=\"8d6f\" class=\"graf graf--p graf-after--p graf--trailing\">If our solution has intrigued you and you like the idea of implementing it in your workflow, leave us a comment or\u00a0<a class=\"markup--anchor markup--p-anchor\" href=\"https:\/\/www.besharp.it\/en\/contact-us\/\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" data-href=\"https:\/\/www.besharp.it\/contacts\/\"><strong class=\"markup--strong markup--p-strong\">contact us<\/strong><\/a>! We\u2019d be happy to answer all your questions, read your thoughts, and help you get the most out of this application.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>AWS DevOps With the launch of\u00a0CodeBuild\u00a0last November\u00a0on the stage of re:Invent, AWS added the missing puzzle piece to the suite [&hellip;]<\/p>\n","protected":false},"author":3,"featured_media":473,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[242],"tags":[365,369],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v21.9.1 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Full stack Continuous Delivery on AWS - Proud2beCloud Blog<\/title>\n<meta name=\"description\" content=\"Full stack Continuous Delivery on AWS\" \/>\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\/full-stack-continuous-delivery-on-aws\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Full stack Continuous Delivery on AWS\" \/>\n<meta property=\"og:description\" content=\"Full stack Continuous Delivery on AWS\" \/>\n<meta property=\"og:url\" content=\"https:\/\/blog.besharp.it\/full-stack-continuous-delivery-on-aws\/\" \/>\n<meta property=\"og:site_name\" content=\"Proud2beCloud Blog\" \/>\n<meta property=\"article:published_time\" content=\"2017-03-10T14:33:42+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2023-02-22T16:20:22+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2017\/03\/FullStackCDonAWS-e1489149925140.png\" \/>\n\t<meta property=\"og:image:width\" content=\"900\" \/>\n\t<meta property=\"og:image:height\" content=\"520\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Simone Merlini\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:title\" content=\"Full stack Continuous Delivery on AWS\" \/>\n<meta name=\"twitter:description\" content=\"Full stack Continuous Delivery on AWS\" \/>\n<meta name=\"twitter:image\" content=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2017\/03\/FullStackCDonAWS-e1489149925140.png\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Simone Merlini\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"9 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/blog.besharp.it\/full-stack-continuous-delivery-on-aws\/\",\"url\":\"https:\/\/blog.besharp.it\/full-stack-continuous-delivery-on-aws\/\",\"name\":\"Full stack Continuous Delivery on AWS - Proud2beCloud Blog\",\"isPartOf\":{\"@id\":\"https:\/\/blog.besharp.it\/#website\"},\"datePublished\":\"2017-03-10T14:33:42+00:00\",\"dateModified\":\"2023-02-22T16:20:22+00:00\",\"author\":{\"@id\":\"https:\/\/blog.besharp.it\/#\/schema\/person\/f5772030de5fdee2860686ede72225ee\"},\"description\":\"Full stack Continuous Delivery on AWS\",\"breadcrumb\":{\"@id\":\"https:\/\/blog.besharp.it\/full-stack-continuous-delivery-on-aws\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/blog.besharp.it\/full-stack-continuous-delivery-on-aws\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/blog.besharp.it\/full-stack-continuous-delivery-on-aws\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/blog.besharp.it\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Full stack Continuous Delivery on AWS\"}]},{\"@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\":\"required name=search_term_string\"}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/blog.besharp.it\/#\/schema\/person\/f5772030de5fdee2860686ede72225ee\",\"name\":\"Simone Merlini\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/blog.besharp.it\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/3476bf5e5ab09a9a5cfe42385c9cbe8f?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/3476bf5e5ab09a9a5cfe42385c9cbe8f?s=96&d=mm&r=g\",\"caption\":\"Simone Merlini\"},\"description\":\"CEO e co-fondatore di beSharp, Cloud Ninja ed early adopter di qualsiasi tipo di soluzione *aaS. Mi divido tra la tastiera del PC e quella a tasti bianchi e neri; sono specializzato nel deploy di cene pantagrueliche e nel test di bottiglie d'annata.\",\"url\":\"https:\/\/blog.besharp.it\/author\/amadeus\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Full stack Continuous Delivery on AWS - Proud2beCloud Blog","description":"Full stack Continuous Delivery on AWS","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\/full-stack-continuous-delivery-on-aws\/","og_locale":"en_US","og_type":"article","og_title":"Full stack Continuous Delivery on AWS","og_description":"Full stack Continuous Delivery on AWS","og_url":"https:\/\/blog.besharp.it\/full-stack-continuous-delivery-on-aws\/","og_site_name":"Proud2beCloud Blog","article_published_time":"2017-03-10T14:33:42+00:00","article_modified_time":"2023-02-22T16:20:22+00:00","og_image":[{"width":900,"height":520,"url":"https:\/\/blog.besharp.it\/wp-content\/uploads\/2017\/03\/FullStackCDonAWS-e1489149925140.png","type":"image\/png"}],"author":"Simone Merlini","twitter_card":"summary_large_image","twitter_title":"Full stack Continuous Delivery on AWS","twitter_description":"Full stack Continuous Delivery on AWS","twitter_image":"https:\/\/blog.besharp.it\/wp-content\/uploads\/2017\/03\/FullStackCDonAWS-e1489149925140.png","twitter_misc":{"Written by":"Simone Merlini","Est. reading time":"9 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/blog.besharp.it\/full-stack-continuous-delivery-on-aws\/","url":"https:\/\/blog.besharp.it\/full-stack-continuous-delivery-on-aws\/","name":"Full stack Continuous Delivery on AWS - Proud2beCloud Blog","isPartOf":{"@id":"https:\/\/blog.besharp.it\/#website"},"datePublished":"2017-03-10T14:33:42+00:00","dateModified":"2023-02-22T16:20:22+00:00","author":{"@id":"https:\/\/blog.besharp.it\/#\/schema\/person\/f5772030de5fdee2860686ede72225ee"},"description":"Full stack Continuous Delivery on AWS","breadcrumb":{"@id":"https:\/\/blog.besharp.it\/full-stack-continuous-delivery-on-aws\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/blog.besharp.it\/full-stack-continuous-delivery-on-aws\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/blog.besharp.it\/full-stack-continuous-delivery-on-aws\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/blog.besharp.it\/"},{"@type":"ListItem","position":2,"name":"Full stack Continuous Delivery on AWS"}]},{"@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":"required name=search_term_string"}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/blog.besharp.it\/#\/schema\/person\/f5772030de5fdee2860686ede72225ee","name":"Simone Merlini","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/blog.besharp.it\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/3476bf5e5ab09a9a5cfe42385c9cbe8f?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/3476bf5e5ab09a9a5cfe42385c9cbe8f?s=96&d=mm&r=g","caption":"Simone Merlini"},"description":"CEO e co-fondatore di beSharp, Cloud Ninja ed early adopter di qualsiasi tipo di soluzione *aaS. Mi divido tra la tastiera del PC e quella a tasti bianchi e neri; sono specializzato nel deploy di cene pantagrueliche e nel test di bottiglie d'annata.","url":"https:\/\/blog.besharp.it\/author\/amadeus\/"}]}},"_links":{"self":[{"href":"https:\/\/blog.besharp.it\/wp-json\/wp\/v2\/posts\/472"}],"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\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.besharp.it\/wp-json\/wp\/v2\/comments?post=472"}],"version-history":[{"count":0,"href":"https:\/\/blog.besharp.it\/wp-json\/wp\/v2\/posts\/472\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.besharp.it\/wp-json\/wp\/v2\/media\/473"}],"wp:attachment":[{"href":"https:\/\/blog.besharp.it\/wp-json\/wp\/v2\/media?parent=472"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.besharp.it\/wp-json\/wp\/v2\/categories?post=472"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.besharp.it\/wp-json\/wp\/v2\/tags?post=472"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}