Skip to content

Commit c8d45cb

Browse files
SamyOubouazizjcirinosclwy
SamyOubouaziz
and
jcirinosclwy
authored
feat(obj): add new troubleshooting pages MTA-5448 (#5228)
* feat(obj): add new troubleshooting pages MTA-5488 * feat(obj): update * feat(obj): update * feat(obj): update * feat(obj): update * feat(obj): update * feat(obj): update * feat(obj): update * feat(obj): update * feat(obj): update * feat(obj): revert error * feat(obj): update * fix(gen): update * docs(obj): update * Apply suggestions from code review Co-authored-by: Jessica <[email protected]> * docs(obj): update --------- Co-authored-by: Jessica <[email protected]>
1 parent 2bf6f79 commit c8d45cb

File tree

6 files changed

+245
-7
lines changed

6 files changed

+245
-7
lines changed

‎pages/object-storage/troubleshooting/deleted-objects-still-billed.mdx‎

Lines changed: 74 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,74 @@
1+
---
2+
title: I am getting billed for objects that I cannot see
3+
description: I don't understand the amount billed compared to the objects that are present in my Scaleway Object Storage bucket
4+
tags:
5+
categories:
6+
- storage
7+
- object-storage
8+
dates:
9+
validation: 2025-07-16
10+
posted: 2025-07-03
11+
---
12+
13+
import Requirements from '@macros/iam/requirements.mdx'
14+
15+
<Requirements />
16+
17+
- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
18+
19+
## Problem
20+
21+
The amount billed does not correspond to the objects that are present in my Scaleway Object Storage bucket.
22+
23+
## Possible causes
24+
25+
- Your [bucket is versioned](/object-storage/how-to/use-bucket-versioning/), and multiple versions of your objects are stored in it, incurring extra cost.
26+
27+
- 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.
28+
29+
## Possible solutions
30+
31+
### Bucket versioning
32+
33+
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:
34+
```
35+
aws s3api get-bucket-versioning --bucket BucketName
36+
```
37+
- If the versioning is `disabled`, the issue is not linked to versioning.
38+
- If the versioning is `enabled` or `suspended`, you may have multiple versions of your objects.
39+
2. Use the [ListObjectVersions](/object-storage/api-cli/bucket-operations/#listobjectversions) command to list the versions of the objects in your bucket:
40+
```sh
41+
aws s3api list-object-versions --bucket BucketName
42+
```
43+
A list of all the objects versions and delete markers present in the bucket appears.
44+
3. Delete the unwanted versions and delete markers using the [DeleteObject] command with a versionId specified:
45+
```sh
46+
aws s3api delete-object --bucket BucketName --key ObjectName --version-id ObjectVersion
47+
```
48+
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.
49+
50+
### Multipart uploads
51+
52+
1. Check if some multipart uploads are ongoing using the [ListMultipartUpload](/object-storage/api-cli/multipart-uploads/#listing-multipart-uploads) command:
53+
```sh
54+
list-multipart-uploads --bucket BucketName
55+
```
56+
A list of ongoing multipart uploads displays.
57+
58+
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/).
59+
60+
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.
61+
62+
## Going further
63+
64+
65+
- 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:
66+
- Object Storage Endpoint (e.g. `s3.fr-par.scw.cloud`)
67+
- Bucket name
68+
- Object name (if the request concerns an object)
69+
- Request type (PUT, GET, etc.)
70+
- HTTP status code
71+
- Date and time (timestamp)
72+
- User-agent (SDK, client, console, etc.)
73+
- Transaction ID (if possible)
74+
- Log / trace of the error (if possible)

‎pages/object-storage/troubleshooting/index.mdx‎

Lines changed: 15 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -59,10 +59,19 @@ productIcon: ObjectStorageProductIcon
5959
## Object Storage troubleshooting pages
6060

6161
<LinksList>
62-
- [My API key does not work with Object Storage](/object-storage/troubleshooting/api-key-does-not-work)
63-
- [I cannot access my data](/object-storage/troubleshooting/cannot-access-data)
64-
- [I cannot delete my bucket](/object-storage/troubleshooting/cannot-delete-bucket)
65-
- [I cannot restore my objects from Glacier](/object-storage/troubleshooting/cannot-restore-glacier)
66-
- [I lost access to a bucket after applying a bucket policy](/object-storage/troubleshooting/lost-bucket-access-bucket-policy)
67-
- [I am experiencing performance issues](/object-storage/troubleshooting/low-performance)
62+
- [My API key does not work with Object Storage](/object-storage/troubleshooting/api-key-does-not-work/)
63+
- [I cannot access my data](/object-storage/troubleshooting/cannot-access-data/)
64+
- [I cannot delete my bucket](/object-storage/troubleshooting/cannot-delete-bucket/)
65+
- [I cannot restore my objects from Glacier](/object-storage/troubleshooting/cannot-restore-glacier/)
66+
- [I lost access to a bucket after applying a bucket policy](/object-storage/troubleshooting/lost-bucket-access-bucket-policy/)
67+
- [I am experiencing performance issues](/object-storage/troubleshooting/low-performance/)
68+
- [Lifecycle rules issues](/object-storage/troubleshooting/lifecycle-rules-issues/)
69+
- [Deleted objects are still billed](/object-storage/troubleshooting/deleted-objects-still-billed/)
70+
- [Lifecycle rules issues](/object-storage/troubleshooting/lifecycle-rules-issues/)
71+
- [Object deletion issues](/object-storage/troubleshooting/object-deletion-issues/)
72+
- [I am getting billed for objects that I cannot see](/object-storage/troubleshooting/deleted-objects-still-billed/)
73+
- [I get error messages when trying to access a bucket](/object-storage/troubleshooting/error-messages-access/)
74+
- [I am experiencing DNS/Edge Services issues](/object-storage/troubleshooting/issues-dns-edge-services/)
75+
- [I am getting presigned URL errors](/object-storage/troubleshooting/presigned-url-errors/)
76+
- [I am experiencing request rate errors](/object-storage/troubleshooting/request-rate-error/)
6877
</LinksList>

‎pages/object-storage/troubleshooting/lifecycle-rules-issues.mdx‎

Lines changed: 54 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,54 @@
1+
---
2+
title: I am experiencing issues with lifecycle rules
3+
description: Resolve issues encountered while using lifecycle rules with Scaleway Object Storage
4+
tags: issues error problem lifecycle rules expire transfer class
5+
categories:
6+
- storage
7+
- object-storage
8+
dates:
9+
validation: 2025-07-16
10+
posted: 2025-07-03
11+
---
12+
13+
import Requirements from '@macros/iam/requirements.mdx'
14+
15+
<Requirements />
16+
17+
- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
18+
19+
## Problem
20+
21+
I am experiencing issues with the lifecycle rules of my Scaleway Object Storage bucket.
22+
23+
## Cause
24+
25+
- Lifecycle rules are not properly set
26+
27+
- Spaces are present in the prefixes or tags of your objects
28+
29+
- You reached the limit of 500,000 lifecycle jobs per day
30+
31+
## Possible solutions
32+
33+
- Make sure that [lifecycle rules are properly set](/object-storage/how-to/manage-lifecycle-rules/) in the Scaleway console.
34+
35+
- Make sure that the prefixes and tags of your objects do not contain any spaces.
36+
37+
- 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.
38+
39+
- 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.
40+
41+
## Going further
42+
43+
- Refer to the [lifecycle rules documentation](/object-storage/how-to/manage-lifecycle-rules/) for more information.
44+
45+
- 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:
46+
- Object Storage Endpoint (e.g. `s3.fr-par.scw.cloud`)
47+
- Bucket name
48+
- Object name (if the request concerns an object)
49+
- Request type (PUT, GET, etc.)
50+
- HTTP status code
51+
- Date and time (timestamp)
52+
- User-agent (SDK, client, console, etc.)
53+
- Transaction ID (if possible)
54+
- Log / trace of the error (if possible)

‎pages/object-storage/troubleshooting/object-deletion-issues.mdx‎

Lines changed: 53 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,53 @@
1+
---
2+
title: I am experiencing issues while deleting objects
3+
description: Find solutions to problems encountered while deleting objects with Scaleway Object Storage
4+
tags:
5+
categories:
6+
- storage
7+
- object-storage
8+
dates:
9+
validation: 2025-07-16
10+
posted: 2025-07-03
11+
---
12+
13+
import Requirements from '@macros/iam/requirements.mdx'
14+
15+
<Requirements />
16+
17+
- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
18+
19+
## Problem
20+
21+
I am experiencing issues while deleting objects
22+
23+
## Cause
24+
25+
- The object you are trying to delete is locked
26+
- The bucket is versioned, and deleting an object adds a **delete marker** rather than deleting the object
27+
28+
## Possible solutions
29+
30+
### Object lock
31+
32+
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.
33+
34+
### Bucket versioning
35+
36+
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.
37+
38+
## Going further
39+
40+
- Refer to the [object lock documentation](/object-storage/api-cli/object-lock/) for more information.
41+
42+
- Refer to the [bucket versioning documentation](/object-storage/how-to/use-bucket-versioning/) for more information.
43+
44+
- 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:
45+
- Object Storage Endpoint (e.g. `s3.fr-par.scw.cloud`)
46+
- Bucket name
47+
- Object name (if the request concerns an object)
48+
- Request type (PUT, GET, etc.)
49+
- HTTP status code
50+
- Date and time (timestamp)
51+
- User-agent (SDK, client, console, etc.)
52+
- Transaction ID (if possible)
53+
- Log / trace of the error (if possible)

‎pages/object-storage/troubleshooting/presigned-url-errors.mdx‎

Lines changed: 47 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,47 @@
1+
---
2+
title: I am getting presigned URL errors
3+
description: I am receiving errors when using a presigned URL to access an object using Scaleway Object Storage.
4+
tags:
5+
categories:
6+
- storage
7+
- object-storage
8+
dates:
9+
validation: 2025-07-16
10+
posted: 2025-07-03
11+
---
12+
import Requirements from '@macros/iam/requirements.mdx'
13+
14+
<Requirements />
15+
16+
- A Scaleway account logged into the [console](https://console.scaleway.com)
17+
- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
18+
19+
## Problem
20+
21+
I am receiving errors when using a presigned URL to access an object.
22+
23+
## Cause
24+
25+
- A clock skew of more than 15 minutes between the host and client will trigger a `InvalidSignatureException` or a `RequestTimeTooSkewed` error
26+
27+
- The public link of your [private object](/object-storage/concepts/) has expired
28+
29+
## Possible solutions
30+
31+
- Make sure that there is less than 15 minutes of clock skew between the host and client machines.
32+
33+
- Make sure that the object's public link has not expired.
34+
35+
## Going further
36+
37+
- Refer to the [documentation on sharing objects](/object-storage/how-to/access-objects-via-https/) for more information on public links.
38+
- 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:
39+
- Object Storage Endpoint (e.g. `s3.fr-par.scw.cloud`)
40+
- Bucket name
41+
- Object name (if the request concerns an object)
42+
- Request type (PUT, GET, etc.)
43+
- HTTP status code
44+
- Date and time (timestamp)
45+
- User-agent (SDK, client, console, etc.)
46+
- Transaction ID (if possible)
47+
- Log / trace of the error (if possible)

‎pages/object-storage/troubleshooting/request-rate-error.mdx‎

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,11 +9,12 @@ categories:
99
- storage
1010
- object-storage
1111
---
12-
import Requirements from '@macros/iam/requirements.mdx'
1312

13+
import Requirements from '@macros/iam/requirements.mdx'
1414

1515
<Requirements />
1616

17+
- A Scaleway account logged into the [console](https://console.scaleway.com)
1718
- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
1819

1920
## Problem

0 commit comments

Comments
 (0)