The secret key is only shown once. Write it down and keep it safe. It cannot be recovered if you lose it.
Object Storage is a service based on the S3 protocol. It allows you to store any kind of objects (documents, images, videos, etc.)
We provide you with a comfortable and integrated UI in the console for convenience. But it is not easy to browse infinite storage from the web, so we came up with some engineering trade-offs: Bear in mind that some actions are limited in the console for Object Storage. It includes:
- batch deletion is limited to 1000 objects.
- empty files are not reported as empty folders.
We provide an S3-compatible API for programmatic access or for usage with any compatible software. Thus, we recommend using dedicated tools like s3cmd to manage large data sets.
You can create a token in the Credentials section of the management console. To connect to Object Storage, use the Access-Key and Secret-Key displayed during token creation.
|Type of consumption
|One Zone - IA
|Bucket websites feature
|75 GB free every month, then €0.01/GB
* Egress fees include external outgoing data transfer and inter-region data transfers (PAR<->AMS / PAR<->WAW / AMS <-> WAW). Intra-regional data transfers are free of charge.
Refer to our Cold Storage FAQ for more information on Scaleway Glacier billing.
Chia farming on Scaleway Object Storage that occurs without prior authorization will be billed at €0.08 per GB. Read our blogpost to learn more.
If you exceed 750 GB of Multi-AZ storage during the free trial period, you will only be billed for the excess data.
You can activate your free trial period from the Object Storage section of the Scaleway console. Once it is activated, you cannot deactivate it to resume it at a later time.
At the end of the 90-day trial period, you will be billed for regular Object Storage pricing.
To be eligible for this offer, you must have never used the Standard Multi-AZ class before November, 30th 2023, 23:59:59.
Bucket names must be unique and comply with the following:
- Must not contain uppercase characters or underscores.
- Must not be formatted as an IP address.
- Can contain lowercase letters, numbers, and hyphens.
- Can contain a set of the 63 alphabetic characters, a to z, and the 10 Arabic numerals, 0 to 9.
For buckets with a name containing a dot (.), users must use the canonical path. The subdomain form, for instance,
https://toto.tata.s3.nl-ams.scw.cloud will not work as the SSL certificate
*.s3.nl-ams.scw.cloud is not recursive.
In addition, when using buckets with Secure Sockets Layer (SSL), the SSL wildcard certificate only matches buckets that do not contain periods. Therefore, it is not recommended to use bucket names with multiple dots, as it will have an impact on accessing your bucket via HTTPS. To avoid this, it is recommended to use dashes in your bucket names.
Bucket names are unique in relation to our whole platform. This means if a bucket exists already in one region, the name cannot be reused in another.
“Bucket already exists” error message is triggered when the name you intended to use for your bucket is already reserved by another user (or yourself).
When deleting a bucket, its name becomes available again. Anybody can reuse it on a first-come, first-served principle.
The Object Storage product delivers content for your applications and users from a single point in the region of your choice. Our platform is designed to deliver very high performance, up to 100 Gbit/sec per bucket per region without performance loss.
If you want to deliver your content to several geographic locations with minimal latency, you can use Scaleway’s Edge Services directly from your bucket.
Yes, you can access your files via HTTPS by creating a public link from the Scaleway console. Follow the How to access my files via HTTPS documentation to do so.
Yes, this is allowed with tools like
s3cmd, but only cache-control or those prefixed by
Yes. All objects are private by default, but you can change their visibility to public anytime. Follow the How to manage object visibility documentation to do so.
Object Storage supports multipart upload. We recommend uploading by chunks, in a limit of 1000 chunks.
The following technical specifications apply to multipart uploads:
- 1 to 1000 parts per object
- 5 MB to 5 GB per part (except for the last one)
- Each object stores up to 5 TB
For more information, refer to the documentation.
If your bucket has been deleted from the Scaleway console, our teams may, as a last option, be able to retrieve its data the same day it is deleted (excluding weekends). Nevertheless, this measure applies on a case by case basis, and is not guaranteed. Contact Scaleway’s support team if you need to recover data from a deleted bucket within this time frame.
If your bucket has been deleted via the API, it is deleted instantly.
Yes. Scaleway Object Storage provides
read-after-write consistency for
DELETE requests of objects in buckets in all regions. This applies to writes of new objects as well as requests overwriting existing objects and to DELETEs.
Read-after-write consistency guarantees that changes are immediately visible (reading data) right after making those changes (writing data), meaning that a newly-created object will be visible immediately, without any delay.
Scaleway Object Storage stores data across multiple storage systems to achieve high availability. Any read (
LIST) request initiated after a successful PUT request will immediately return the data written by the
- You upload a new object into your bucket and request a listing of the objects in it: The new object will be visible in the list.
- You delete an existing object in your bucket and try to immediately read it. Object Storage will not return any data as the object has been deleted.
No. After you click to delete a bucket in the Scaleway console, the request is processed in our backend, and it is not dependent on your web browser. For more information on how to delete a bucket, refer to the documentation.
Yes. If you have deleted a bucket via the web console, you can create a new one with the same name after a delay of 24 hours.
Each Scaleway Project can use up to 250 TB of Object Storage resources. If you wish to increase your Object Storage quota, contact Scaleway’s support team.
Scaleway offers three storage classes:
Standard (Multi-AZ): your data is secured by distributing it across three different Availability Zones (AZ). In the event of a complete datacenter failure in an AZ, we are still able to rebuild your data and make it accessible. This is the system we call Multi-AZ (one datacenter per AZ, three AZs per region). The Standard class is available in all regions.
One Zone - Infrequent Access: your data is stored across three different racks in a single Availability Zone (AZ). This storage class is best suited for secondary backups and recreatable data. The One Zone - IA class is available in all regions.
When Multi-AZ is launched in a region, all existing objects are converted to the One Zone - IA class, which is equivalent to the old
New objects created after the Multi-AZ launch can have the
One Zone - IA, or the
Glacier class assigned.
No, any objects you upload into your buckets are added as Standard class objects by default, just as before. If you want to transfer your objects to One Zone - IA or Glacier you can do so manually or set up lifecycle rules.
Unfortunately, you cannot use the old Standard class. You must use the One Zone - IA class, which has the same behavior as the old Standard class.
No, because restoring an object can only be done from Glacier to Standard class. Transition lifecycle rules can only be configured in the “top-down” direction.
This means that you can transfer objects from Standard class to One Zone - IA and Glacier, but not from the last two to Standard. You can transfer objects from One Zone - IA to Glacier, but not restore objects from Glacier to One Zone - IA. The same applies when you make server-side copies.
No, the rules for using Glacier class remain the same and your data is still hosted in DC4. Refer to our Cold storage FAQ for more information on Scaleway Glacier.
Yes, you simply need to edit the storage class of your objects.
The cold storage “Glacier” class of Object Storage gets its name in opposition to “hot data”. Hot data is the type that is frequently accessed. Cold storage is accessed less frequently and does not require fast access like hot data.
Starting from November 6th 2023, restore operations from Glacier are billed at €0.009/GB. Restore operations started before this date will not be billed.
Scaleway Glacier is billed based on two parameters:
- Data storage: €0.00000348/GB/hour (approx. €0.002/GB/month)
- Restore to Standard class: €0.009/GB
Transferring objects from
One Zone - IA to
Glacier is free.
Scaleway Glacier is engineered for use cases that can be described as “deep archiving”. It is a durable Object Storage class designed for data archiving, for example legal documents or long-term backups that do not require immediate access.
We recommend you use Glacier to store average sized files (larger than 1 MB), as opposed to several small files.
Standard class is ideal for storing frequently accessed data and files, such as static assets, on-demand content such as streaming, Content Delivery Networks (CDN) or work related documents.
An object stored in Glacier class is listed but cannot be downloaded instantly. It needs to be restored to Standard class first. We recommend that you use Glacier to archive data that you may need only once or twice within a decade.
The time it takes to restore an object depends on the size of the object and on if multipart is configured. It can take anywhere from a few minutes to 24 hours for restore to start (for objects larger than 1 MB). Unfortunately, we are unable to provide estimates of how long data retrieval takes for each use case.
To facilitate the steps of restoration and ensure a fast restitution of your data, we recommend you use average-sized files (larger than 1 MB).
Find out how to restore an object from Glacier in our dedicated page.
Yes, you can select the storage class (
GLACIER) when uploading objects using the Scaleway console. It is also possible to do so using the API. For more information, refer to our dedicated documentation.
Our Paris underground databunker (DC4) provides an increased layer of security by being 25 meters deep below the surface in a bunker where the Glacier storage class cluster is available. This storage cluster is available from any bucket in Paris and Amsterdam and all objects can change the storage class to Glacier.
It is not yet possible to transfer files to Glacier in Warsaw, Poland.
The expiration & transition rules are implemented every day at midnight UTC, but the actual action might take between one minute and twenty-four hours* after implementation.
For example, a user wants to configure a lifecycle rule that moves an object after two days to Glacier:
- lifecycle rules are checked every day at midnight.
- the user uploaded a file on April 6th, at 2:00 pm UTC.
- the rule is triggered on April 8th, at 11:59 pm UTC.
- the application of the rule can take up to 24 hours ⇒ the object will be transferred to Glacier no later than 11:59 pm UTC on April 9th.
When a lifecycle rule is set for a very large amount of objects (several 100000s) simultaneously, the rule might take longer to be applied.
For increased security, we recommend you encrypt your data before sending it to Scaleway Glacier. Encryption should be done on the client-side to guarantee that there is no evidence of your private key stored on the cluster. Data can be encrypted using third-party solutions, like GPG. It is possible to automatize your backups and to encrypt them using a solution like Duplicity or Rclone using the crypt backend.
The GDPR requires that the life span of data be defined in two distinct cases:
- the deletion of data after a certain period of time
- the archiving of data that must legally be kept
Lifecycle management features meet both of these requirements by allowing you to set a timeframe beyond which your data is archived or deleted.
There is no maximum data size, Glacier accepts an unlimited number of objects up to 5 TB each. Large objects can be uploaded using multipart uploads.
Access to tape storage platforms requires a tape library to identify the cartridge on which the data is stored. Furthermore, retrieving data stored using tape storage requires reading several kilometers of tape.
Scaleway Glacier offers extra benefits compared to tape storage:
- Scaleway Glacier’s hard disk drive-based technology offers much better random data access time
- Scaleway Glacier enables parallel writing to multiple disks simultaneously, providing very high read and write speeds.
- redundancy is achieved by advanced parity mechanisms (6+3) on many media, whereas tape technology does not allow this and is limited to CRC.
- there is no risk of mechanical part failure (ex: robot) or wear and tear (tape drive).
Yes, a best practice is to create a transition lifecycle rule with an empty prefix. In this case, all files contained within the selected bucket will have their storage class altered automatically on the dates stipulated by you. However, due to S3 Protocol restrictions, a lifecycle rule cannot be created to modify the storage class from Glacier to Standard.