Create Pull Request
| Date | Scan | Status | Result |
|---|---|---|---|
| 2025-07-12 23:44 | #41 | cancelled |
Biased
|
| 2025-07-12 00:58 | #8 | cancelled |
Clean
|
| 2025-07-10 05:06 | #7 | processing |
Clean
|
> [!NOTE] > CycleCloud chooses an unused ephemeral port for the tunnel to the Windows VM. You can configure the `cyclecloud` command to use a single bastion host for all your connections:
With the above directive, you can run `cyclecloud connect htcondor-scheduler` without specifying any details about the bastion server. You can also use `cyclecloud connect` to connect a Windows VM. Executing the following command will create an RDP connection over an SSH tunnel. Additionally, it will launch the Microsoft RDP client on OSX and Windows:
This connects to the bastion and then immediately runs SSH again, so you get a terminal on the target VM. You may need to specify a user other than `cyclecloud` on the VM if your cluster is configured differently. The `-A` argument forwards the agent connection so your private key on your local machine is used automatically. Note that agent forwarding is a chain, so the second SSH command also includes `-A` so that any subsequent SSH connections initiated from the target VM also use your local private key. ### Connecting to Services on the Target VM You can use the SSH connection to connect to services on the target VM, such as a Remote Desktop, a database, etc. For example, if the target VM is Windows, you can create a Remote Desktop tunnel by connecting to the target VM with a similar SSH command from above, using the `-L` argument: