1 - Harness ECS Delegate

Updated 2 weeks ago by Michael Cretzman

The Harness ECS Delegate is software you install in your environment that connects to the Harness Manager and performs Continuous Delivery tasks.

The ECS cluster for the ECS Delegate is run in the same VPC as the ECS cluster(s) where you will deploy your ECS services. You can run the ECS Delegate in the same subnet as a cluster, which is often the easiest way to manage the Delegate.

Most importantly, in order for Harness to obtain metadata about ECS containers and use that in its Continuous Verification features (using verification providers and Harness machine learning algorithms), the Harness Delegate must be running in the same VPC as the target ECS cluster. This is a restriction of AWS.

For steps on installing and running the Harness ECS Delegate, see the following:

You can also use a Delegate on an EC2 instance that assumes the same role as your ECS cluster. In this case, update the trust relationship of the IAM role so that the EC2 instances can assume the role. You can set this up in the Trust relationships tab of the IAM role:

Add a Delegate Tag

When Harness makes a connection to your ECS cluster via its Delegates, it will select the best Delegate according to its history and other factors. To ensure a specific Delegate is used by a Harness entity, you can scope the Delegate as explained in Delegate Scope, or you can add tags to Delegates and then reference the tags in commands and configurations.

For this guide, we will use a Delegate Tag. Later, when you add an AWS Cloud Provider to your Harness account, you will use the Delegate Tag you added to ensure the Cloud Provider uses that Delegate.

Here is an example of an AWS Cloud Provider using the Delegate Tag of a Harness Delegate:

For steps on using Delegate Tags with your ECS Delegate, see the steps in Set up ECS Delegate in AWS.


ECS Connectors and Providers Setup

How did we do?