Introduction

You need to setup Lightwing CLI to do SSH. This is required for lightwing to detect the TCP traffic and keep your resources alive during the SSH session.

SSH into instances

The instances managed by lightwing will not be running during idle time. Before attempting SSH, lightwing will have to start the instances and setup a SSH tunnel.

qa1 in this example is the Autostopping gateway name.

> lwc ssh qa1
lwc ssh qa1
INFO[0000] Warming up service. Current status: down
INFO[0005] Warming up service. Current status: warmingup
INFO[0025] Warming up service. Current status: warmingup
SSH is setup. Use the following info to connect


SSH Host  |IP            |SSH Port |Command
localhost |52.207.81.193 |56176    |ssh -p 56176 username@localhost
localhost |35.171.6.250  |41024    |ssh -p 41024 username@localhost
localhost |52.91.190.219 |38371    |ssh -p 38371 username@localhost

In this case, lightwing warmed up the service qa1 and setup SSH tunnel to all the instances under the gateway qa1.

To SSH, simply do:

> ssh -p 56176 ubuntu@localhost

RDP into Windows instances

Lightwing can also setup a RDP tunnel to connect to Windows instances.

. qa1 in this example is the Autostopping gateway name.

> lwc rdp qa1
lwc ssh qa1
INFO[0000] Warming up service. Current status: down
INFO[0005] Warming up service. Current status: warmingup
INFO[0025] Warming up service. Current status: warmingup
RDP is setup. Use the following info to connect


Host      |IP            |Port
localhost |52.207.81.193 |15022

Open up your RDP client and configure the above details to connect.

RDP With Lightwing Autostopping