Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions pages/file-storage/faq.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,10 @@ category: storage
productIcon: FileStorageProductIcon
---

<Message type="note">
File Storage is currently in Public Beta.
</Message>

## Overview

### What is Scaleway File Storage?
Expand Down
4 changes: 4 additions & 0 deletions pages/file-storage/how-to/attach-file-system.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,10 @@ dates:
posted: 2025-07-23
---

<Message type="note">
File Storage is currently in Public Beta.
</Message>

This page explains how to attach a file system to one or several Instances. File systems can only be attached to Instances within the same [region](/file-storage/concepts/#region).

import Requirements from '@macros/iam/requirements.mdx'
Expand Down
8 changes: 6 additions & 2 deletions pages/file-storage/how-to/create-file-system.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -11,13 +11,17 @@ dates:
---
import Requirements from '@macros/iam/requirements.mdx'

<Message type="note">
File Storage is currently in Public Beta.
</Message>

This page explains how to create a file system using the Scaleway console.

<Requirements />

- A Scaleway account logged into the [console](https://console.scaleway.com)
- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization

This page explains how to create a file system using the Scaleway console.

## How to create a file system

1. Click **File Storage** in the **Storage** section of the side menu. The [File Storage dashboard](https://console.scaleway.com/file-storage/) displays.
Expand Down
4 changes: 3 additions & 1 deletion pages/file-storage/how-to/detach-file-system.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,9 @@ dates:
posted: 2025-07-23
---

## How to detach a file system from an instance
<Message type="note">
File Storage is currently in Public Beta.
</Message>

1. Click **File Storage** in the **Storage** section of the side menu. A list of your file systems displays.

Expand Down
4 changes: 4 additions & 0 deletions pages/file-storage/how-to/manage-delete-file-system.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,10 @@ dates:
posted: 2025-07-23
---

<Message type="note">
File Storage is currently in Public Beta.
</Message>

import Requirements from '@macros/iam/requirements.mdx'

This page explains how to manage and delete a file system.
Expand Down
4 changes: 4 additions & 0 deletions pages/file-storage/how-to/mount-file-system.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,10 @@ dates:
posted: 2025-07-23
---

<Message type="note">
File Storage is currently in Public Beta.
</Message>

import Requirements from '@macros/iam/requirements.mdx'

This page explains how to mount a file system to one or several Scaleway Instances.
Expand Down
4 changes: 4 additions & 0 deletions pages/file-storage/how-to/resize-file-system.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,10 @@ dates:
posted: 2025-07-23
---

<Message type="note">
File Storage is currently in Public Beta.
</Message>

This page explains how to resize a file system using the Scaleway console.

import Requirements from '@macros/iam/requirements.mdx'
Expand Down
4 changes: 4 additions & 0 deletions pages/file-storage/how-to/unmount-file-system.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,10 @@ dates:
posted: 2025-07-23
---

<Message type="note">
File Storage is currently in Public Beta.
</Message>

import Requirements from '@macros/iam/requirements.mdx'

This page explains how to unmount a file system from one or several Scaleway Instances.
Expand Down
5 changes: 5 additions & 0 deletions pages/file-storage/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,11 @@ description: Explore Scaleway File Storage with quickstart guides, how-tos, and
label="File Storage Quickstart"
/>


<Message type="note">
File Storage is currently in Public Beta.
</Message>

## Getting Started

<Grid>
Expand Down
4 changes: 4 additions & 0 deletions pages/file-storage/quickstart.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,10 @@ categories:
---
import Requirements from '@macros/iam/requirements.mdx'

<Message type="note">
File Storage is currently in Public Beta.
</Message>

Scaleway File Storage allows you to create file systems to easily share files across multiple Instances within the same region. File systems are network-attached storage structures that can be accessed by Scaleway Instances to easily share files within your cloud infrastructure.

Each file system can be attached to several Instances, and each Instance can have several file systems attached to it.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,10 @@ dates:
posted: 2026-01-27
---

<Message type="note">
File Storage is currently in Public Beta.
</Message>

Scaleway File Storage performance (IOPS and throughput) scales linearly with your provisioned capacity. To avoid bottlenecks, you must pair your file system with Instances that matches its performance profile and supports the required number of mount points.

Refer to the [dedicated documentation](/file-storage/reference-content/performance-scaling/) for more information on performance scaling.
Expand All @@ -20,7 +24,7 @@ To optimize storage costs and avoid throttling your file system at the Instance
Ideal for lightweight web servers, small-scale production environments, and low-traffic repositories.

- **Provisioning range:** 25 GB to 100 GB
- **Recommended instances:** POP2-2C (or any 2 vCPU General Purpose Instance), BASIC3-X, BASIC2
- **Recommended instances:** POP2-2C (or any 2 vCPU General Purpose Instance)

<Message type="tip">
Ideal for one or two mount points to maintain a stable network baseline.
Expand Down Expand Up @@ -52,79 +56,54 @@ Above 1 TB, File Storage delivers significant throughput. Only high-core count o

To ensure optimum performance, the number of file systems you can attach to an Instance is limited based on the Instance's configuration.

Use the following [Scaleway CLI](/scaleway-cli/quickstart/) command to find the maximum number of file systems you can attach to a Scaleway Instance. Do not forget to replace the value of the `zone` parameter with the desired Availability Zone:
Use the following [Scaleway CLI](/scaleway-cli/quickstart/) command to find the maximum number of file systems you can attach to a Scaleway Instance. Make sure to replace the value of the `zone` parameter with the desired Availability Zone:

```bash
scw instance server-type list zone=fr-par-2
```

<Message type="note">
The availability of Instances types varies between Availability Zones, some offers may be missing in the table below.
Currently, only Linux-based POP2 CPU Instances, L4, L40S, and H100 GPU Instances are fully qualified for File Storage. Other offers will be added during the Public Beta phase.
</Message>

| NAME | CPU | GPU | RAM | ARCH | MAX FILE SYSTEMS |
|---------------------|-----|-----|---------|--------|------------------|
| BASIC3-X2C-4G | 2 | 0 | 4 GiB | x86_64 | 1 |
| BASIC3-X2C-8G | 2 | 0 | 8 GiB | x86_64 | 1 |
| BASIC3-X4C-8G | 4 | 0 | 8 GiB | x86_64 | 1 |
| COMPUTE3-X2C-4G | 2 | 0 | 4 GiB | x86_64 | 1 |
| MEMORY3-X2C-16G | 2 | 0 | 16 GiB | x86_64 | 1 |
| POP2-HC-2C-4G | 2 | 0 | 4 GiB | x86_64 | 1 |
| POP2-2C-8G | 2 | 0 | 8 GiB | x86_64 | 1 |
| POP2-HC-4C-8G | 4 | 0 | 8 GiB | x86_64 | 1 |
| POP2-4C-16G | 4 | 0 | 16 GiB | x86_64 | 1 |
| POP2-HM-4C-32G | 4 | 0 | 32 GiB | x86_64 | 1 |
| POP2-HN-3 | 2 | 0 | 4 GiB | x86_64 | 1 |
| POP2-HN-5 | 4 | 0 | 8 GiB | x86_64 | 1 |
| POP2-HN-10 | 4 | 0 | 8 GiB | x86_64 | 1 |
| STANDARD2-A2C-8G | 2 | 0 | 8 GiB | arm64 | 1 |
| STANDARD3-X2C-8G | 2 | 0 | 8 GiB | x86_64 | 1 |
| BASIC3-X4C-16G | 4 | 0 | 16 GiB | x86_64 | 2 |
| BASIC3-X8C-16G | 8 | 0 | 16 GiB | x86_64 | 2 |
| COMPUTE3-X4C-8G | 4 | 0 | 8 GiB | x86_64 | 2 |
| L4-1-24G | 8 | 1 | 48 GiB | x86_64 | 2 |
| MEMORY3-X4C-32G | 4 | 0 | 32 GiB | x86_64 | 2 |
| POP2-HM-2C-16G | 2 | 0 | 16 GiB | x86_64 | 2 |
| POP2-HC-8C-16G | 8 | 0 | 16 GiB | x86_64 | 2 |
| POP2-8C-32G | 8 | 0 | 32 GiB | x86_64 | 2 |
| POP2-HM-8C-64G | 8 | 0 | 64 GiB | x86_64 | 2 |
| STANDARD2-A4C-16G | 4 | 0 | 16 GiB | arm64 | 2 |
| STANDARD3-X4C-16G | 4 | 0 | 16 GiB | x86_64 | 2 |
| BASIC3-X8C-32G | 8 | 0 | 32 GiB | x86_64 | 4 |
| BASIC3-X16C-32G | 16 | 0 | 32 GiB | x86_64 | 4 |
| COMPUTE3-X8C-16G | 8 | 0 | 16 GiB | x86_64 | 4 |
| COMPUTE3-X16C-32G | 16 | 0 | 32 GiB | x86_64 | 4 |
| L4-2-24G | 16 | 2 | 96 GiB | x86_64 | 4 |
| MEMORY3-X8C-64G | 8 | 0 | 64 GiB | x86_64 | 4 |
| MEMORY3-X16C-128G | 16 | 0 | 128 GiB | x86_64 | 4 |
| POP2-HC-16C-32G | 16 | 0 | 32 GiB | x86_64 | 4 |
| POP2-16C-64G | 16 | 0 | 64 GiB | x86_64 | 4 |
| POP2-HM-16C-128G | 16 | 0 | 128 GiB | x86_64 | 4 |
| STANDARD2-A8C-32G | 8 | 0 | 32 GiB | arm64 | 4 |
| STANDARD2-A16C-64G | 16 | 0 | 64 GiB | arm64 | 4 |
| STANDARD3-X8C-32G | 8 | 0 | 32 GiB | x86_64 | 4 |
| STANDARD3-X16C-64G | 16 | 0 | 64 GiB | x86_64 | 4 |
| BASIC3-X16C-64G | 16 | 0 | 64 GiB | x86_64 | 8 |
| COMPUTE3-X32C-64G | 32 | 0 | 64 GiB | x86_64 | 8 |
| COMPUTE3-X48C-96G | 48 | 0 | 96 GiB | x86_64 | 8 |
| COMPUTE3-X64C-128G | 64 | 0 | 128 GiB | x86_64 | 8 |
| COMPUTE3-X96C-192G | 96 | 0 | 192 GiB | x86_64 | 8 |
| L4-4-24G | 32 | 4 | 192 GiB | x86_64 | 8 |
| MEMORY3-X32C-256G | 32 | 0 | 256 GiB | x86_64 | 8 |
| MEMORY3-X48C-384G | 48 | 0 | 384 GiB | x86_64 | 8 |
| POP2-HC-32C-64G | 32 | 0 | 64 GiB | x86_64 | 8 |
| POP2-32C-128G | 32 | 0 | 128 GiB | x86_64 | 8 |
| POP2-HM-32C-256G | 32 | 0 | 256 GiB | x86_64 | 8 |
| STANDARD2-A32C-128G | 32 | 0 | 128 GiB | arm64 | 8 |
| STANDARD2-A48C-192G | 48 | 0 | 192 GiB | arm64 | 8 |
| STANDARD2-A64C-256G | 64 | 0 | 256 GiB | arm64 | 8 |
| STANDARD3-X32C-128G | 32 | 0 | 128 GiB | x86_64 | 8 |
| STANDARD3-X48C-192G | 48 | 0 | 192 GiB | x86_64 | 8 |
| STANDARD3-X64C-256G | 64 | 0 | 256 GiB | x86_64 | 8 |
| POP2-HC-48C-96G | 48 | 0 | 96 GiB | x86_64 | 12 |
| POP2-48C-192G | 48 | 0 | 192 GiB | x86_64 | 12 |
| POP2-HM-48C-384G | 48 | 0 | 384 GiB | x86_64 | 12 |
| L4-8-24G | 64 | 8 | 384 GiB | x86_64 | 16 |
| POP2-HC-64C-128G | 64 | 0 | 128 GiB | x86_64 | 16 |
| POP2-64C-256G | 64 | 0 | 256 GiB | x86_64 | 16 |
| POP2-HM-64C-512G | 64 | 0 | 512 GiB | x86_64 | 16 |
| NAME | CPU | GPU | RAM | ARCH | MAX FILE SYSTEMS |
|------------------|-----|-----|---------|--------|------------------|
| POP2-HC-2C-4G | 2 | 0 | 4 GiB | x86_64 | 1 |
| POP2-2C-8G | 2 | 0 | 8 GiB | x86_64 | 1 |
| POP2-HC-4C-8G | 4 | 0 | 8 GiB | x86_64 | 1 |
| POP2-4C-16G | 4 | 0 | 16 GiB | x86_64 | 1 |
| POP2-HM-4C-32G | 4 | 0 | 32 GiB | x86_64 | 1 |
| POP2-HN-3 | 2 | 0 | 4 GiB | x86_64 | 1 |
| POP2-HN-5 | 4 | 0 | 8 GiB | x86_64 | 1 |
| POP2-HN-10 | 4 | 0 | 8 GiB | x86_64 | 1 |
| L4-1-24G | 8 | 1 | 48 GiB | x86_64 | 2 |
| POP2-HM-2C-16G | 2 | 0 | 16 GiB | x86_64 | 2 |
| POP2-HC-8C-16G | 8 | 0 | 16 GiB | x86_64 | 2 |
| POP2-8C-32G | 8 | 0 | 32 GiB | x86_64 | 2 |
| POP2-HM-8C-64G | 8 | 0 | 64 GiB | x86_64 | 2 |
| H100-1-80G | 24 | 1 | 240 GiB | x86_64 | 2 |
| H100-1-M | 24 | 1 | 240 GiB | x86_64 | 2 |
| L40S-1-48G | 8 | 1 | 96 GiB | x86_64 | 2 |
| L4-2-24G | 16 | 2 | 96 GiB | x86_64 | 4 |
| POP2-HC-16C-32G | 16 | 0 | 32 GiB | x86_64 | 4 |
| POP2-16C-64G | 16 | 0 | 64 GiB | x86_64 | 4 |
| POP2-HM-16C-128G | 16 | 0 | 128 GiB | x86_64 | 4 |
| H100-2-80G | 48 | 2 | 480 GiB | x86_64 | 4 |
| H100-SXM-2-80G | 32 | 2 | 240 GiB | x86_64 | 4 |
| H100-2-M | 48 | 2 | 480 GiB | x86_64 | 4 |
| L40S-2-48G | 16 | 2 | 192 GiB | x86_64 | 4 |
| L4-4-24G | 32 | 4 | 192 GiB | x86_64 | 8 |
| POP2-HC-32C-64G | 32 | 0 | 64 GiB | x86_64 | 8 |
| POP2-32C-128G | 32 | 0 | 128 GiB | x86_64 | 8 |
| POP2-HM-32C-256G | 32 | 0 | 256 GiB | x86_64 | 8 |
| H100-SXM-4-80G | 64 | 4 | 480 GiB | x86_64 | 8 |
| L40S-4-48G | 32 | 4 | 384 GiB | x86_64 | 8 |
| POP2-HC-48C-96G | 48 | 0 | 96 GiB | x86_64 | 12 |
| POP2-48C-192G | 48 | 0 | 192 GiB | x86_64 | 12 |
| POP2-HM-48C-384G | 48 | 0 | 384 GiB | x86_64 | 12 |
| L4-8-24G | 64 | 8 | 384 GiB | x86_64 | 16 |
| POP2-HC-64C-128G | 64 | 0 | 128 GiB | x86_64 | 16 |
| POP2-64C-256G | 64 | 0 | 256 GiB | x86_64 | 16 |
| POP2-HM-64C-512G | 64 | 0 | 512 GiB | x86_64 | 16 |
| H100-SXM-8-80G | 128 | 8 | 960 GiB | x86_64 | 16 |
| L40S-8-48G | 64 | 8 | 768 GiB | x86_64 | 16 |
Original file line number Diff line number Diff line change
Expand Up @@ -7,10 +7,16 @@ dates:
posted: 2026-04-08
---

<Message type="note">
File Storage is currently in Public Beta.
</Message>

## Performance scaling

Scaleway File Storage architecture follows a "pay-as-you-grow" model where IOPS and throughput scale linearly as you provision more capacity for a file system. This guarantees consistent and predictable performance that you can adjust according to your needs.

The performance of a file system may vary due to factors such as the number of attached Instances, the attached Instance type, and the workload. Refer to the [dedicated guidelines](/file-storage/reference-content/file-system-instance-selection/) for more information.

Both IOPS and throughput reach their maximum values at 2 TB of provisioned capacity. Provisioning beyond 2 TB increases available storage, but does not further increase performance.

### IOPS
Expand Down
Loading