Connect to Your Repos and Target SSH Platforms

Traditional (SSH) deployments typically pull application packages from artifact servers and then deploy to target virtual machines on a cloud platform. They can also target physical servers. Harness supports connecting and deploying to all target types.

This topic covers the steps needed to connect Harness to your artifact servers and target environments.

Before You Begin

• Traditional Deployments (SSH) Overview
• Harness Delegate Overview
• Harness Key Concepts

Step 1: Set Up a Harness Delegate

The Delegate needs to be able to connect to the artifact server or repository containing the file, and the target host where the file will be deployed. Typically, the Delegate is installed on a host in the same subnet as the target host.

For steps on installing the Delegate, see Harness Delegate Overview.

For AWS, you can install the Delegate on an EC2 instance and then have the Harness Cloud Provider assume the IAM role used by the Delegate host. For more information, see Delegate Selectors in Select Delegates for Specific Tasks with Selectors.

Step 2: Connect to Your Artifact Server

Harness retrieves the package file from an artifact source using a Harness Artifact Server and deploys it to the target host using a Cloud Provider.

See Add Artifact Servers.

Step 3: Connect to Your Cloud Provider or Physical Server

You connect Harness to the target environment for your deployment. This can be a VM in the cloud or a physical server.

See Add Cloud Providers and Add Physical Data Center as Cloud Provider.

Configure As Code

To see how to configure the settings in this topic using YAML, configure the settings in the UI first, and then click the YAML editor button.