As we explained in Quickstart , 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 Create an OpenSSH Key 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 our Orbiter dashboard of the environment you want to connect to → Instances → project-environment-natgw → Public IP.
Linux/macOS
On your local machine (eg workstation or enterprise-internal jump server) add your secret ssh key to your ssh-agent:
ssh-add /path/to/privatekey
ssh -A ProjectUser@IP
The most likely path to your secret ssh key is ~/.ssh/id_rsa.