You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: pages/instances/how-to/connect-to-instance.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -64,7 +64,7 @@ This page shows how to connect to your Scaleway Instance via SSH. Thanks to the
64
64
click **Instances** in the Compute section of the side menu. A list of your
65
65
Instances and their associated IP addresses will display.
66
66
</Message>
67
-
4. In the side menu, under **Connection**, navigate to the **Auth**sub-category. Do this by expanding **Connection**, then **SSH**, and finally clicking on **Auth**:
67
+
4. In the side menu, expand the **Connection**, **SSH**and **Auth** submenus, then click **Credentials**:
68
68
<Lightboxsrc="scaleway-putty-ssh.webp"alt="" />
69
69
5. Click the **Browse** button and select the private key file you [generated previously](/organizations-and-projects/how-to/create-ssh-key/).
70
70
6. Click **Open** at the bottom of the screen to open a connection to the Instance. Upon the first connection, PuTTY asks you to allow the connection to the host.
It is strongly recommended to use [Ed25519](https://en.wikipedia.org/wiki/EdDSA#Ed25519) for increased security and performance. If you cannot use Ed25519 keys, you can create an RSA4096 key as a fallback option:
3. When prompted to enter a file path in which to save the key, either specify a path or press **Enter** to accept the default location (`~/.ssh/id_ed25519`).
47
-
```
48
-
Enter file in which to save the key (~/.ssh/id_ed25519):
49
-
```
50
-
4. Enter a passphrase when prompted. This step is optional but recommended for increased security. If you do not want to set a passphrase, press **Enter** directly.
51
-
```
52
-
Enter passphrase (empty for no passphrase):
53
-
```
54
-
5. Confirm the passphrase by entering it again when prompted, and press **Enter**:
55
-
```
56
-
Enter same passphrase again:
57
-
```
29
+
<Macroid="requirements" />
58
30
59
-
The key pair will be generated in the specified filepath. The key pair consists of:
60
-
- The public key, named `id_ed25519.pub`
61
-
- The private key, named `id_ed25519`
62
-
<Messagetype="important">
63
-
Ensure that the private key file (`<key_name>`) is kept secure. Do not share it with unauthorized parties. You can set appropriate permissions on the file to restrict access using the following command:
64
-
```bash
65
-
chmod 600 <key_name>
66
-
```
67
-
</Message>
68
-
6. Display the content of the public key with the following command and copy it:
69
-
```bash
70
-
cat ~/.ssh/id_ed25519.pub
71
-
```
72
-
7. Copy the content of the public key displayed. You will need this in the next step. It should look something like this:
- A Scaleway account logged into the [console](https://console.scaleway.com)
32
+
-[Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
76
33
77
-
### How to generate an Ed25519 SSH key pair on Windows
78
-
79
-
On Windows, you can use the third-party application [PuTTYgen](https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html) to generate an SSH key pair.
80
-
81
-
1. Download and install [PuTTY](https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html) on your local computer. The **PuTTYgen** application is automatically installed along with the main PuTTY application.
- Fill in the **Key comment** field with a name to help you identify this key pair.
93
-
- Click the **Save public key** button and save it in the folder of your choice.
94
-
- Click the **Save private key** button to save it in the same folder.
95
-
<Messagetype="important">
96
-
Ensure that the private key file (`<key_name>`) is kept secure. Do not share it with unauthorized parties.
97
-
</Message>
98
-
- Select the content of the public key (the sequence of characters under "Public key for pasting into OpenSSH authorized_keys file") and copy it, as you will need this in the next step/
99
-
100
-
## How to generate a RSA SSH key pair
101
-
102
-
<Messagetype="tip">
103
-
- Windows-based Instances require a special type of SSH key known as RSA (Rivest-Shamir-Adleman), a prevalent asymmetric cryptographic algorithm used for secure data transmission.
104
-
- It is recommended to use [Ed25519 keys](#how-to-generate-an-ed25519-ssh-key-pair) for SSH connections to your Linux Instances.
34
+
## How to generate an SSH key pair
35
+
36
+
### How to generate an Ed25519 SSH key pair
37
+
38
+
Ed25519 SSH key pairs allow you to connect to your Linux-based Instances from a macOS, Linux or Windows machine.
39
+
40
+
<Tabsid="Ed25519-ssh-key-pair">
41
+
<TabsTablabel="macOS and Linux">
42
+
43
+
On macOS and Linux, you can generate the SSH key pair directly from the terminal.
44
+
45
+
1. Open a terminal.
46
+
47
+
2. Run the following command to generate a new key:
It is strongly recommended to use [Ed25519](https://en.wikipedia.org/wiki/EdDSA#Ed25519) for increased security and performance. If you cannot use Ed25519 keys, you can create an RSA4096 key as a fallback option:
3. When prompted to enter a file path in which to save the key, either specify a path or press **Enter** to accept the default location (`~/.ssh/id_ed25519`).
58
+
```
59
+
Enter file in which to save the key (~/.ssh/id_ed25519):
60
+
```
61
+
4. Enter a passphrase when prompted. This step is optional but recommended for increased security. If you do not want to set a passphrase, press **Enter** directly.
62
+
```
63
+
Enter passphrase (empty for no passphrase):
64
+
```
65
+
5. Confirm the passphrase by entering it again when prompted, and press **Enter**:
66
+
```
67
+
Enter same passphrase again:
68
+
```
69
+
70
+
The key pair will be generated in the specified filepath. The key pair consists of:
71
+
- The public key, named `id_ed25519.pub`
72
+
- The private key, named `id_ed25519`
73
+
<Messagetype="important">
74
+
Ensure that the private key file (`<key_name>`) is kept secure. Do not share it with unauthorized parties. You can set appropriate permissions on the file to restrict access using the following command:
75
+
```bash
76
+
chmod 600 <key_name>
77
+
```
78
+
</Message>
79
+
6. Display the content of the public key with the following command and copy it:
7. Copy the content of the public key displayed, as you will need this in the next step.
88
+
89
+
</TabsTab>
90
+
<TabsTablabel="Windows">
91
+
92
+
On Windows, you can use the third-party application [PuTTYgen](https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html) to generate an SSH key pair.
93
+
94
+
1. Download and install [PuTTY](https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html) on your local computer. The **PuTTYgen** application is automatically installed along with the main PuTTY application.
- Fill in the **Key comment** field with a name to help you identify this key pair.
106
+
- Click the **Save public key** button and save it in the folder of your choice.
107
+
- Click the **Save private key** button to save it in the same folder.
108
+
<Messagetype="important">
109
+
Ensure that the private key file (`<key_name>`) is kept secure. Do not share it with unauthorized parties.
110
+
</Message>
111
+
- Select the content of the public key (the sequence of characters under "Public key for pasting into OpenSSH authorized_keys file") and copy it, as you will need this in the next step.
112
+
</TabsTab>
113
+
</Tabs>
114
+
115
+
### How to generate a RSA SSH key pair
116
+
117
+
RSA SSH key pairs allow you to connect to your Windows-based Instances from a macOS, Linux or Windows machine. RSA (Rivest-Shamir-Adleman) is a prevalent asymmetric cryptographic algorithm used for secure data transmission.
118
+
119
+
<Messagetype="note">
120
+
We recommend you use [Ed25519 keys](#how-to-generate-an-ed25519-ssh-key-pair) for SSH connections to your Linux Instances.
105
121
</Message>
106
122
107
123
1. Open a terminal or command prompt on your local machine. This could be Terminal on macOS/Linux or the Command Prompt/PowerShell on Windows.
@@ -127,19 +143,21 @@ On Windows, you can use the third-party application [PuTTYgen](https://www.chiar
127
143
128
144
You must upload the content of the public part of the SSH key pair you just generated to the Scaleway interface. This is then transferred to your Instance during the boot process. You can then connect and authenticate from your local machine, where your private key is stored, to the remote Instance, where the public key can be found.
129
145
130
-
1. Log into the [Scaleway console](https://console.scaleway.com), and navigate to the [Credentials](/iam/concepts/#api-key) tab of your Project Dashboard:
2. Scroll down to the **SSH key** section, and click **Add a new SSH key**.
133
-
<Lightboxsrc="scaleway-ssh-keys.webp"alt="" />
134
-
3. Paste the content of the public key (which you copied in the previous step) into the pop-up box, and optionally add a description. Then click **Add an SSH key**.
146
+
1. Log into the [Scaleway console](https://console.scaleway.com).
135
147
136
-
You will now be able to [connect to your Instances via SSH](/instances/how-to/connect-to-instance/).
148
+
2. Click the name of your Organization in the top-right corner, then select **SSH Keys**.
137
149
138
-
<Messagetype="tip">
139
-
If you have any difficulties connecting to an Instance after uploading a new public SSH key to your Project, try the following:
140
-
- If you cannot connect to your Instance at all via SSH, reboot your Instance from the console and try again.
141
-
- If you can connect to your Instance using a previously uploaded SSH key but not the new one, go ahead and connect to your Instance with the old key. Once connected, run the `scw-fetch-ssh-keys --upgrade` command, which launches a script on your Instance to update your SSH keys. You can then check that the new key has been added to the `authorized_keys` file (`~/.ssh/authorized_keys`). Note that this command works only for Instances.
142
-
- For further information, refer to the [SSH connection troubleshooting](/instances/troubleshooting/cant-connect-ssh/) documentation.
143
-
</Message>
150
+
2. Click **+ Add SSH key**. A popup displays.
151
+
152
+
3. Enter a name for your SSH key, paste the content of the public key copied earlier into the **Public key** box, then click **Add SSH key**.
153
+
154
+
You can now [connect to your Instances via SSH](/instances/how-to/connect-to-instance/).
155
+
156
+
## Troubleshooting
157
+
158
+
If you have any difficulties connecting to an Instance after uploading a new public SSH key to your Project, try the following:
144
159
160
+
- If you cannot connect to your Instance at all via SSH, reboot your Instance from the console and try again.
161
+
- If you can connect to your Instance using a previously uploaded SSH key but not the new one, go ahead and connect to your Instance with the old key. Once connected, run the `scw-fetch-ssh-keys --upgrade` command, which launches a script on your Instance to update your SSH keys. You can then check that the new key has been added to the `authorized_keys` file (`~/.ssh/authorized_keys`). Note that this command works only for Instances.
145
162
163
+
For further information, refer to the dedicated [SSH connection troubleshooting](/instances/troubleshooting/cant-connect-ssh/) documentation.
0 commit comments