{"id":645,"date":"2019-05-17T15:58:41","date_gmt":"2019-05-17T13:58:41","guid":{"rendered":"https:\/\/blog.besharp.it\/how-to-create-flexible-ci-cd-pipeline-on-aws-with-fargate-and-sqs\/"},"modified":"2021-03-29T17:17:03","modified_gmt":"2021-03-29T15:17:03","slug":"how-to-create-flexible-ci-cd-pipeline-on-aws-with-fargate-and-sqs","status":"publish","type":"post","link":"https:\/\/blog.besharp.it\/how-to-create-flexible-ci-cd-pipeline-on-aws-with-fargate-and-sqs\/","title":{"rendered":"How to create flexible CI\/CD Pipeline on AWS with Fargate and SQS"},"content":{"rendered":"<p id=\"6994\" class=\"graf graf--p graf-after--figure\">The use of <strong class=\"markup--strong markup--p-strong\">Pipeline for automatic code deployment\u00a0<\/strong>is now an almost essential feature of every development project in the Cloud, as the concept of scalable architecture requires that virtual machines (or containers), which are started on the Cloud to manage traffic spikes use the most up-to-date version of the code. Furthermore, the creation of an automated pipeline\u00a0<strong class=\"markup--strong markup--p-strong\">frees the DevOps from the manual management<\/strong>\u00a0of AMIs and Docker images, as well as eliminating the possibility of \u201chuman errors\u201d in the deployment phase.<\/p>\n<p id=\"84fb\" class=\"graf graf--p graf-after--p\">AWS provides DevOps with a very powerful tool for creating automatic Pipelines:\u00a0<strong class=\"markup--strong markup--p-strong\">AWS CodePipeline.<\/strong>\u00a0This fully managed service works as an\u00a0<strong class=\"markup--strong markup--p-strong\">orchestrator for a CI\/CD<\/strong>\u00a0pipeline with similar functionalities to those offered by other services such as Jenkins but which must be installed on an EC2 instance and, therefore, in addition to not being highly reliable, require a significant configuration and maintenance effort.<\/p>\n<p id=\"2474\" class=\"graf graf--p graf-after--p\">The most common flow of an AWS CodePipeline consists of three steps:<\/p>\n<ul class=\"postList\">\n<li id=\"c954\" class=\"graf graf--li graf-after--p\"><strong class=\"markup--strong markup--li-strong\">Source:<\/strong>\u00a0AWS CodePipeline starts a fully managed and configured container from AWS that takes care of pulling the desired commit from the project git repository and saves it to the supporting pipeline S3 bucket as a compressed bundle. This operation is triggered automatically through AWS CloudWatch events whenever a developer performs a push if the git repository is hosted on AWS CodeCommit or GitHub, while for other git services it is necessary to configure a webhook.<\/li>\n<li id=\"85b2\" class=\"graf graf--li graf-after--li\"><strong class=\"markup--strong markup--li-strong\">Build:<\/strong>\u00a0AWS CodePipeline starts a Docker container that can be configured by the user through the AWS CodeBuild service, which on startup downloads the code previously saved on S3 to execute the build steps, tests and any other steps to prepare to deploy.<\/li>\n<li id=\"0024\" class=\"graf graf--li graf-after--li\"><strong class=\"markup--strong markup--li-strong\">Deploy:<\/strong>\u00a0this step can use several other AWS services to deploy the compiled and tested code in the previous step; for example, you can update the version of a Web app using AWS CodeDeploy, or use AWS CloudFormation to deploy a new version of an AWS Lambda Function or update the container task definition on ECS.<\/li>\n<\/ul>\n<p id=\"d465\" class=\"graf graf--p graf-after--li\">Although the features of AWS CodePipeline are sufficient for the most common use cases, some special needs require you to develop one or more customized steps, to have more flexibility. In this article, we will see how it is possible to\u00a0<strong class=\"markup--strong markup--p-strong\">create an automated pipeline able to build all the branches of a repo git hosted on AWS CodeCommit.<\/strong><\/p>\n<p id=\"f74d\" class=\"graf graf--p graf-after--p\">Many projects, particularly large ones, use git flow or a similar flow to organize the repository.<\/p>\n<p id=\"4590\" class=\"graf graf--p graf-after--p\">This means that there are two or more branches (e.g., production, staging, development) containing the code actually deployed on the relevant environments and a large number of branch features, containing the individual features being developed assigned to the respective developer and team, which once completed are integrated into development and publications.<\/p>\n<p id=\"adf8\" class=\"graf graf--p graf-after--p\">However, very often it is not possible to run the entire suite of automated tests directly from the developers\u2019 workstations, both for reasons of time and for the need to test the ever-increasing integration of the code with the various AWS SaaS services. To overcome these problems and reduce integration errors, it would be very convenient to be able to directly launch the build and the test suite at each commit on the individual features branch via AWS CodeBuild, instead of just merge the feature in dev through CodePipeline created explicitly for this environment.<\/p>\n<p id=\"617e\" class=\"graf graf--p graf-after--p\">Unfortunately, at the moment, AWS CodePipeline does not support source from multiple inputs; it is in fact necessary to specify both the repo and the branch. To solve the problem, in beSharp, we have developed a creative solution using the power of\u00a0<strong class=\"markup--strong markup--p-strong\">CloudWatch Events, SQS, and Fargate.<\/strong><\/p>\n<h4 id=\"e413\" class=\"graf graf--h4 graf-after--p\">Services used for the solution:<\/h4>\n<p id=\"297c\" class=\"graf graf--p graf-after--h4\"><strong class=\"markup--strong markup--p-strong\">CloudWatch Rules:<\/strong>\u00a0the AWS service that allows you to create rules to perform operations or in response to events concerning the AWS account, such as turning on an EC2 or, in our case, a push on a CodeCommit repo, or to fixed time intervals.<\/p>\n<p id=\"85ba\" class=\"graf graf--p graf-after--p\"><strong class=\"markup--strong markup--p-strong\">SQS FIFO:<\/strong>\u00a0the fully managed and highly reliable code service offered by AWS. In our case, we used the First In First Out (FIFO) version to be sure of preserving the order of the messages.<\/p>\n<p id=\"7711\" class=\"graf graf--p graf-after--p\"><strong class=\"markup--strong markup--p-strong\">Fargate:<\/strong>\u00a0The third component of the solution is a Docker container deployed through Fargate (ECS), the new AWS service that allows you to start containers\u00a0<em class=\"markup--em markup--p-em\">as a service<\/em>, without having to deal with management of the underlying infrastructure.<\/p>\n<p id=\"10c7\" class=\"graf graf--p graf-after--p\">In a similar way to the standard operation of AWS CodePipeline, we used CloudWatch Rules to prepare a rule that is triggered at the time of push by a developer on any of the branches. The rule has two configured actions:<\/p>\n<p id=\"b639\" class=\"graf graf--p graf-after--p\">The first queues a message in an SQS queue, while the second starts the Fargate container. The message entered in the queue is the JSON that describes the whole event that started the CloudWatch Rule and contains the name of the repo, the name of the branch and the ID of the commit just sent by the developer.<\/p>\n<p id=\"63cb\" class=\"graf graf--p graf-after--p\">The event pattern of the rule will look like this:<\/p>\n<pre id=\"2cad\" class=\"graf graf--pre graf-after--p\">{\r\n  \"source\": [\r\n    \"aws.codecommit\"\r\n  ],\r\n  \"detail-type\": [\r\n    \"CodeCommit Repository State Change\"\r\n  ],\r\n  \"resources\": [\r\n    \"arn:aws:codecommit:eu-west-1:&lt;ACCOUNT_ID&gt;:&lt;REPOSITORY&gt;\",\r\n    ...\r\n  ],\r\n  \"detail\": {\r\n    \"event\": [\r\n      \"referenceCreated\",\r\n      \"referenceUpdated\"\r\n    ]\r\n  }\r\n}<\/pre>\n<p id=\"5308\" class=\"graf graf--p graf-after--pre\"><strong class=\"markup--strong markup--p-strong\">The SQS FIFO queue, therefore,<\/strong>\u00a0contains the messages corresponding to the push code events on the repository and is consumed by the Fargate containers. To prevent corrupt messages from being re-processed indefinitely, we added a\u00a0<strong class=\"markup--strong markup--p-strong\">dead letter queue<\/strong>\u00a0where messages are transferred after two failed read attempts.<\/p>\n<p id=\"e555\" class=\"graf graf--p graf-after--p\">Once started from the CloudWatch Rule,\u00a0<strong class=\"markup--strong markup--p-strong\">the Fargate container reads messages from the queue,<\/strong>\u00a0pulls the commit from the CodeCommit repository, saves the compressed code bundle on s3 and finally launches AWS CodeBuild with the correct parameters.<\/p>\n<p id=\"abdb\" class=\"graf graf--p graf-after--p\">The Docker container was created using the\u00a0<strong class=\"markup--strong markup--p-strong\">Dockerfile:<\/strong><\/p>\n<pre id=\"f964\" class=\"graf graf--pre graf-after--p\">FROM ubuntu:16.04\r\nRUN apt-get update\r\nRUN apt-get install wget -y\r\nRUN apt-get install numactl -y\r\nRUN apt-get install jq -y\r\nRUN apt-get install zip -y\r\nRUN apt-get install git -y\r\nRUN apt-get install software-properties-common -y\r\nRUN add-apt-repository ppa:jonathonf\/python-3.6 -y\r\nRUN apt-get update\r\nRUN apt-get install python3.6 -y\r\nRUN wget <a class=\"markup--anchor markup--pre-anchor\" href=\"https:\/\/bootstrap.pypa.io\/get-pip.py\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" data-href=\"https:\/\/bootstrap.pypa.io\/get-pip.py\">https:\/\/bootstrap.pypa.io\/get-pip.py<\/a>\r\nRUN python3.6 get-pip.py\r\nRUN pip3.6 install awscli --upgrade\r\nRUN pip3.6 install boto3\r\nRUN mkdir \/pipeline_source\r\nWORKDIR \/pipeline_source\r\nADD .\/codecommit_source.sh \/pipeline_source\/codecommit_source.sh\r\nRUN chmod +x \/pipeline_source\/codecommit_source.sh\r\nCMD \/pipeline_source\/codecommit_source.sh<\/pre>\n<p id=\"483a\" class=\"graf graf--p graf-after--pre\">As shown, only standard bash packages are required, in addition to the AWS CLI. The<em class=\"markup--em markup--p-em\">\u00a0codecommit_source.sh<\/em>script starts when the container is turned on and executes the logic described above.<\/p>\n<p id=\"bd3c\" class=\"graf graf--p graf-after--p\">An example of\u00a0<strong class=\"markup--strong markup--p-strong\">codecommit_source.sh<\/strong>\u00a0is shown below:<\/p>\n<pre id=\"5fdd\" class=\"graf graf--pre graf-after--p\">#!\/bin\/bash\r\nset -Eeuxo pipefail<\/pre>\n<pre id=\"55e2\" class=\"graf graf--pre graf-after--pre\">MESSAGE=$(aws sqs receive-message --queue-url https:\/\/sqs.eu-west-1.amazonaws.com\/&lt;account-id&gt;\/custom-codecommit-events.fifo --wait-time-seconds 20)\r\nRECEIPT_HANDLE=$(echo $MESSAGE | jq -r '.Messages | .[] | .ReceiptHandle')<\/pre>\n<pre id=\"9f7e\" class=\"graf graf--pre graf-after--pre\">aws sqs delete-message --queue-url https:\/\/sqs.eu-west-1.amazonaws.com\/&lt;account-id&gt;\/custom-codecommit-events.fifo --receipt-handle $RECEIPT_HANDLE<\/pre>\n<pre id=\"3c67\" class=\"graf graf--pre graf-after--pre\">if [ -n \"$MESSAGE\" ]\r\nthen\r\nEVENT=$(echo $MESSAGE | jq -r '.Messages | .[] | .Body | fromjson')\r\nREPOSITORY_NAME=$(echo $EVENT | jq -r '.detail | .repositoryName')\r\nCOMMIT_ID=$(echo $EVENT | jq -r '.detail | .commitId')\r\nBRANCH_NAME=$(echo $EVENT | jq -r '.detail | .referenceName')\r\nREPO_URL=https:\/\/git-codecommit.eu-west-1.amazonaws.com\/v1\/repos\/$REPOSITORY_NAME\r\ngit config --global credential.helper '!aws codecommit credential-helper $@'\r\ngit config --global credential.UseHttpPath true\r\ngit clone --depth 10 --branch $BRANCH_NAME $REPO_URL<\/pre>\n<pre id=\"bb38\" class=\"graf graf--pre graf-after--pre\">cd $REPOSITORY_NAME\r\ngit checkout $COMMIT_ID\r\nrm -rf .git \r\nzip -r ..\/$COMMIT_ID.zip .\r\ncd ..<\/pre>\n<pre id=\"3ab4\" class=\"graf graf--pre graf-after--pre\">rm -rf $REPOSITORY_NAME<\/pre>\n<pre id=\"700c\" class=\"graf graf--pre graf-after--pre\">if [ -s $COMMIT_ID.zip ]\r\nthen\r\nCODEBUILD_PROJECT=$REPOSITORY_NAME<\/pre>\n<pre id=\"0ba4\" class=\"graf graf--pre graf-after--pre\">if [ $BRANCH_NAME != \"test\" ] &amp;&amp; [ $BRANCH_NAME != \"develop\" ] &amp;&amp; [ $BRANCH_NAME != \"staging\" ] \r\nthen<\/pre>\n<pre id=\"05d2\" class=\"graf graf--pre graf-after--pre\">aws s3 cp $COMMIT_ID.zip s3:\/\/$CODE_BUCKET\/$REPOSITORY_NAME\/$BRANCH_NAME\/$COMMIT_ID.zip\r\necho s3:\/\/$CODE_BUCKET\/$REPOSITORY_NAME\/$BRANCH_NAME\/$COMMIT_ID.zip\r\naws codebuild start-build --project-name $CODEBUILD_PROJECT --environment-variables-override name=COMMIT_ID,value=$COMMIT_ID,type=PLAINTEXT --source-type-override S3 --source-location-override $CODE_BUCKET\/$REPOSITORY_NAME\/$BRANCH_NAME\/$COMMIT_ID.zip --artifacts-override type=NO_ARTIFACTS<\/pre>\n<pre id=\"dbee\" class=\"graf graf--pre graf-after--pre\">fi\r\nfi\r\nelse\r\necho \"no message in queque\"\r\nfi<\/pre>\n<p id=\"25d2\" class=\"graf graf--p graf-after--pre\">Finally, those who manage the source code will have to take care of\u00a0<strong class=\"markup--strong markup--p-strong\">creating\/modifying the buildspec<\/strong>\u00a0to save the build\u2019s outputs on S3 with an easily readable name.<\/p>\n<p id=\"9cb2\" class=\"graf graf--p graf-after--p\">The solution shown here can be easily modified to work even\u00a0<strong class=\"markup--strong markup--p-strong\">in the case of multiple accounts.<\/strong>\u00a0For example, two accounts may be present: the first account (\u201cmaster\u201d) containing the production environment and the repos, while the second accounts for the staging\/development environments and the pipelines. To do this, it is necessary to add a\u00a0<em class=\"markup--em markup--p-em\">role<\/em>to the \u201cmaster\u201d account that can be taken over by staging to pull the repositories. Finally, it will also be necessary to configure event buses on both accounts in order to share rep messages with the development account.<\/p>\n<p id=\"a579\" class=\"graf graf--p graf-after--p\">In conclusion, AWS CodePipeline is a very powerful tool, but for some cases of use, it is not enough and should, therefore, be combined with custom solutions like the one proposed which are easily configurable using the wide suite of services made available by AWS.<\/p>\n<p id=\"0b04\" class=\"graf graf--p graf-after--p graf--trailing\">Would you like to tell us about your innovative CD\/CI solution or have more information on that proposed in this article? Don\u2019t hesitate to comment and\/or\u00a0<a href=\"https:\/\/www.besharp.it\/en\/contact-us\/\" target=\"_blank\" rel=\"noopener noreferrer\"><strong class=\"markup--strong markup--p-strong\">contact us!<\/strong><\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>The use of Pipeline for automatic code deployment\u00a0is now an almost essential feature of every development project in the Cloud, [&hellip;]<\/p>\n","protected":false},"author":9,"featured_media":649,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[242],"tags":[290,294,264,370],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v21.9.1 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>How to create flexible CI\/CD Pipeline on AWS with Fargate and SQS - Proud2beCloud Blog<\/title>\n<meta name=\"description\" content=\"How to create flexible CI\/CD Pipeline on AWS with AWS Fargate and Amazon SQS\" \/>\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-create-flexible-ci-cd-pipeline-on-aws-with-fargate-and-sqs\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"CI\/CD Pipeline on AWS with AWS Fargate and Amazon SQS\" \/>\n<meta property=\"og:description\" content=\"Using AWS Fargate and Amazon SQS to set up flexible CI\/CD Pipelines\" \/>\n<meta property=\"og:url\" content=\"https:\/\/blog.besharp.it\/how-to-create-flexible-ci-cd-pipeline-on-aws-with-fargate-and-sqs\/\" \/>\n<meta property=\"og:site_name\" content=\"Proud2beCloud Blog\" \/>\n<meta property=\"article:published_time\" content=\"2019-05-17T13:58:41+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2021-03-29T15:17:03+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2019\/05\/copertine-blog_Codepipeline_Tavola-disegno-1-copia.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1668\" \/>\n\t<meta property=\"og:image:height\" content=\"1250\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Matteo Moroni\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:title\" content=\"CI\/CD Pipeline on AWS with AWS Fargate and Amazon SQS\" \/>\n<meta name=\"twitter:description\" content=\"Using AWS Fargate and Amazon SQS to set up flexible CI\/CD Pipelines\" \/>\n<meta name=\"twitter:image\" content=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2019\/05\/copertine-blog_Codepipeline_Tavola-disegno-1-copia.png\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Matteo Moroni\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"8 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-create-flexible-ci-cd-pipeline-on-aws-with-fargate-and-sqs\/\",\"url\":\"https:\/\/blog.besharp.it\/how-to-create-flexible-ci-cd-pipeline-on-aws-with-fargate-and-sqs\/\",\"name\":\"How to create flexible CI\/CD Pipeline on AWS with Fargate and SQS - Proud2beCloud Blog\",\"isPartOf\":{\"@id\":\"https:\/\/blog.besharp.it\/#website\"},\"datePublished\":\"2019-05-17T13:58:41+00:00\",\"dateModified\":\"2021-03-29T15:17:03+00:00\",\"author\":{\"@id\":\"https:\/\/blog.besharp.it\/#\/schema\/person\/0b3e69eb2dcb125d58476b906ec1c7bc\"},\"description\":\"How to create flexible CI\/CD Pipeline on AWS with AWS Fargate and Amazon SQS\",\"breadcrumb\":{\"@id\":\"https:\/\/blog.besharp.it\/how-to-create-flexible-ci-cd-pipeline-on-aws-with-fargate-and-sqs\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/blog.besharp.it\/how-to-create-flexible-ci-cd-pipeline-on-aws-with-fargate-and-sqs\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/blog.besharp.it\/how-to-create-flexible-ci-cd-pipeline-on-aws-with-fargate-and-sqs\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/blog.besharp.it\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"How to create flexible CI\/CD Pipeline on AWS with Fargate and SQS\"}]},{\"@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\/0b3e69eb2dcb125d58476b906ec1c7bc\",\"name\":\"Matteo Moroni\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/blog.besharp.it\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/acad790b9bb4c6d62e076ecdc1debb35?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/acad790b9bb4c6d62e076ecdc1debb35?s=96&d=mm&r=g\",\"caption\":\"Matteo Moroni\"},\"description\":\"DevOps e Solution Architect di beSharp, mi occupo di sviluppare soluzioni Saas, Data Analysis, HPC e di progettare architetture non convenzionali a complessit\u00e0 divergente. Appassionato di informatica e fisica, da sempre lavoro nella prima e ho un PhD nella seconda. Parlare di tutto ci\u00f2 che \u00e8 tecnico e nerd mi rende felice!\",\"url\":\"https:\/\/blog.besharp.it\/author\/matteo-moroni\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"How to create flexible CI\/CD Pipeline on AWS with Fargate and SQS - Proud2beCloud Blog","description":"How to create flexible CI\/CD Pipeline on AWS with AWS Fargate and Amazon SQS","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-create-flexible-ci-cd-pipeline-on-aws-with-fargate-and-sqs\/","og_locale":"en_US","og_type":"article","og_title":"CI\/CD Pipeline on AWS with AWS Fargate and Amazon SQS","og_description":"Using AWS Fargate and Amazon SQS to set up flexible CI\/CD Pipelines","og_url":"https:\/\/blog.besharp.it\/how-to-create-flexible-ci-cd-pipeline-on-aws-with-fargate-and-sqs\/","og_site_name":"Proud2beCloud Blog","article_published_time":"2019-05-17T13:58:41+00:00","article_modified_time":"2021-03-29T15:17:03+00:00","og_image":[{"width":1668,"height":1250,"url":"https:\/\/blog.besharp.it\/wp-content\/uploads\/2019\/05\/copertine-blog_Codepipeline_Tavola-disegno-1-copia.png","type":"image\/png"}],"author":"Matteo Moroni","twitter_card":"summary_large_image","twitter_title":"CI\/CD Pipeline on AWS with AWS Fargate and Amazon SQS","twitter_description":"Using AWS Fargate and Amazon SQS to set up flexible CI\/CD Pipelines","twitter_image":"https:\/\/blog.besharp.it\/wp-content\/uploads\/2019\/05\/copertine-blog_Codepipeline_Tavola-disegno-1-copia.png","twitter_misc":{"Written by":"Matteo Moroni","Est. reading time":"8 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/blog.besharp.it\/how-to-create-flexible-ci-cd-pipeline-on-aws-with-fargate-and-sqs\/","url":"https:\/\/blog.besharp.it\/how-to-create-flexible-ci-cd-pipeline-on-aws-with-fargate-and-sqs\/","name":"How to create flexible CI\/CD Pipeline on AWS with Fargate and SQS - Proud2beCloud Blog","isPartOf":{"@id":"https:\/\/blog.besharp.it\/#website"},"datePublished":"2019-05-17T13:58:41+00:00","dateModified":"2021-03-29T15:17:03+00:00","author":{"@id":"https:\/\/blog.besharp.it\/#\/schema\/person\/0b3e69eb2dcb125d58476b906ec1c7bc"},"description":"How to create flexible CI\/CD Pipeline on AWS with AWS Fargate and Amazon SQS","breadcrumb":{"@id":"https:\/\/blog.besharp.it\/how-to-create-flexible-ci-cd-pipeline-on-aws-with-fargate-and-sqs\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/blog.besharp.it\/how-to-create-flexible-ci-cd-pipeline-on-aws-with-fargate-and-sqs\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/blog.besharp.it\/how-to-create-flexible-ci-cd-pipeline-on-aws-with-fargate-and-sqs\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/blog.besharp.it\/"},{"@type":"ListItem","position":2,"name":"How to create flexible CI\/CD Pipeline on AWS with Fargate and SQS"}]},{"@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\/0b3e69eb2dcb125d58476b906ec1c7bc","name":"Matteo Moroni","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/blog.besharp.it\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/acad790b9bb4c6d62e076ecdc1debb35?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/acad790b9bb4c6d62e076ecdc1debb35?s=96&d=mm&r=g","caption":"Matteo Moroni"},"description":"DevOps e Solution Architect di beSharp, mi occupo di sviluppare soluzioni Saas, Data Analysis, HPC e di progettare architetture non convenzionali a complessit\u00e0 divergente. Appassionato di informatica e fisica, da sempre lavoro nella prima e ho un PhD nella seconda. Parlare di tutto ci\u00f2 che \u00e8 tecnico e nerd mi rende felice!","url":"https:\/\/blog.besharp.it\/author\/matteo-moroni\/"}]}},"_links":{"self":[{"href":"https:\/\/blog.besharp.it\/wp-json\/wp\/v2\/posts\/645"}],"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\/9"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.besharp.it\/wp-json\/wp\/v2\/comments?post=645"}],"version-history":[{"count":0,"href":"https:\/\/blog.besharp.it\/wp-json\/wp\/v2\/posts\/645\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.besharp.it\/wp-json\/wp\/v2\/media\/649"}],"wp:attachment":[{"href":"https:\/\/blog.besharp.it\/wp-json\/wp\/v2\/media?parent=645"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.besharp.it\/wp-json\/wp\/v2\/categories?post=645"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.besharp.it\/wp-json\/wp\/v2\/tags?post=645"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}