Instances

Compute Instances are billed on a pay-as-you-go basis. The price of your Instance is made up of three parts:

• the price of the Instance itself
• the price of the storage (local or block). You can adjust storage quantity when you create the Instance
• the price of the flexible IP - you can change or delete associated flexible IP afterward

Instance Pricing as of December 1st 2022

*All regions include PAR1, PAR2, AMS1, AMS2, AMS3, WAW1, WAW2and WAW3. PAR3 prices are shown separately.

Storage Pricing

*All regions include PAR1, PAR2, AMS1, AMS2, AMS3, WAW1, WAW2, and WAW3. PAR3` prices are shown separately.

IP Pricing

Each flexible IPv4 for an Instance costs 0,004€/hour excl. VAT.

We provide a wide range of different Linux distributions and InstantApps for Instances.

You are free to bootstrap your own distribution.

You must create at least one snapshot before you can create an image.

See the documentation on creating an image from scratch.

Scaleway’s ImageHub is a catalog of system images that allow you to deploy, manage and scale your favorite applications in seconds, from image templates.

When you request to power off your Instance, four options are available:

• Hard Reboot
• Power off
• Terminate
• Standby

When you select the Hard Reboot option, your Instance performs an electrical reboot. Your data remains on the local storage. Whenever possible, you should reboot your Instance from the OS to avoid data corruption.

When you select the Power off option, all data on the local volume of your Instance is transferred to a volume store, and your physical node is released back to the pool of available machines. Depending on the amount of data to be archived, the process can take time.

When you select the Terminate option, your Instance and volumes are deleted. You will not be able to recover them. The flexible IP attached to your Instance will not be deleted.

When you select the Standby option, your Instance is stopped, but all your data remains on the local storage. Your Instance is still allocated to your account, and you can restart it anytime, without delay.

Yes, each Instance has two DNS hostnames associated with it:

• A public DNS hostname: <instance-uuid>.pub.instances.scw.cloud
• A private DNS hostname: <instance-uuid>.priv.instances.scw.cloud

Both are being updated automatically when the Instance moves to another hypervisor (and thus its IPv6, and the private IPv4, changes). You can either use these hostnames directly or configure a CNAME record linking to it.

Why do I have to specify the CPU architecture when I create an image from a volume?

ARM and x86-based Instances (Development Instances and General Purpose Instances) use a different instruction set and this requires to specify the architecture of the platform when creating an image from a volume.

An ARM CPU is using a Reduced Instruction Set Computing (RISC) architecture while an x86 CPU is using a Complex Instruction Set Computing (CISC) architecture. Hence, ARM architecture uses a simplified instruction set which results in power efficiency, making it ideal for mobile devices. Therefore ARM64 Instances are ideal to develop and test mobile applications.

A Marketplace is an online store that offers applications and services either built on or integrated with Scaleway’s offerings.

Scaleway Marketplace provides customers with information related to Instance images, through variants named “local-images”. This information can include the Instance zone and identification, along with constraints regarding the applicable Instance types. When you want to create an Instance using an image in the Instance API, you need to specify the local-image UUID matching the zone and Instance type constraints you fetch from the marketplace API.

Use the Marketplace API to find the UUID of the image you want to use. Alternatively, you can use this CLI command:

scw marketplace image get label=image_nameCopy

Replace the image_name with the name of your image or distribution, e.g.: ubuntu_focal or debian_stretch.

Yes. When creating an Instance, you can select Block Storage as a system volume type. This allows you to reboot Instances from the block volume on which your OS is stored.

You can also add a Block volume after you have created your Instance and choose it as the boot volume.

Your system volume must be at least 10 GB (125 GB for a GPU OS).

When creating an Instance, you must select a local or block to be the system volume. Your system volume is the volume on which your Instance will boot, so it is necessary you have a minimum size available to store the OS.