As we explained in https://root360.atlassian.net/wiki/spaces/KB/pages/2014353119 , only the jump server can be accessed directly from the internet. All the other instances are only accessible through that jump server. The following explains how to configure your ssh client to make that possible.

Preconditions

• You do have a key created via https://root360.atlassian.net/wiki/spaces/KB/pages/2014353044 and its is provisioned by root360 to the requested environment.

• The permissions on the file of your secret ssh key must be set so that only the owner can read them. For example in Linux with rights "600".

Username of Project User

The ssh username is of the format "project-environment". You can get the name of your project with us through our Orbiter dashboard on my.root360.cloud: The listed environments always have the format "company-project-environment".

IP to connect to

You need to connect to the  jumpserver, also known as the bastionhost or natgw. You can get its public IP through our Orbiter dashboard of the environment you want to connect to in Instances → project-environment-natgw → Public IP.

Linux/macOS and OpenSSH

On your local machine (e.g. workstation or enterprise-internal jump server) make sure that you have ssh-agent running. You will get this response if no agent is running or your current shell is not aware of it:

Start an agent and export its environment variables into your current shell:

(see for example https://wiki.archlinux.org/title/SSH_keys#SSH_agents for further information about ssh agents and how to automate this process)

Add your secret ssh key to your ssh-agent with ssh-add and use ssh -A to use the ssh-agent. This is needed to connect to your application instances from the jumpserver:

The most likely path to your secret ssh key is ~/.ssh/id_rsa. You can check your currently loaded keys with ssh-add -l.

When you have connected to the jumpserver you can use r3 instance list to get a list of internal IPs of your application instances. You can connect to them simply with ssh <internal-ip>, ssh -A is not necessary for these internal connections.

Windows (Putty)

• Open

  

  Putty Agent pageant.exe must be active and have the appropriate key loaded. You can download it at https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html

• In the configuration of Putty, the AgentForwarding must be activated under Category> Connection > SSH> Auth. 

• Under Category> Connection> Data, the ProjectUser is stored.

Commands on the Jump Server / Bastion Host

• On Jump Server you can make use of
  r3 --help

• To Jump to an instance use
  ssh [WebInstanceIP]

Known Issues

If you haven't added your private key to your ssh agent the following error occur:

Related tutorials

Related components