reference deployment

CI/CD for .NET Applications on AWS Fargate

Deploy an automated pipeline to build and deploy a .NET application to Fargate

This solution deploys a continuous integration and continuous delivery (CI/CD) pipeline for .NET applications to the Amazon Web Services (AWS) Cloud. It's for users who want to create a CI/CD pipeline that builds and deploys a containerized .NET application to AWS Fargate. 

Built using the AWS portfolio of DevOps services and best practices, this solution serves as both a reference architecture and a template for creating a fully implemented CI/CD pipeline for deploying a .NET application to AWS Fargate. It also demonstrates how to use Fargate to host a containerized application using a fully managed AWS infrastructure.

AWS logo

This solution was developed by AWS.

  •  What you'll build
  • This solution sets up the following:

    • A highly available architecture that spans two Availability Zones.
    • A virtual private cloud (VPC) configured with public and private subnets, according to AWS best practices, to provide you with your own virtual network on AWS.
    • AWS CodePipeline to create a pipeline with source, build, and deploy stages. The pipeline is invoked when a developer commits a code change to the AWS CodeCommit repository.
      • CodeCommit to host the application source code in a Git repository.  
      • AWS CodeBuild to serve as a CodePipeline stage for performing the build process for a container image.
      • Amazon Elastic Container Service (Amazon ECS) to deploy the updated application container image.
    • Amazon Simple Storage Service (Amazon S3) to store CodePipeline artifacts.
    • AWS Identity and Access Management (IAM) roles for the CI/CD pipeline’s build and deployment process.  
    • In the public subnets, managed NAT gateways to allow outbound internet access for resources in the private subnets.
    • In the private subnets:
      • AWS Fargate tasks to host the containers using Amazon ECS.
      • An Application Load Balancer to direct traffic to the Fargate cluster.
  •  How to deploy
  • To deploy the solution, follow the instructions in the deployment guide, which includes these steps.

    1. Sign in to your AWS account. If you don't have an account, sign up at
    2. Launch the solution. The stack takes about 15 minutes to deploy. Before you create the stack, choose the AWS Region from the top toolbar. 
    3. Test the deployment. 

    Amazon may share user-deployment information with the AWS Partner that collaborated with AWS on this solution.  

  •  Costs and licenses
  • You are responsible for the cost of the AWS services and any third-party licenses used while running this solution. There is no additional cost for using the solution.

    This solution includes configuration parameters that you can customize. Some of these settings, such as instance type, affect the cost of deployment. For cost estimates, refer to the pricing pages for each AWS service you use. Prices are subject to change.

    Tip: After you deploy a solution, create AWS Cost and Usage Reports to track associated costs. These reports deliver billing metrics to an Amazon Simple Storage Service (Amazon S3) bucket in your account. They provide cost estimates based on usage throughout each month and aggregate the data at the end of the month. For more information, refer to What are AWS Cost and Usage Reports?