About Object Storage

What is Scaleway Object Storage?

Our scalable object storage service is based on the S3 protocol. S3 is the de facto object storage protocol created by Amazon for its object storage service. Object Storage officially supports a subset of S3. This cloud-based storage is designed to be highly available and durable.

Is Object Storage available in all regions?

Yes, Object Storage is available in our nl-ams (Amsterdam, The Netherlands) and fr-par(Paris, France) region.

How am I billed for Object Storage Service?

Object Storage pricing starts at €5 and includes:

  • 500GB of storage
  • 500GB of outbound transfer
  • €0.01/GB per additional GB stored
  • €0.02/GB per additional GB transferred

Network transit to Scaleway instances and Dedibox dedicated servers remain free within the region used. Traffic inter-region (AMS/PAR) is free up to 500GB/month. Additional traffic is billed €0,01/GB.

How is the Object Storage service calculated?

The Object Storage service is calculated as follows:

  • A monthly fixed price of €5.00 for the Starter Pack which comprises 500GB of transfer and 500GB of storage
  • An hourly rate of €0.00002 for any additional GB of consumed storage, up to 500 storage hours per month (€0.01/GB/month for data stored for a full month)
  • Additional storage is charged in slices of 1GB, which means that if you upload a 3 MB photo and you delete it after 30 minutes, you will be billed for 1GB of data consumption during 1hour

Data transfer towards the Internet is billed at €0.02/GB per GB transferred if you exceed the included transfer amount.

Is there a limitation in the number of HTTP requests?

You can make up to 250 requests per second to write and read from a bucket. However, if you need to increase that limit, you can always contact our support team.

How can I access the object storage?

The service is accessible through our console for simple operations.

We provide an S3-compatible API for programmatic access or for usage with any compatible software.

Why is the console limited?

We provide you with a comfortable and integrated UI in the console for convenience.

But it’s not easy to browse infinite storage from the web, so we came up with some engineering trade-offs:

  • batch deletion is limited to 1000 objects;
  • empty files are not reported as empty folders.

For all these reasons, we recommend using dedicated tools like s3cmd to manage large data sets.

What kind of data can I store?

You can store any kind of data, in any format (documents, images, videos, and much more).

How can I monitor my service?

You can monitor your Object Storage consumption directly from the Scaleway Console. Metrics such as storage and bucket usage help you estimate your consumption:

Object Storage Metrics

Which S3 operations are supported?

We currently support a subset of S3 operations. The exhaustive list is available on the S3 Object Storage API page.

How much data can I store?

There is no limit on the total volume of data of a bucket, or the number of objects it can contain. However, the bucket might slow down with a vast amount of objects.

How many buckets can I create?

You can create up to 100 buckets per user, and there is no storage usage limitation per bucket.

I get the message `Bucket already exists`, what is happening?

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.

The 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.

Note: We recommend using non-conspicuous names for your buckets.

Is there a limitation in the bucket name?

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 26 alphabetic characters, a to z, and the 10 Arabic numerals, 0 to 9.

Can I use dots or multiple dots in a bucket name?

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.

Can I transfer a bucket to another organization?

Bucket ownership is not transferable. A bucket is owned by the account which created it.

Can you recover a bucket deleted by mistake?

Unfortunately, recovering a deleted bucket is not be possible. Also, recovering the objects in a deleted bucket is not possible even if versioning is enabled on that bucket.

Can I use Object Storage as a CDN?

The object storage service was not designed to be used as a CDN: it is not fine-tuned for this kind of usage. We do not recommend it.

You can still use Object Storage as a backend for a CDN. All you need is to put a caching layer in front of it.

How can I access my files via HTTPS?

You can access your files via HTTPS by creating a public link from the control panel. Click on the file name and enable the public link by clicking on the corresponding button.

Can I use Object Storage as a file-system?

You can use Object Storage as a file-system with fuse based project such as s3fs.

Can I change HTTP headers during upload?

Yes, this is allowed with tools like s3cmd, but only cache-control or those prefixed by x-amz-meta.

How can I make an object public?

In order to make an object public, click on Visibility in the drop-down menu, set it to Public and save the setting.

If you upload a file by using the CLI, you can make it public by using the parameter: --acl public-read

Note: You can only make an object public or private (each one at a time). This action cannot be performed on a whole bucket, which is by default private. Allowing public access on a bucket only allows a public listing of the objects that are stored in the bucket.

How can I upload large objects?

Object Storage supports multipart upload. We recommend uploading by chunks, in a limit of 1000 chunks per upload and 5TB per object.

Can I create per-bucket or per-object access token?

What you’re asking for are federated tokens. We don’t support these for the moment as we want to keep tokens simple.

Which credentials do I have to use for the Object Storage?

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.

Note The Secret-Key is only shown once. Please take a note of it and keep it safe. It can’t be recovered if you lose it.

Is my data safe?

Object Storage is designed to provide 99.999% durability of objects over a given year. This durability level corresponds to an average annual expected loss of 0.001% of objects. In addition, the service is covered by SLAs to ensure data availability and durability.

As with any environment, the best practice is to have a backup and to put in place safeguards against malicious or accidental deletion.

What features can I expect in the future?

  • Infrequent Access
  • Cross Region Replication
  • Lambdas for DataManagement
  • Advanced ACL

A full list of features is available on the S3 API operations page.