I get 400 Bad Request errors when uploading objects

Before you start

To complete the actions presented below, you must have:

• Owner status or IAM permissions allowing you to perform actions in the intended Organization

Problem

When uploading an object, I get an error similar to the following:

HTTP 400 Bad Request: InvalidArgument.

Cause

Scaleway Object Storage previously accepted requests containing the x-amz-server-side-encryption: AES256 header without enforcing encryption, returning a successful HTTP 200 OK response.

Requests with this header are now explicitly rejected with an HTTP 400 Bad Request: InvalidArgument error, as AES256 server-side encryption is not currently supported by Scaleway Object Storage.

Solution

Remove the x-amz-server-side-encryption: AES256 header from your requests.

Going further

Refer to the dedicated documentation for comprehensive information on how to encrypt objects using SSE-C.

• If you did not manage to identify the error and solve it by yourself, open a support ticket, and provide as many details as possible, along with the necessary information below:
  • Object Storage Endpoint (e.g. s3.fr-par.scw.cloud)
  • Bucket name
  • Object name (if the request concerns an object)
  • Request type (PUT, GET, etc.)
  • HTTP status code
  • Date and time (timestamp)
  • User-agent (SDK, client, console, etc.)
  • Transaction ID (if possible)
  • Log / trace of the error (if possible)