-
Notifications
You must be signed in to change notification settings - Fork 258
feat(obj): add new troubleshooting pages MTA-5448 #5228
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from 14 commits
Commits
Show all changes
16 commits
Select commit
Hold shift + click to select a range
3691b5c
feat(obj): add new troubleshooting pages MTA-5488
SamyOubouaziz ee7008c
feat(obj): update
SamyOubouaziz 6149278
feat(obj): update
SamyOubouaziz 702e2b1
feat(obj): update
SamyOubouaziz f979a9f
feat(obj): update
SamyOubouaziz 80f8547
feat(obj): update
SamyOubouaziz 46535d6
feat(obj): update
SamyOubouaziz 9d97d37
feat(obj): update
SamyOubouaziz 6026b64
feat(obj): update
SamyOubouaziz 49bd983
feat(obj): update
SamyOubouaziz 6c750b9
feat(obj): revert error
SamyOubouaziz dcabc59
feat(obj): update
SamyOubouaziz 8e4bdeb
fix(gen): update
SamyOubouaziz 184a3f3
docs(obj): update
SamyOubouaziz 6d0d3e0
Apply suggestions from code review
SamyOubouaziz 6638ec9
docs(obj): update
SamyOubouaziz File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
74 changes: 74 additions & 0 deletions
74
pages/object-storage/troubleshooting/deleted-objects-still-billed.mdx
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,74 @@ | ||
| --- | ||
| 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 | ||
| - object-storage | ||
| dates: | ||
| validation: 2025-07-03 | ||
| posted: 2025-07-03 | ||
| --- | ||
|
|
||
| import Requirements from '@macros/iam/requirements.mdx' | ||
|
|
||
| <Requirements /> | ||
|
|
||
| - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization | ||
|
|
||
| ## Problem | ||
|
|
||
| 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 | ||
| ``` | ||
| 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 | ||
|
|
||
|
|
||
| - 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) | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
54 changes: 54 additions & 0 deletions
54
pages/object-storage/troubleshooting/lifecycle-rules-issues.mdx
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,54 @@ | ||
| --- | ||
| 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 | ||
| - object-storage | ||
| dates: | ||
| validation: 2025-07-03 | ||
SamyOubouaziz marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| posted: 2025-07-03 | ||
| --- | ||
|
|
||
| import Requirements from '@macros/iam/requirements.mdx' | ||
|
|
||
| <Requirements /> | ||
|
|
||
| - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization | ||
|
|
||
| ## 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. | ||
SamyOubouaziz marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
| - 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. | ||
|
|
||
| - 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) | ||
53 changes: 53 additions & 0 deletions
53
pages/object-storage/troubleshooting/object-deletion-issues.mdx
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,53 @@ | ||
| --- | ||
| title: I am experiencing issues while deleting objects | ||
| description: Find solutions to problems encountered while deleting objects with Scaleway Object Storage | ||
| tags: | ||
| categories: | ||
| - storage | ||
| - object-storage | ||
| dates: | ||
| validation: 2025-07-03 | ||
SamyOubouaziz marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| posted: 2025-07-03 | ||
| --- | ||
|
|
||
| import Requirements from '@macros/iam/requirements.mdx' | ||
|
|
||
| <Requirements /> | ||
|
|
||
| - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization | ||
|
|
||
| ## Problem | ||
|
|
||
| I am experiencing issues while deleting objects | ||
|
|
||
| ## Cause | ||
|
|
||
| - 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 lock | ||
|
|
||
| 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 [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`) | ||
| - 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) | ||
47 changes: 47 additions & 0 deletions
47
pages/object-storage/troubleshooting/presigned-url-errors.mdx
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,47 @@ | ||
| --- | ||
| title: I am getting presigned URL errors | ||
SamyOubouaziz marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| 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 | ||
SamyOubouaziz marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| posted: 2025-07-03 | ||
| --- | ||
| import Requirements from '@macros/iam/requirements.mdx' | ||
|
|
||
| <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 | ||
|
|
||
| ## 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 | ||
|
|
||
| - 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. | ||
|
|
||
| ## 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 | ||
| - 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) | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.