NavigationContentFooter
Jump toSuggest an edit
Was this page helpful?

Instances

First stepsLink to this anchor

How can I create an image?Link to this anchor

You must create at least one snapshot before creating an image.

See the documentation on creating an image from scratch.

What is ImageHub?Link to this anchor

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

What is a Marketplace image?Link to this anchor

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

Scaleway Marketplace provides 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_name

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

BillingLink to this anchor

How am I billed for my compute Instances?Link to this anchor

Instances are billed on a pay-as-you-go basis, and their prices are made up of three parts:

  • Instance price,
  • Storage price (local or block),
  • Flexible IP price.

You can change the storage type and flexible IP after the Instance creation, which may affect the monthly billing.

What are the prices for Instances?Link to this anchor

Note
  • Prices indicated below do not include storage or IP.
  • *All regions refer to PAR1, PAR2, AMS1, AMS2, AMS3, WAW1, WAW2, and WAW3. Some ranges might not be available in some of these regions. Check the Instances availability guide to discover where each Instance type is available.
  • PAR3 prices are shown separately.

Learning Instances

RangePrice for all regions*Price for PAR3
STARDUST1-S€0.0046/hourNot available

Cost-Optimized Instances

RangePrice for all regions*Price for PAR3
COPARM1-2C-8G€0.0426/hourNot available
COPARM1-4C-16G€0.0857/hourNot available
COPARM1-8C-32G€0.1724/hourNot available
COPARM1-16C-64G€0.3454/hourNot available
COPARM1-32C-128G€0.6935/hourNot available
PRO2-XXS€0.055/hour€0.082/hour
PRO2-XS€0.11/hour€0.164/hour
PRO2-S€0.219/hour€0.329/hour
PRO2-M€0.438/hour€0.658/hour
PRO2-L€0.877/hour€1.315/hour
PLAY2-PICO€0.014/hourNot available
PLAY2-NANO€0.027/hourNot available
PLAY2-MICRO€0.054/hourNot available
GP1-XS€0.1016/hourNot available
GP1-S€0.2042/hourNot available
GP1-M€0.4064/hourNot available
GP1-L€0.7894/hourNot available
GP1-XL€1.6714/hourNot available
DEV1-S€0.0137/hourNot available
DEV1-M€0.0256/hourNot available
DEV1-L€0.0495/hourNot available
DEV1-XL€0.0731/hourNot available

Production-Optimized Instances

RangePrice for all regions*Price for PAR3
POP2-2C-8G€0.0735/hour€0.1103/hour
POP2-4C-16G€0.147/hour€0.2205/hour
POP2-8C-32G€0.29/hour€0.435/hour
POP2-16C-64G€0.59/hour€0.885/hour
POP2-32C-128G€1.18/hour€1.77/hour
POP2-64C-256G€2.35/hour€3.525/hour
ENT1-XXS€0.0735/hour€0.11/hour
ENT1-XS€0.147/hour€0.221/hour
ENT1-S€0.29/hour€0.44/hour
ENT1-M€0.59/hour€0.88/hour
ENT1-L€1.18/hour€1.76/hour
ENT1-XL€2.35/hour€3.53/hour
ENT1-2XL€3.53/hour€5.29/hour

Production-Optimized Instances with Windows Server operating system

RangePrice for all regions*Price for PAR3
POP2-2C-8G-WIN€0.1823/hourNot available
POP2-4C-16G-WIN€0.3637/hourNot available
POP2-8C-32G-WIN€0.7233/hourNot available
POP2-16C-64G-WIN€1.4567/hourNot available
POP2-32C-128-WIN€2.9133/hourNot available

Workload-Optimized Instances

RangePrice for all regions*Price for PAR3
POP2-HM-2C-16G€0.103/hour€0.1545/hour
POP2-HM-4C-32G€0.206/hour€0.309/hour
POP2-HM-8C-64G€0.412/hour€0.618/hour
POP2-HM-16C-128G€0.824/hour€1.236/hour
POP2-HM-32C-256G€1.648/hour€2.472/hour
POP2-HM-64C-512G€3.296/hour€4.944/hour
POP2-HC-2C-4G€0.0532/hour€0.0798/hour
POP2-HC-4C-8G€0.1064/hour€0.1596/hour
POP2-HC-8C-16G€0.2128/hour€0.3192/hour
POP2-HC-16C-32G€0.4256/hour€0.6384/hour
POP2-HC-32C-64G€0.8512/hour€1.2768/hour
POP2-HC-64C-128G€1.7024/hour€2.5536/hour
POP2-HN-3€0.2554/hour€0.3831/hour
POP2-HC-5€0.4524/hour€0.6786/hour
POP2-HC-10€0.7264/hour€1.0896/hour

GPU Instances

RangeAvailable inPrice
H100-1-80GPAR2, WAW2€2.52/hour¹
H100-2-80GPAR2, WAW2€5.04/hour¹
L40S-1-48GPAR2€1.40/hour¹
L40S-2-48GPAR2€2.80/hour¹
L40S-4-48GPAR2€5.60/hour¹
L40S-8-48GPAR2€11.20/hour¹
L4-1-24GPAR2, WAW2€0.75/hour¹
L4-2-24GPAR2, WAW2€1.50/hour¹
L4-4-24GPAR2, WAW2€3.00/hour¹
L4-8-24GPAR2, WAW2€6.00/hour¹
RENDER-SPAR1, PAR2€1.2426/hour
GPU-3070-SPAR2€0.98/hour

¹= Billed per minute.

Note

PLAY2-PICO and DEV1-S Instances are not available for Kubernetes Kapsule due to RAM constraints.

What are the storage prices for Instances?Link to this anchor

ProductAll regions*PAR3
Local Storage€0.000044 GB/hourNot available
Local snapshot€0.000044 GB/hourNot available
Block Storage€0.000118 GB/hour€0.000177 GB/hour
Block snapshot€0.000044 GB/hour€0.000066 GB/hour

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

How much does a flexible IP cost?Link to this anchor

Each Instance’s flexible IPv4 costs €0.004/hour, excl. VAT.

Requirements and configurationsLink to this anchor

What is the minimum volume size my Instance can have?Link to this anchor

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

What are the benefits of Dedicated Resources?Link to this anchor

Dedicated Resources give you a more stable experience for compute-demanding workloads, offering benefits such as:

  • No “noisy neighbors”,
  • No “burst effects”,
  • Optimization for demanding and specific needs.

Which options are available to power off my Instance?Link to this anchor

You can choose between four options when powering off your Instance:

  • Hard reboot: Your Instance performs an electrical reboot and its data is kept on the Local Storage. We recommend always rebooting your Instance from the OS to avoid data corruption.
  • Power off: All local volume data is transferred to a volume store, and your physical node is released back to the pool of available machines. The process duration depends on the amount of data archived.
  • Terminate: Your Instance and its volumes are permanently deleted, but the attached flexible IP is preserved.
  • Standby: Your Instance is stopped, but its data remains in the Local Storage. The Instance is still allocated to your account and can be restarted anytime.
Important

The standby mode is charged as a running Instance. To avoid being billed for an unused Instance, power it off and ensure no IPs or allocated storage are left in use.

Why do I have to specify the CPU architecture when creating an image from a volume?Link to this anchor

ARM and x86-based Instances use a different instruction set, which requires specifying the architecture of the platform when creating an image from a volume.

An ARM CPU uses a Reduced Instruction Set Computing RISC architecture, while an x86 CPU uses a Complex Instruction Set Computing CISC architecture.

Can I reach my Instance using a DNS hostname instead of its IP address?Link to this anchor

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 automatically updated when the Instance moves to another hypervisor, also changing its IPv6 and private IPv4. You can either use these hostnames directly or configure a CNAME record linking to it.

Can I migrate from a first-generation DEV1 Instance to a PLAY2 Instance?Link to this anchor

Yes. Refer to the changing the commercial type of an Instance documentation.

Can I migrate from my first-generation GP1 Instance to a PRO2 Instance?Link to this anchor

Yes. Refer to the changing the commercial type of an Instance documentation.

Can I boot my Instance from a Block Storage volume?Link to this anchor

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 creating an Instance and choosing it as the boot volume.

Offers and availabilityLink to this anchor

Which Linux distributions are available?Link to this anchor

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

You are free to bootstrap your own distribution.

Which Linux distributions are available for Enterprise Instances?Link to this anchor

We provide a wide range of different Linux distributions and InstantApps for Instances. Refer to Scaleway Instance OS images and InstantApps for a complete list of all available OSes and InstantApps.

What are the differences between ENT1 and POP2 Instances?Link to this anchor

Both ENT1 and POP2 Instance types share the following features:

  • Identical hardware specifications
  • Dedicated vCPU allocation
  • Same pricing structure
  • Accelerated booting process

POP2 Instances provide CPU- and memory-optimized variants tailored to suit your workload requirements more effectively. The primary distinction between ENT1 and POP2 lies in AMD Secure Encrypted Virtualization (SEV), which is disabled for POP2 Instances. By choosing POP2 Instances, you gain access to the latest features, such as the potential for live migration of Instances in the future, ensuring that your infrastructure remains aligned with evolving demands and technological advancements. We recommend choosing POP2 Instances for most general workloads unless your specific workload requires features unique to ENT1 Instances.

Where are my Instances located?Link to this anchor

Scaleway offers different Instance ranges in all regions: Paris (France), Amsterdam (Netherlands), and Warsaw (Poland).

Check the Instances availability guide to discover where each Instance type is available.

What makes FR-PAR-2 a sustainable Region?Link to this anchor

FR-PAR-2 is our sustainable and environmentally efficient Availability Zone (AZ) in Paris.

This Region is entirely powered by renewable (hydraulic) energy. It also has an energetic footprint 30-40% lower than traditional data centers, thanks to the fact that it does not require air conditioning. Learn more about our environmental commitment.

NetworkLink to this anchor

Which Instances support IP Mobility?Link to this anchor

All ranges are compatible except for Instances using the “bootscript” feature, which has reached its end of life (EOL).

Can I enable “Routed IP” on my bootscript Instance?Link to this anchor

Instances using a bootscript are not compatible with Routed IPs. As the bootscript feature has reached its end of life (EOL), refer to this tutorial for migration instructions.

Can I revert the migration to “Routed IP”?Link to this anchor

No, the migration is permanent.

Will my Instance retain its public IPv4 after migration?Link to this anchor

Yes, your existing flexible public IPv4 will be converted to a routed one and will remain unchanged after migration.

Will my Instance retain its public IPv6 after migration?Link to this anchor

No, you will receive a new IPv6 after migration.

Will my Instance retain its private IPv4 after migration?Link to this anchor

No, the Scaleway private IP will be removed after the migration.

Will my Instance retain its VPC private IPv4 after migration?Link to this anchor

Yes, your VPC configuration will remain intact after migrating to a routed public IPv4.

Can a resource with a routed IP communicate with a resource with a NAT IP?Link to this anchor

Yes, they can communicate with each other using their public IPs.

Are there any limitations on IP autoconfiguration with the routed IP feature?Link to this anchor

Currently, additional routed IPv6 addresses do not autoconfigure on CentOS 7, 8, 9, Alma 8, 9, Rocky 8, 9 after migration. Additional routed IPv4 and IPv6 addresses are not autoconfigured post-migration on Ubuntu 20.04 Focal. However, the primary IPv6 continues to be configured via SLAAC. These limitations are currently being addressed. For detailed migration steps, refer to our migration guide. If you encounter connectivity issues with Ubuntu Focal Instances having multiple public IPs, consult our troubleshooting guide.

Was this page helpful?
API DocsScaleway consoleDedibox consoleScaleway LearningScaleway.comPricingBlogCareers
© 2023-2025 – Scaleway