SSH Quick Start Guide

The Gateway can proxy SSH connections, allowing users to access SSH servers through their Twingate identity without managing individual SSH keys. See SSH Overview for details on how it works.

Prerequisites

• A Twingate account with administrator privileges
• Terraform installed
• A cloud provider account (see individual guides for specific requirements)

Getting started

The recommended way to get started is with the Twingate Terraform provider, which provides complete, runnable examples. Each guide includes full Terraform configurations, startup scripts, and step-by-step deployment instructions.

These guides use a local SSH CA for simplicity, where the Gateway holds the CA private key and signs certificates directly. This is a good way to try out SSH access through the Gateway, but for production deployments consider using an external CA such as HashiCorp Vault. See SSH Overview for more on CA modes.

• Local SSH CA on AWS - Deploy a Gateway with SSH access on AWS.
• Local SSH CA on DigitalOcean - Deploy a Gateway with SSH access on DigitalOcean.
• Local SSH CA on GCE - Deploy a Gateway with SSH access on Google Compute Engine.