Traditional (SSH) Deployments How-tos

The following topics discuss how to perform Traditional deployments using application package files and a runtime environment (Tomcat, JBoss) in Harness.

These deployments are different from Harness deployments using container orchestration platforms like Kubernetes, Helm, Pivotal, AWS ECS, and Azure.

Traditional deployments involve obtaining an application package from an artifact source, such as a WAR file in an AWS S3 bucket, and deploying it to a target host, such an AWS AMI.

For an overview, see Traditional Deployments (SSH) Overview.

Traditional Deployments How-tos:

• Connect to Your Repos and Target SSH Platforms
• Add Artifacts and App Stacks for Traditional (SSH) Deployments
• Add Scripts for Traditional (SSH) Deployments
• Define Your Traditional (SSH) Target Infrastructure
• Create Default Application Directories and Variables
• Create a Basic Workflow for Traditional (SSH) Deployments