CI/CD with AWS Fargate

Hero Banner Description Text

AWS Fargate.pngContinuous Integration & Continuous Deployment with AWS Fargate

Continuous Integration & Continuous Deployment (CI/CD) pipelines enable automation for software delivery, and have become especially useful when going serverless. The additional automation promotes efficiency, no longer requiring that developers manually take care of the delivery steps. Developing CI/CD pipelines on AWS can be done using the AWS Fargate ECS launch type, effectively bringing about an additional set of automation by removing the need to manage the application's infrastructure.

Learn more below about how services such as AWS CodePipeline works with AWS Fargate to bring added ease in deploying applications.

fargate diagram.png

Building a Modern CI/CD Pipeline with GitOps on AWS Fargate

Migrating from monolith to microservice development enables the use of a CI/CD pipeline that can help to automate the software delivery process. In this growing serverless world, CI/CD is a vehicle for efficiency, and can be built using GitOps and run on AWS Fargate. In this post on the AWS Blog, Shimon Tolts, CTO and co-founder of, walks through the process of setting up a CI/CD pipeline and all the components that go with it. 

CI/CD with AWS Developer Tools and AWS Fargate

In order to implement a CI/CD Pipeline, there are a few different services. The CI/CD stack for Fargate service is built using AWS CodeCommit, moves on to AWS CodeBuild, and is completed with AWS CodePipeline before it is pushed out and deployed with AWS Fargate.

Learn more about the process and watch a demo in the video below:

Customer Story: KPMG's Customer Due Diligence Solution

One of the Big Four accounting organizations, KPMG is a multinational professional services network that provides Audit, Tax and Advisory services. As a company that is 90% in on AWS, they have 250 production workloads, 90 engineers, and 150+ internal projects, and were looking to evolve their customer due diligence (CDD) solution by deploying on AWS Fargate instead of EC2. Deploying with AWS Fargate lead to the costs decreasing and speed of delivery increasing.

Their solution is made up of a number of microservices which are deployed to containers using AWS Fargate. The video below will dive into the details of the architecture of the solution, talking through the AWS resources used in the solution, including DynamoDB, ECS, Fargate and S3, CI/CD and automation, with a focus around security to meet banking regulatory requirements. In addition, it will explain how the infrastructure and applications are deployed using third party tools, and the best practices when running containers in production workloads.