SSH to log into a Broker UAI and reach the End-User UAIs on demand.
Log in to the Broker UAI.
The following example is the first login for the vers
user:
vers> ssh vers@35.226.246.154
The authenticity of host '35.226.246.154 (35.226.246.154)' can't be established.
ECDSA key fingerprint is SHA256:k4ef6vTtJ1Dtb6H17cAFh5ljZYTl4IXtezR3fPVUKZI.
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Warning: Permanently added '35.226.246.154' (ECDSA) to the list of known hosts.
Password:
Creating a new UAI...
The authenticity of host '10.21.138.52 (10.21.138.52)' can't be established.
ECDSA key fingerprint is SHA256:TX5DMAMQ8yQuL4YHo9qFEJWpKaaiqfeSs4ndYXOTjkU.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '10.21.138.52' (ECDSA) to the list of known hosts.
There are several things to notice here:
.ssh/authorized_keys
entry had been present, there would not have been a password prompt. Home directory trees can be mounted as volumes just as any other directory can.vers
has never logged into this Broker UAI before.Log out of the Broker UAI.
Log in to the Broker UAI again.
The next time vers
logs in, it will look similar to the following:
vers> ssh vers@35.226.246.154
Password:
vers@uai-vers-ee6f427e-6c7468cdb8-2rqtv>
Only the password prompt appears now, because the hosts are all known and the End-User UAI exists but there is no .ssh/authorized_keys
known yet by the Broker UAI for vers
.