Here are six ways to set up a CD/CI pipeline for a .Net Core based console application hosted on an EC2 instance:

1. AWS CodePipeline with AWS CodeBuild:

   • Use AWS CodePipeline to create a pipeline that automatically builds, tests, and deploys your .Net Core console application.
   • Configure AWS CodeBuild to build your application using a buildspec.yml file that specifies the build steps.
   • Set up the pipeline to deploy the application to your EC2 instance using AWS CodeDeploy or custom deployment scripts.

2. Jenkins with AWS EC2 Plugin:

   • Install Jenkins on a separate EC2 instance or use a managed Jenkins service.
   • Create a Jenkins pipeline using a Jenkinsfile that defines the build, test, and deployment stages.
   • Use the AWS EC2 Plugin to deploy the application to your EC2 instance as part of the pipeline.
   • Configure the necessary AWS credentials and security groups to allow Jenkins to access your EC2 instance.

3. GitLab CI/CD with AWS integration:

   • Host your .Net Core console application code on GitLab.
   • Create a .gitlab-ci.yml file to define the CI/CD pipeline stages, including build, test, and deploy.
   • Use GitLab's built-in AWS integration to deploy the application to your EC2 instance.
   • Configure the necessary AWS credentials and security groups in GitLab for deployment.

4. Azure DevOps with AWS Tools for Microsoft Visual Studio Team Services (VSTS):

   • Use Azure DevOps (formerly VSTS) to create a build and release pipeline for your .Net Core console application.
   • Install the AWS Tools for Microsoft Visual Studio Team Services extension in Azure DevOps.
   • Configure the build pipeline to build and test your application.
   • Set up the release pipeline to deploy the application to your EC2 instance using the AWS Tools extension.

5. CircleCI with AWS EC2 deployment:

   • Host your .Net Core console application code on a version control system supported by CircleCI (e.g., GitHub, Bitbucket).
   • Create a .circleci/config.yml file to define the CI/CD pipeline steps.
   • Use CircleCI's AWS EC2 deployment feature to deploy the application to your EC2 instance.
   • Configure the necessary AWS credentials and permissions in CircleCI for deployment.

6. GitHub Actions with AWS deployment:

   • Host your .Net Core console application code on GitHub.
   • Create a GitHub Actions workflow file (e.g., .github/workflows/main.yml) to define the CI/CD pipeline.
   • Use the AWS CLI or AWS SDKs in your workflow to build, test, and deploy the application to your EC2 instance.
   • Store the necessary AWS credentials securely in GitHub Secrets and use them in your workflow.

These are just a few examples of how you can set up a CD/CI pipeline for a .Net Core console application hosted on an EC2 instance. The choice of tools and services depends on your specific requirements, familiarity with the platforms, and integration preferences. Each approach has its own configuration steps and best practices, so refer to the respective documentation and guides for detailed implementation instructions.