Sign in to scale group nodes

Scale group nodes keep the SSH keys and the root password saved with the image. Sign in to them the way you signed in to the node you saved the image from: over SSH with its key, or on Access Console as root with its root password.

Before you begin

• The scale group reads Running, Scaling, or Cooldown, the states in which its Active Node Details tab is available.
• The saved image holds the SSH key and the root password you want to use. To add a key to the node you save the image from, see Add an SSH key to a node.
• For SSH, one of the scale group’s security groups allows inbound TCP port 22 from your address. Add the rule, or attach a security group that has it. See Manage a scale group’s network and security groups.
• For Access Console, your role in the current project has the update permission for Auto Scaling.

Find the node’s address

In MyAccount, under Compute, click Auto Scaling, click your scale group, and open its Active Node Details tab. It lists each node with its Scale Node Name, Public IP, and Private IP. Connect to the Public IP. If a node shows N/A under Public IP, connect to its Private IP from inside the scale group’s private network.

Sign in over SSH

Connect with the private key that matches a key saved in the image, where <key-file> is that private key, <user> the user you signed in as on the node you saved the image from, and <node-ip> the node’s address:

ssh -i <key-file> <user>@<node-ip>

For more on SSH, see Connect to a Linux node.

A new node may get the public IP of a node the scale group removed earlier. If SSH then warns that the remote host identification has changed, remove the old entry for that address, and connect again:

ssh-keygen -R <node-ip>

Sign in on Access Console

1. On Active Node Details, open the node’s menu, and click Access Console. It is available whatever the node’s status.
2. The node’s console opens in a new window and asks for a login. Sign in as root with the saved image’s root password.

You are now signed in to the node. If sign-in fails, see SSH to a new node fails.