This page shows how to create and connect to your first Scaleway instance.
After you’ve launched your server, you can connect to it as root and use it as you wish.
There are five steps to provision a new server
Important: Your SSH public keys are fetched during the boot process.
If you add them after your server is booted, they will not be added to your
If you do not want the keys to be downloaded during the next boot, execute the following command on your server:
root@c1-X-Y-Z-T:~# echo manual > /etc/init/ssh-keys.override
Before starting, click the “Create Server” button in the control panel.
You will land on the server-creation page where you must input basic information for your server:
After inputting your server basic information, you have to choose a starting image for your server.
You can choose this image from three sources:
Marketplace: We provide an up-to-date list of linux distributions.
My images: You can populate your own list of server templates. See also Create your own image
Snapshots: You can recover a server from a previously saved state. See also Backup your data with snapshots
A simple solution to increase the storage for your servers is to add extra volumes.
You can add extra storage to your server. Added storage can be an existing volume or new volume.
Click the “Create Server” button. This action starts your server. In a few seconds, your server will be ready to use.
When your server is running, you can see the server’s IP address in the server list on the control panel.
On a Mac or Linux computer, open your terminal program and in the shell just type the following command:
john@localhost:~$ ssh -i ~/.ssh/your_private_key root@your_server_ip
Allow the connection to the host:
Well done, you are now logged into your server!
On Windows, you will need a small application named PuTTy, an SSH client. You can download putty here.
Once you have downloaded PuTTY, just start the program.
You are now logged into your server from Windows!
If the new volume has never been formatted, you need to format the volume using
mkfs before you can mount it.
For instance, the following command creates an
ext4 file system on the volume:
To mount the device manually as /mnt/data, run the following commands:
To mount the additional volume automatically, you can create a systemd script that will mount your volumes automatically during the boot of your cloud server.
If not yet done, create the directory into you want to mount your volume:
mkdir -p /mnt/data
As the volume is empty by default, you have to create a filesystem before you can use it. To format it with with an
ext4 filesystem, use the following command:
mkfs -t ext4 /dev/nbd1
To get the
UUID of your volume, run the command
blkid and take a note of the ID as you will need it in the next step.
Create or edit the file that corresponds to the path of your directory
nano /etc/systemd/system/mnt-data.mount and edit is as following: The file name of the script must correspond to the path where you mount the volume (
UUID with the ID of your volume.
Now reload systemd:
systemctl daemon-reload Launch the script to mount the volume:
systemctl start mnt-data.mount Finally enable the script to mount your volume automatically during boot:
systemctl enable mnt-data.mount
Your volume will automatically be mounted after a reboot. You can run the
df -h command, this command will list all your devices and where they are mounted: