From 3691b5ccb081a51c46844cc634d4026dc57953a9 Mon Sep 17 00:00:00 2001 From: SamyOubouaziz Date: Thu, 3 Jul 2025 17:29:58 +0200 Subject: [PATCH 01/16] feat(obj): add new troubleshooting pages MTA-5488 --- .../deleted-objects-still-billed.mdx | 40 +++++++++++++++++++ .../object-storage/object-deletion-issues.mdx | 40 +++++++++++++++++++ .../object-versioning-issues.mdx | 40 +++++++++++++++++++ pages/object-storage/presigned-url-errors.mdx | 40 +++++++++++++++++++ .../lifecycle-rules-issues.mdx | 40 +++++++++++++++++++ 5 files changed, 200 insertions(+) create mode 100644 pages/object-storage/deleted-objects-still-billed.mdx create mode 100644 pages/object-storage/object-deletion-issues.mdx create mode 100644 pages/object-storage/object-versioning-issues.mdx create mode 100644 pages/object-storage/presigned-url-errors.mdx create mode 100644 pages/object-storage/troubleshooting/lifecycle-rules-issues.mdx diff --git a/pages/object-storage/deleted-objects-still-billed.mdx b/pages/object-storage/deleted-objects-still-billed.mdx new file mode 100644 index 0000000000..593d2181f8 --- /dev/null +++ b/pages/object-storage/deleted-objects-still-billed.mdx @@ -0,0 +1,40 @@ +--- +meta: + title: &title + description: &description +content: + h1: *title + paragraph: *description +tags: +categories: + - storage + - object-storage +dates: + validation: 2025-07-03 + posted: 2025-07-03 +--- + + + +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization + +## Problem + +## Cause + +## Possible solutions + +## Going further + +- Refer to the [bucket policies overview](/object-storage/api-cli/bucket-policy/) for more information on the different elements of a bucket policy. + +- If you did not manage to identify the error and solve it by yourself, [open a support ticket](/account/how-to/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) diff --git a/pages/object-storage/object-deletion-issues.mdx b/pages/object-storage/object-deletion-issues.mdx new file mode 100644 index 0000000000..593d2181f8 --- /dev/null +++ b/pages/object-storage/object-deletion-issues.mdx @@ -0,0 +1,40 @@ +--- +meta: + title: &title + description: &description +content: + h1: *title + paragraph: *description +tags: +categories: + - storage + - object-storage +dates: + validation: 2025-07-03 + posted: 2025-07-03 +--- + + + +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization + +## Problem + +## Cause + +## Possible solutions + +## Going further + +- Refer to the [bucket policies overview](/object-storage/api-cli/bucket-policy/) for more information on the different elements of a bucket policy. + +- If you did not manage to identify the error and solve it by yourself, [open a support ticket](/account/how-to/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) diff --git a/pages/object-storage/object-versioning-issues.mdx b/pages/object-storage/object-versioning-issues.mdx new file mode 100644 index 0000000000..593d2181f8 --- /dev/null +++ b/pages/object-storage/object-versioning-issues.mdx @@ -0,0 +1,40 @@ +--- +meta: + title: &title + description: &description +content: + h1: *title + paragraph: *description +tags: +categories: + - storage + - object-storage +dates: + validation: 2025-07-03 + posted: 2025-07-03 +--- + + + +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization + +## Problem + +## Cause + +## Possible solutions + +## Going further + +- Refer to the [bucket policies overview](/object-storage/api-cli/bucket-policy/) for more information on the different elements of a bucket policy. + +- If you did not manage to identify the error and solve it by yourself, [open a support ticket](/account/how-to/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) diff --git a/pages/object-storage/presigned-url-errors.mdx b/pages/object-storage/presigned-url-errors.mdx new file mode 100644 index 0000000000..593d2181f8 --- /dev/null +++ b/pages/object-storage/presigned-url-errors.mdx @@ -0,0 +1,40 @@ +--- +meta: + title: &title + description: &description +content: + h1: *title + paragraph: *description +tags: +categories: + - storage + - object-storage +dates: + validation: 2025-07-03 + posted: 2025-07-03 +--- + + + +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization + +## Problem + +## Cause + +## Possible solutions + +## Going further + +- Refer to the [bucket policies overview](/object-storage/api-cli/bucket-policy/) for more information on the different elements of a bucket policy. + +- If you did not manage to identify the error and solve it by yourself, [open a support ticket](/account/how-to/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) diff --git a/pages/object-storage/troubleshooting/lifecycle-rules-issues.mdx b/pages/object-storage/troubleshooting/lifecycle-rules-issues.mdx new file mode 100644 index 0000000000..b96baae72d --- /dev/null +++ b/pages/object-storage/troubleshooting/lifecycle-rules-issues.mdx @@ -0,0 +1,40 @@ +--- +meta: + title: &title I am experiencing issues with lifecycle rules + description: &description Resolve issues encountered while using lifecycle rules with Scaleway Object Storage +content: + h1: *title + paragraph: *description +tags: issues error problem lifecycle rules expire transfer class +categories: + - storage + - object-storage +dates: + validation: 2025-07-03 + posted: 2025-07-03 +--- + + + +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization + +## Problem + +## Cause + +## Possible solutions + +## Going further + +- Refer to the [bucket policies overview](/object-storage/api-cli/bucket-policy/) for more information on the different elements of a bucket policy. + +- If you did not manage to identify the error and solve it by yourself, [open a support ticket](/account/how-to/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) From ee7008ca1d8fe5b6c79759544b7ff37f53001388 Mon Sep 17 00:00:00 2001 From: SamyOubouaziz Date: Thu, 3 Jul 2025 17:51:31 +0200 Subject: [PATCH 02/16] feat(obj): update --- pages/object-storage/deleted-objects-still-billed.mdx | 4 ++-- pages/object-storage/object-deletion-issues.mdx | 4 ++-- pages/object-storage/object-versioning-issues.mdx | 4 ++-- pages/object-storage/presigned-url-errors.mdx | 4 ++-- 4 files changed, 8 insertions(+), 8 deletions(-) diff --git a/pages/object-storage/deleted-objects-still-billed.mdx b/pages/object-storage/deleted-objects-still-billed.mdx index 593d2181f8..aa9a3a5f42 100644 --- a/pages/object-storage/deleted-objects-still-billed.mdx +++ b/pages/object-storage/deleted-objects-still-billed.mdx @@ -1,7 +1,7 @@ --- meta: - title: &title - description: &description + title: &title I am still getting billed for deleted objects + description: &description I don't understand the amount billed compared to the objects that are present in my Scaleway Object Storage bucket content: h1: *title paragraph: *description diff --git a/pages/object-storage/object-deletion-issues.mdx b/pages/object-storage/object-deletion-issues.mdx index 593d2181f8..9ef3c87f87 100644 --- a/pages/object-storage/object-deletion-issues.mdx +++ b/pages/object-storage/object-deletion-issues.mdx @@ -1,7 +1,7 @@ --- meta: - title: &title - description: &description + title: &title I am experiencing issues while deleting objects + description: &description Find solutions to problems encountered while deleting objects with Scaleway Object Storage content: h1: *title paragraph: *description diff --git a/pages/object-storage/object-versioning-issues.mdx b/pages/object-storage/object-versioning-issues.mdx index 593d2181f8..b84526ada7 100644 --- a/pages/object-storage/object-versioning-issues.mdx +++ b/pages/object-storage/object-versioning-issues.mdx @@ -1,7 +1,7 @@ --- meta: - title: &title - description: &description + title: &title I am experiencing issues with object versioning + description: &description Solve issues encountered while using object versioning with Scaleway Object Storage content: h1: *title paragraph: *description diff --git a/pages/object-storage/presigned-url-errors.mdx b/pages/object-storage/presigned-url-errors.mdx index 593d2181f8..d07dd62cbe 100644 --- a/pages/object-storage/presigned-url-errors.mdx +++ b/pages/object-storage/presigned-url-errors.mdx @@ -1,7 +1,7 @@ --- meta: - title: &title - description: &description + title: &title I am getting presigned URL errors + description: &description I am receiving errors when using a presigned URL to access an object using Scaleway Object Storage. content: h1: *title paragraph: *description From 6149278b74451753f53d955a828f4f514c826cd6 Mon Sep 17 00:00:00 2001 From: SamyOubouaziz Date: Thu, 3 Jul 2025 18:04:02 +0200 Subject: [PATCH 03/16] feat(obj): update --- .../deleted-objects-still-billed.mdx | 0 .../object-storage/troubleshooting/index.mdx | 21 +++++++++++++------ .../object-deletion-issues.mdx | 0 .../object-versioning-issues.mdx | 0 .../presigned-url-errors.mdx | 0 5 files changed, 15 insertions(+), 6 deletions(-) rename pages/object-storage/{ => troubleshooting}/deleted-objects-still-billed.mdx (100%) rename pages/object-storage/{ => troubleshooting}/object-deletion-issues.mdx (100%) rename pages/object-storage/{ => troubleshooting}/object-versioning-issues.mdx (100%) rename pages/object-storage/{ => troubleshooting}/presigned-url-errors.mdx (100%) diff --git a/pages/object-storage/deleted-objects-still-billed.mdx b/pages/object-storage/troubleshooting/deleted-objects-still-billed.mdx similarity index 100% rename from pages/object-storage/deleted-objects-still-billed.mdx rename to pages/object-storage/troubleshooting/deleted-objects-still-billed.mdx diff --git a/pages/object-storage/troubleshooting/index.mdx b/pages/object-storage/troubleshooting/index.mdx index 46a47c2f0f..3dde4bb71e 100644 --- a/pages/object-storage/troubleshooting/index.mdx +++ b/pages/object-storage/troubleshooting/index.mdx @@ -59,10 +59,19 @@ productIcon: ObjectStorageProductIcon ## Object Storage troubleshooting pages - - [My API key does not work with Object Storage](/object-storage/troubleshooting/api-key-does-not-work) - - [I cannot access my data](/object-storage/troubleshooting/cannot-access-data) - - [I cannot delete my bucket](/object-storage/troubleshooting/cannot-delete-bucket) - - [I cannot restore my objects from Glacier](/object-storage/troubleshooting/cannot-restore-glacier) - - [I lost access to a bucket after applying a bucket policy](/object-storage/troubleshooting/lost-bucket-access-bucket-policy) - - [I am experiencing performance issues](/object-storage/troubleshooting/low-performance) +- [My API key does not work with Object Storage](/object-storage/troubleshooting/api-key-does-not-work/) +- [I cannot access my data](/object-storage/troubleshooting/cannot-access-data/) +- [I cannot delete my bucket](/object-storage/troubleshooting/cannot-delete-bucket/) +- [I cannot restore my objects from Glacier](/object-storage/troubleshooting/cannot-restore-glacier/) +- [I lost access to a bucket after applying a bucket policy](/object-storage/troubleshooting/lost-bucket-access-bucket-policy/) +- [I am experiencing performance issues](/object-storage/troubleshooting/low-performance/) +- [Lifecycle rules issues](/object-storage/troubleshooting/lifecycle-rules-issues/) +- [Deleted objects are still billed](/object-storage/troubleshooting/deleted-objects-still-billed/) +- [Lifecycle rules issues](/object-storage/troubleshooting/lifecycle-rules-issues/) +- [Object deletion issues](/object-storage/troubleshooting/object-deletion-issues/) +- [I am getting billed for objects that I cannot see](/object-storage/troubleshooting/deleted-objects-still-billed/) +- [I get error messages when trying to access a bucket](/object-storage/troubleshooting/error-messages-access/) +- [I am experiencing DNS/Edge Services issues](/object-storage/troubleshooting/issues-dns-edge-services/) +- [I am getting presigned URL errors](/object-storage/troubleshooting/presigned-url-errors/) +- [I am experiencing request rate errors](/object-storage/troubleshooting/request-rate-error/) diff --git a/pages/object-storage/object-deletion-issues.mdx b/pages/object-storage/troubleshooting/object-deletion-issues.mdx similarity index 100% rename from pages/object-storage/object-deletion-issues.mdx rename to pages/object-storage/troubleshooting/object-deletion-issues.mdx diff --git a/pages/object-storage/object-versioning-issues.mdx b/pages/object-storage/troubleshooting/object-versioning-issues.mdx similarity index 100% rename from pages/object-storage/object-versioning-issues.mdx rename to pages/object-storage/troubleshooting/object-versioning-issues.mdx diff --git a/pages/object-storage/presigned-url-errors.mdx b/pages/object-storage/troubleshooting/presigned-url-errors.mdx similarity index 100% rename from pages/object-storage/presigned-url-errors.mdx rename to pages/object-storage/troubleshooting/presigned-url-errors.mdx From 702e2b136388efbec0f0e9a18c22a16eca507dd2 Mon Sep 17 00:00:00 2001 From: SamyOubouaziz Date: Fri, 4 Jul 2025 12:00:19 +0200 Subject: [PATCH 04/16] feat(obj): update --- .../deleted-objects-still-billed.mdx | 36 +++++++++++++++++-- 1 file changed, 34 insertions(+), 2 deletions(-) diff --git a/pages/object-storage/troubleshooting/deleted-objects-still-billed.mdx b/pages/object-storage/troubleshooting/deleted-objects-still-billed.mdx index aa9a3a5f42..45fcbef412 100644 --- a/pages/object-storage/troubleshooting/deleted-objects-still-billed.mdx +++ b/pages/object-storage/troubleshooting/deleted-objects-still-billed.mdx @@ -1,6 +1,6 @@ --- meta: - title: &title I am still getting billed for deleted objects + title: &title I am getting billed for objects that I cannot see description: &description I don't understand the amount billed compared to the objects that are present in my Scaleway Object Storage bucket content: h1: *title @@ -20,10 +20,42 @@ dates: ## Problem -## Cause +The amount billed does not correspond to the objects that are present in my Scaleway Object Storage bucket. + +## Possible causes + +- Your [bucket is versioned](/object-storage/how-to/use-bucket-versioning/), and multiple versions of your objects are stored in it, incurring extra cost. + +- Some [multipart uploads](/object-storage/api-cli/multipart-uploads/) are ongoing. The storage used during the upload is billed, but the object is not visible as long as the upload is not complete. ## Possible solutions +### Bucket versioning + +1. Check the versioning status of your bucket via the [Scaleway console](https://console.scaleway.com/object-storage/buckets), or using the [GetBucketVersioning](/object-storage/api-cli/bucket-operations/#getbucketversioning) command: + ``` + aws s3api get-bucket-versioning --bucket BucketName + ``` + - If the versioning is `disabled`, the issue is not linked to versioning. + - If the versioning is `enabled` or `suspended`, you may have multiple versions of your objects. +2. Use the [ListObjectVersions](/object-storage/api-cli/bucket-operations/#listobjectversions) command to list the versions of the objects in your bucket: + ```sh + aws s3api list-object-versions --bucket BucketName + ``` + A list of all the objects versions and delete markers present in the bucket appears. +3. Delete the unwanted versions and delete markers using the [DeleteObject] command with a versionId specified: + ```sh + aws s3api delete-object --bucket BucketName --key ObjectName --version-id ObjectVersion + ``` +Refer to the [official Amazon S3 documentation](https://docs.aws.amazon.com/AmazonS3/latest/userguide/versioning-workflows.html) for more information on how versioning works. + +### Multipart uploads + +1. Check if some multipart uploads are ongoing using the [ListMultipartUpload](/object-storage/api-cli/multipart-uploads/#listing-multipart-uploads) command: + ```sh + list-multipart-uploads --bucket BucketName + ``` + ## Going further - Refer to the [bucket policies overview](/object-storage/api-cli/bucket-policy/) for more information on the different elements of a bucket policy. From f979a9f96d3dd4636004329a503ed60b8c3bde4f Mon Sep 17 00:00:00 2001 From: SamyOubouaziz Date: Fri, 4 Jul 2025 13:47:16 +0200 Subject: [PATCH 05/16] feat(obj): update --- .../troubleshooting/deleted-objects-still-billed.mdx | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/pages/object-storage/troubleshooting/deleted-objects-still-billed.mdx b/pages/object-storage/troubleshooting/deleted-objects-still-billed.mdx index 45fcbef412..2062d3327d 100644 --- a/pages/object-storage/troubleshooting/deleted-objects-still-billed.mdx +++ b/pages/object-storage/troubleshooting/deleted-objects-still-billed.mdx @@ -55,10 +55,14 @@ Refer to the [official Amazon S3 documentation](https://docs.aws.amazon.com/Amaz ```sh list-multipart-uploads --bucket BucketName ``` + A list of ongoing multipart uploads displays. + +2. Abort the unwanted multipart uploads via the [Scaleway console](/object-storage/how-to/abort-incomplete-mpu/), or [using the CLI](/object-storage/api-cli/multipart-uploads/). + +3. Optionally, you can [set up lifecycle rules](/object-storage/how-to/manage-lifecycle-rules/) to automatically abort incomplete multipart uploads after a given duration. ## Going further -- Refer to the [bucket policies overview](/object-storage/api-cli/bucket-policy/) for more information on the different elements of a bucket policy. - If you did not manage to identify the error and solve it by yourself, [open a support ticket](/account/how-to/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`) From 80f85476fa87d1a05a28582cd0061be8f1dce60c Mon Sep 17 00:00:00 2001 From: SamyOubouaziz Date: Mon, 7 Jul 2025 17:00:09 +0200 Subject: [PATCH 06/16] feat(obj): update --- .../troubleshooting/lifecycle-rules-issues.mdx | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-) diff --git a/pages/object-storage/troubleshooting/lifecycle-rules-issues.mdx b/pages/object-storage/troubleshooting/lifecycle-rules-issues.mdx index b96baae72d..0f5fa9fbf0 100644 --- a/pages/object-storage/troubleshooting/lifecycle-rules-issues.mdx +++ b/pages/object-storage/troubleshooting/lifecycle-rules-issues.mdx @@ -20,13 +20,25 @@ dates: ## Problem +I am experiencing issues with the lifecycle rules of my Scaleway Object Storage bucket. + ## Cause +- Lifecycle rules are not properly set +- Spaces are present in the prefixes or tags of your objects +- You reached the limit of 500,000 lifecycle jobs per day + ## Possible solutions +- Make sure that [lifecycle rules are properly set](/object-storage/how-to/manage-lifecycle-rules/) in the Scaleway console. + +- Make sure that the prefixes and tags of your objects do not contain prefixes or tags. + +- If you reached the limit of 500,000 jobs per day, you can [transition](/object-storage/how-to/edit-storage-class/) or [delete](/object-storage/how-to/delete-an-object/) objects manually. + ## Going further -- Refer to the [bucket policies overview](/object-storage/api-cli/bucket-policy/) for more information on the different elements of a bucket policy. +- Refer to the [lifecycle rules documentation](/object-storage/how-to/manage-lifecycle-rules/) for more information. - If you did not manage to identify the error and solve it by yourself, [open a support ticket](/account/how-to/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`) From 46535d6f06861e5f27a5957df625accf27aa8418 Mon Sep 17 00:00:00 2001 From: SamyOubouaziz Date: Mon, 7 Jul 2025 17:10:09 +0200 Subject: [PATCH 07/16] feat(obj): update --- .../object-storage/troubleshooting/lifecycle-rules-issues.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/pages/object-storage/troubleshooting/lifecycle-rules-issues.mdx b/pages/object-storage/troubleshooting/lifecycle-rules-issues.mdx index 0f5fa9fbf0..b4b772cb20 100644 --- a/pages/object-storage/troubleshooting/lifecycle-rules-issues.mdx +++ b/pages/object-storage/troubleshooting/lifecycle-rules-issues.mdx @@ -25,7 +25,9 @@ I am experiencing issues with the lifecycle rules of my Scaleway Object Storage ## Cause - Lifecycle rules are not properly set + - Spaces are present in the prefixes or tags of your objects + - You reached the limit of 500,000 lifecycle jobs per day ## Possible solutions @@ -36,6 +38,8 @@ I am experiencing issues with the lifecycle rules of my Scaleway Object Storage - If you reached the limit of 500,000 jobs per day, you can [transition](/object-storage/how-to/edit-storage-class/) or [delete](/object-storage/how-to/delete-an-object/) objects manually. +- For expiration rules, you can use the [HeadObject](/object-storage/api-cli/object-operations/#headobject) command to check which rule is applied to a specific object. The `x-amz-expiration` header should return the expiration date and rule ID. + ## Going further - Refer to the [lifecycle rules documentation](/object-storage/how-to/manage-lifecycle-rules/) for more information. From 9d97d37bfc5efff428940e7f3a6bade9f5c431a3 Mon Sep 17 00:00:00 2001 From: SamyOubouaziz Date: Mon, 7 Jul 2025 17:44:53 +0200 Subject: [PATCH 08/16] feat(obj): update --- .../troubleshooting/object-deletion-issues.mdx | 11 +++++++++++ .../troubleshooting/presigned-url-errors.mdx | 13 +++++++++++-- 2 files changed, 22 insertions(+), 2 deletions(-) diff --git a/pages/object-storage/troubleshooting/object-deletion-issues.mdx b/pages/object-storage/troubleshooting/object-deletion-issues.mdx index 9ef3c87f87..5db70b4cd1 100644 --- a/pages/object-storage/troubleshooting/object-deletion-issues.mdx +++ b/pages/object-storage/troubleshooting/object-deletion-issues.mdx @@ -20,10 +20,21 @@ dates: ## Problem +I am experiencing issues while deleting objects + ## Cause +object is locked +bucket is versioned + ## Possible solutions +object is locked +-> check object lock via a HeadObject, if it’s Governance, you can bypass it with a delete object with the header “x-amz-bypass-governance-retention”, also specify the VersionId since a bucket with lock enabled is versioned. + +bucket is versioned +A DeleteObject on a versioned bucket with no VersionId specified will create a delete marker and the objects will still exist. To actually delete it, list all the versions with a ListObjectVersions (you can specify the name of your object as prefix) and then send a DeleteObject on each versions. + ## Going further - Refer to the [bucket policies overview](/object-storage/api-cli/bucket-policy/) for more information on the different elements of a bucket policy. diff --git a/pages/object-storage/troubleshooting/presigned-url-errors.mdx b/pages/object-storage/troubleshooting/presigned-url-errors.mdx index d07dd62cbe..61f969cf02 100644 --- a/pages/object-storage/troubleshooting/presigned-url-errors.mdx +++ b/pages/object-storage/troubleshooting/presigned-url-errors.mdx @@ -20,14 +20,23 @@ dates: ## Problem +I am receiving errors when using a presigned URL to access an object. + ## Cause +- A clock skew of more than 15 minutes between the host and client will trigger a `InvalidSignatureException` or a `RequestTimeTooSkewed` error + +- The public link of your [private object](/object-storage/concepts/) has expired + ## Possible solutions -## Going further +- Make sure that there is less than 15 minutes of clock skew between the host and client machines. + +- Make sure that the object's public link has not expired. -- Refer to the [bucket policies overview](/object-storage/api-cli/bucket-policy/) for more information on the different elements of a bucket policy. +## Going further +- Refer to the [documentation on sharing objects](/object-storage/how-to/access-objects-via-https/) for more information on public links. - If you did not manage to identify the error and solve it by yourself, [open a support ticket](/account/how-to/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 From 6026b6453f7a93166f3f3ef97c8575e0538d7542 Mon Sep 17 00:00:00 2001 From: SamyOubouaziz Date: Wed, 9 Jul 2025 16:07:48 +0200 Subject: [PATCH 09/16] feat(obj): update --- .../troubleshooting/object-deletion-issues.mdx | 18 +++++++++++------- 1 file changed, 11 insertions(+), 7 deletions(-) diff --git a/pages/object-storage/troubleshooting/object-deletion-issues.mdx b/pages/object-storage/troubleshooting/object-deletion-issues.mdx index 5db70b4cd1..0b10a39748 100644 --- a/pages/object-storage/troubleshooting/object-deletion-issues.mdx +++ b/pages/object-storage/troubleshooting/object-deletion-issues.mdx @@ -24,20 +24,24 @@ I am experiencing issues while deleting objects ## Cause -object is locked -bucket is versioned +- The object you are trying to delete is locked +- The bucket is versioned, and deleting an object adds a **delete marker** rather than deleting the object ## Possible solutions -object is locked --> check object lock via a HeadObject, if it’s Governance, you can bypass it with a delete object with the header “x-amz-bypass-governance-retention”, also specify the VersionId since a bucket with lock enabled is versioned. +### Object lock -bucket is versioned -A DeleteObject on a versioned bucket with no VersionId specified will create a delete marker and the objects will still exist. To actually delete it, list all the versions with a ListObjectVersions (you can specify the name of your object as prefix) and then send a DeleteObject on each versions. +Check if the object is locked using the [HeadObject](/object-storage/api-cli/object-operations/#headobject) command. If it is locked with the **Governance** retention mode, you can bypass it with the [DeleteObject](/object-storage/api-cli/object-operations/#deleteobject) command using the `x-amz-bypass-governance-retention` header. You must also specify the VersionId of the object, as buckets with object lock enabled are automatically versioned. + +### Bucket versioning + +A [DeleteObject](/object-storage/api-cli/object-operations/#deleteobject) operation on a versioned bucket with no `VersionId` specified will create a delete marker, and the targeted objects will keep existing. To permanently delete it, list all the versions with [ListObjectVersions](/object-storage/api-cli/bucket-operations/#listobjectversions) (you can specify the name of your object as a prefix), then use the [DeleteObject](/object-storage/api-cli/object-operations/#deleteobject) operation on each version. ## Going further -- Refer to the [bucket policies overview](/object-storage/api-cli/bucket-policy/) for more information on the different elements of a bucket policy. +- Refer to the [object lock documentation](/object-storage/api-cli/object-lock/) for more information. + +- Refer to the [bucket versioning documentation](/object-storage/how-to/use-bucket-versioning/) for more information. - If you did not manage to identify the error and solve it by yourself, [open a support ticket](/account/how-to/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`) From 49bd983cce21a9113ee145e99419135c37c1cf5b Mon Sep 17 00:00:00 2001 From: SamyOubouaziz Date: Wed, 9 Jul 2025 16:13:47 +0200 Subject: [PATCH 10/16] feat(obj): update --- .../object-versioning-issues.mdx | 40 ------------------- 1 file changed, 40 deletions(-) delete mode 100644 pages/object-storage/troubleshooting/object-versioning-issues.mdx diff --git a/pages/object-storage/troubleshooting/object-versioning-issues.mdx b/pages/object-storage/troubleshooting/object-versioning-issues.mdx deleted file mode 100644 index b84526ada7..0000000000 --- a/pages/object-storage/troubleshooting/object-versioning-issues.mdx +++ /dev/null @@ -1,40 +0,0 @@ ---- -meta: - title: &title I am experiencing issues with object versioning - description: &description Solve issues encountered while using object versioning with Scaleway Object Storage -content: - h1: *title - paragraph: *description -tags: -categories: - - storage - - object-storage -dates: - validation: 2025-07-03 - posted: 2025-07-03 ---- - - - -- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - -## Problem - -## Cause - -## Possible solutions - -## Going further - -- Refer to the [bucket policies overview](/object-storage/api-cli/bucket-policy/) for more information on the different elements of a bucket policy. - -- If you did not manage to identify the error and solve it by yourself, [open a support ticket](/account/how-to/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) From 6c750b94060527cd4699813886f4b4cb7a8e6f7f Mon Sep 17 00:00:00 2001 From: SamyOubouaziz Date: Wed, 9 Jul 2025 16:14:20 +0200 Subject: [PATCH 11/16] feat(obj): revert error --- .husky/commit-msg | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.husky/commit-msg b/.husky/commit-msg index e3bc3e4e1e..5bf2e5ca3c 100755 --- a/.husky/commit-msg +++ b/.husky/commit-msg @@ -1,4 +1,4 @@ #!/bin/sh . "$(dirname "$0")/_/husky.sh" -pnpm commitlint -e && echo "\nHey! Did you Val(e)date your changes? 💡🤡\n" +yarn commitlint -e && echo "\nHey! Did you Val(e)date your changes? 💡🤡\n" From dcabc5925039ee0c307b735d925ee0fca2356942 Mon Sep 17 00:00:00 2001 From: SamyOubouaziz Date: Thu, 10 Jul 2025 11:12:30 +0200 Subject: [PATCH 12/16] feat(obj): update --- .../troubleshooting/deleted-objects-still-billed.mdx | 4 +++- .../object-storage/troubleshooting/lifecycle-rules-issues.mdx | 4 +++- .../object-storage/troubleshooting/object-deletion-issues.mdx | 4 +++- pages/object-storage/troubleshooting/presigned-url-errors.mdx | 4 +++- pages/object-storage/troubleshooting/request-rate-error.mdx | 3 ++- 5 files changed, 14 insertions(+), 5 deletions(-) diff --git a/pages/object-storage/troubleshooting/deleted-objects-still-billed.mdx b/pages/object-storage/troubleshooting/deleted-objects-still-billed.mdx index 2062d3327d..1bf6e2d429 100644 --- a/pages/object-storage/troubleshooting/deleted-objects-still-billed.mdx +++ b/pages/object-storage/troubleshooting/deleted-objects-still-billed.mdx @@ -14,7 +14,9 @@ dates: posted: 2025-07-03 --- - +import Requirements from '@macros/iam/requirements.mdx' + + - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization diff --git a/pages/object-storage/troubleshooting/lifecycle-rules-issues.mdx b/pages/object-storage/troubleshooting/lifecycle-rules-issues.mdx index b4b772cb20..1634a81831 100644 --- a/pages/object-storage/troubleshooting/lifecycle-rules-issues.mdx +++ b/pages/object-storage/troubleshooting/lifecycle-rules-issues.mdx @@ -14,7 +14,9 @@ dates: posted: 2025-07-03 --- - +import Requirements from '@macros/iam/requirements.mdx' + + - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization diff --git a/pages/object-storage/troubleshooting/object-deletion-issues.mdx b/pages/object-storage/troubleshooting/object-deletion-issues.mdx index 0b10a39748..15c2ad1dfd 100644 --- a/pages/object-storage/troubleshooting/object-deletion-issues.mdx +++ b/pages/object-storage/troubleshooting/object-deletion-issues.mdx @@ -14,7 +14,9 @@ dates: posted: 2025-07-03 --- - +import Requirements from '@macros/iam/requirements.mdx' + + - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization diff --git a/pages/object-storage/troubleshooting/presigned-url-errors.mdx b/pages/object-storage/troubleshooting/presigned-url-errors.mdx index 61f969cf02..6ecaa8efdc 100644 --- a/pages/object-storage/troubleshooting/presigned-url-errors.mdx +++ b/pages/object-storage/troubleshooting/presigned-url-errors.mdx @@ -13,9 +13,11 @@ dates: validation: 2025-07-03 posted: 2025-07-03 --- +import Requirements from '@macros/iam/requirements.mdx' - + +- 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 ## Problem diff --git a/pages/object-storage/troubleshooting/request-rate-error.mdx b/pages/object-storage/troubleshooting/request-rate-error.mdx index 1a7438641c..1df0977728 100644 --- a/pages/object-storage/troubleshooting/request-rate-error.mdx +++ b/pages/object-storage/troubleshooting/request-rate-error.mdx @@ -9,11 +9,12 @@ categories: - storage - object-storage --- -import Requirements from '@macros/iam/requirements.mdx' +import Requirements from '@macros/iam/requirements.mdx' +- 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 ## Problem From 8e4bdeb336cdbee5d6ba95d09d287c576ffcaf30 Mon Sep 17 00:00:00 2001 From: SamyOubouaziz Date: Tue, 15 Jul 2025 15:31:50 +0200 Subject: [PATCH 13/16] fix(gen): update --- .husky/commit-msg | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.husky/commit-msg b/.husky/commit-msg index 5bf2e5ca3c..e3bc3e4e1e 100755 --- a/.husky/commit-msg +++ b/.husky/commit-msg @@ -1,4 +1,4 @@ #!/bin/sh . "$(dirname "$0")/_/husky.sh" -yarn commitlint -e && echo "\nHey! Did you Val(e)date your changes? 💡🤡\n" +pnpm commitlint -e && echo "\nHey! Did you Val(e)date your changes? 💡🤡\n" From 184a3f3d7bf596a7d985199c6c5d57a34fb54e51 Mon Sep 17 00:00:00 2001 From: SamyOubouaziz Date: Wed, 16 Jul 2025 14:23:52 +0200 Subject: [PATCH 14/16] docs(obj): update --- .../troubleshooting/deleted-objects-still-billed.mdx | 8 ++------ .../troubleshooting/lifecycle-rules-issues.mdx | 8 ++------ .../troubleshooting/object-deletion-issues.mdx | 8 ++------ .../troubleshooting/presigned-url-errors.mdx | 8 ++------ 4 files changed, 8 insertions(+), 24 deletions(-) diff --git a/pages/object-storage/troubleshooting/deleted-objects-still-billed.mdx b/pages/object-storage/troubleshooting/deleted-objects-still-billed.mdx index 1bf6e2d429..6340cd83a3 100644 --- a/pages/object-storage/troubleshooting/deleted-objects-still-billed.mdx +++ b/pages/object-storage/troubleshooting/deleted-objects-still-billed.mdx @@ -1,10 +1,6 @@ --- -meta: - title: &title I am getting billed for objects that I cannot see - description: &description I don't understand the amount billed compared to the objects that are present in my Scaleway Object Storage bucket -content: - h1: *title - paragraph: *description +title: I am getting billed for objects that I cannot see +description: I don't understand the amount billed compared to the objects that are present in my Scaleway Object Storage bucket tags: categories: - storage diff --git a/pages/object-storage/troubleshooting/lifecycle-rules-issues.mdx b/pages/object-storage/troubleshooting/lifecycle-rules-issues.mdx index 1634a81831..208d1b11b4 100644 --- a/pages/object-storage/troubleshooting/lifecycle-rules-issues.mdx +++ b/pages/object-storage/troubleshooting/lifecycle-rules-issues.mdx @@ -1,10 +1,6 @@ --- -meta: - title: &title I am experiencing issues with lifecycle rules - description: &description Resolve issues encountered while using lifecycle rules with Scaleway Object Storage -content: - h1: *title - paragraph: *description +title: I am experiencing issues with lifecycle rules +description: Resolve issues encountered while using lifecycle rules with Scaleway Object Storage tags: issues error problem lifecycle rules expire transfer class categories: - storage diff --git a/pages/object-storage/troubleshooting/object-deletion-issues.mdx b/pages/object-storage/troubleshooting/object-deletion-issues.mdx index 15c2ad1dfd..7d1fc2170a 100644 --- a/pages/object-storage/troubleshooting/object-deletion-issues.mdx +++ b/pages/object-storage/troubleshooting/object-deletion-issues.mdx @@ -1,10 +1,6 @@ --- -meta: - title: &title I am experiencing issues while deleting objects - description: &description Find solutions to problems encountered while deleting objects with Scaleway Object Storage -content: - h1: *title - paragraph: *description +title: I am experiencing issues while deleting objects +description: Find solutions to problems encountered while deleting objects with Scaleway Object Storage tags: categories: - storage diff --git a/pages/object-storage/troubleshooting/presigned-url-errors.mdx b/pages/object-storage/troubleshooting/presigned-url-errors.mdx index 6ecaa8efdc..86bab76a1b 100644 --- a/pages/object-storage/troubleshooting/presigned-url-errors.mdx +++ b/pages/object-storage/troubleshooting/presigned-url-errors.mdx @@ -1,10 +1,6 @@ --- -meta: - title: &title I am getting presigned URL errors - description: &description I am receiving errors when using a presigned URL to access an object using Scaleway Object Storage. -content: - h1: *title - paragraph: *description +title: I am getting presigned URL errors +description: I am receiving errors when using a presigned URL to access an object using Scaleway Object Storage. tags: categories: - storage From 6d0d3e0dfa915d1fd620f9c8700096a526d63833 Mon Sep 17 00:00:00 2001 From: SamyOubouaziz Date: Wed, 16 Jul 2025 14:53:19 +0200 Subject: [PATCH 15/16] Apply suggestions from code review Co-authored-by: Jessica <113192637+jcirinosclwy@users.noreply.github.com> --- .../object-storage/troubleshooting/lifecycle-rules-issues.mdx | 4 ++-- .../object-storage/troubleshooting/object-deletion-issues.mdx | 2 +- pages/object-storage/troubleshooting/presigned-url-errors.mdx | 4 ++-- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/pages/object-storage/troubleshooting/lifecycle-rules-issues.mdx b/pages/object-storage/troubleshooting/lifecycle-rules-issues.mdx index 208d1b11b4..48ceda59db 100644 --- a/pages/object-storage/troubleshooting/lifecycle-rules-issues.mdx +++ b/pages/object-storage/troubleshooting/lifecycle-rules-issues.mdx @@ -6,7 +6,7 @@ categories: - storage - object-storage dates: - validation: 2025-07-03 + validation: 2025-07-16 posted: 2025-07-03 --- @@ -32,7 +32,7 @@ I am experiencing issues with the lifecycle rules of my Scaleway Object Storage - Make sure that [lifecycle rules are properly set](/object-storage/how-to/manage-lifecycle-rules/) in the Scaleway console. -- Make sure that the prefixes and tags of your objects do not contain prefixes or tags. +- Make sure that the prefixes and tags of your objects do not contain any spaces. - If you reached the limit of 500,000 jobs per day, you can [transition](/object-storage/how-to/edit-storage-class/) or [delete](/object-storage/how-to/delete-an-object/) objects manually. diff --git a/pages/object-storage/troubleshooting/object-deletion-issues.mdx b/pages/object-storage/troubleshooting/object-deletion-issues.mdx index 7d1fc2170a..53a8728e9b 100644 --- a/pages/object-storage/troubleshooting/object-deletion-issues.mdx +++ b/pages/object-storage/troubleshooting/object-deletion-issues.mdx @@ -6,7 +6,7 @@ categories: - storage - object-storage dates: - validation: 2025-07-03 + validation: 2025-07-16 posted: 2025-07-03 --- diff --git a/pages/object-storage/troubleshooting/presigned-url-errors.mdx b/pages/object-storage/troubleshooting/presigned-url-errors.mdx index 86bab76a1b..7ff992c0a7 100644 --- a/pages/object-storage/troubleshooting/presigned-url-errors.mdx +++ b/pages/object-storage/troubleshooting/presigned-url-errors.mdx @@ -1,12 +1,12 @@ --- -title: I am getting presigned URL errors +title: I am getting presigned URL errors description: I am receiving errors when using a presigned URL to access an object using Scaleway Object Storage. tags: categories: - storage - object-storage dates: - validation: 2025-07-03 + validation: 2025-07-16 posted: 2025-07-03 --- import Requirements from '@macros/iam/requirements.mdx' From 6638ec9941a5384de800160db790f9b06107f472 Mon Sep 17 00:00:00 2001 From: SamyOubouaziz Date: Wed, 16 Jul 2025 14:54:27 +0200 Subject: [PATCH 16/16] docs(obj): update --- .../troubleshooting/deleted-objects-still-billed.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/object-storage/troubleshooting/deleted-objects-still-billed.mdx b/pages/object-storage/troubleshooting/deleted-objects-still-billed.mdx index 6340cd83a3..c3b684f870 100644 --- a/pages/object-storage/troubleshooting/deleted-objects-still-billed.mdx +++ b/pages/object-storage/troubleshooting/deleted-objects-still-billed.mdx @@ -6,7 +6,7 @@ categories: - storage - object-storage dates: - validation: 2025-07-03 + validation: 2025-07-16 posted: 2025-07-03 ---